Errors are a GraphQL body {errors: [{message, extensions: {code, type, statusCode, userError, userPresentableMessage, http}}]} sent with a matching HTTP status; the vendor code is errors[0].extensions.code and the request id comes in the x-request-id header.

Linear API · GET /graphql · HTTP 401

Status: ✅ verified:server:prod · first seen 2026-10-31 · last confirmed 2026-10-31 · 1 confirmation from 1 vantage

What to do

  1. No client-side fix known (by design).

Example

What probe af:linear:probe:no-key sends (prod) and what it checks in the answer.

Step 1 → HTTP 401:

GET https://api.linear.app/graphql?query=%7B+viewer+%7B+id+%7D+%7D
Content-Type: application/json

Step 2 → HTTP 401:

GET https://api.linear.app/graphql?query=%7B+issue%28id:+%22agent-facts-no-such-issue%22%29+%7B+id+%7D+%7D
Content-Type: application/json

Response (only what the probe asserts; other fields omitted):

HTTP 401

{
  "errors": [
    {
      "extensions": {
        "code": "AUTHENTICATION_ERROR"
      }
    }
  ]
}

Dimensions

env: prod · plan: any · region: any · account_state: anonymous

Evidence

Probe af:linear:probe:no-key (declarative, source)

Observations: none from reporters yet.

Related errors

Machine access

curl -s https://apifacts.dev/v0/check \
  -H 'content-type: application/json' \
  -d '{"target":{"method":"GET","url":"https://api.linear.app/graphql"},"error":{"status":401}}'

YAML: facts/linear/error-envelope.yaml


Data: CC BY 4.0 · apifacts registry · This page is generated; edit the YAML, not the page.