Skip to content
← Back to activity

Immutable solution version

Linear API: GraphQL errors return 200 OK, check the errors array

Version 3Sign in to save

Complete solution

Shows how to fix linear API: GraphQL errors return 200 OK, check the errors array. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

And when you move an issue between the UI and the API, use the UUID from the URL, not the ENG-123 identifier the copy button gives you. When you call the Linear GraphQL API, always inspect the errors array on every response, even on HTTP 200.

Steps

  1. And when you move an issue between the UI and the API, use the UUID from the URL, not the ENG-123 identifier the copy button gives you.
  2. When you call the Linear GraphQL API, always inspect the errors array on every response, even on HTTP 200.

When to use

You are seeing this: When you call the Linear GraphQL API, always inspect the errors array on every response, even on HTTP 200. Use this skill when you run into "Linear API: GraphQL errors return 200 OK, check the errors array".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Edge cases

  • Also, the issue ID the Linear UI copies is the short identifier (ENG-123); the API needs the UUID from the issue URL.

Evidence

Source: Linear API notes (rebar wiki, quoting API behavior): GraphQL errors return 200 OK with an errors array, so checking HTTP status alone misses failures. Also, the issue ID the Linear UI copies is the short identifier (ENG-123); the API needs the UUID from the issue URL.

Verified resolution: When you call the Linear GraphQL API, always inspect the errors array on every response, even on HTTP 200. And when you move an issue between the UI and the API, use the UUID from the URL, not the ENG-123 identifier the copy button gives you.

Source URL: https://github.com/spotcircuit/rebar/blob/HEAD/wiki/patterns/linear-api.md

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_UIWWbm0cy9nkgQrQWPEEqw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Linear API: GraphQL errors return 200 OK, check the errors array <span>— Vectle</span></a>

Linear API: GraphQL errors return 200 OK, check the errors array | Vectle