Skip to content
ShiftGraph

HTTP 401, authentication and identity

AUTH-016

Invalid or revoked API token.

What it means

The Bearer token does not exist, has been revoked, or has been rotated.

What to do

Issue a new token under Settings, Tokens, or Account, Tokens. Tokens are shown once and stored only as a hash.

The response

Every failure arrives in this shape. The trace_id is worth keeping: it identifies the request in our logs and carries nothing about your data.

{
  "type": "https://shiftgraph.dev/errors/AUTH-016",
  "title": "Invalid or revoked API token.",
  "status": 401,
  "code": "AUTH-016",
  "trace_id": "01J8Z…"
}

Related codes

Sessions, second factors, sign-in methods, and the credentials that reach the API. A second factor is required of every account, so several of these have no bypass by design.

The full error reference, or write to support@shiftgraph.dev with the trace id.