Solved Docs

Authentication and scopes

API keys, OAuth, the principal, and the scope model.

Solved's public API accepts two credentials. API keys (Authorization: Bearer slv_live_…) work on both REST and MCP today. OAuth 2.1 (authorization code + PKCE) is MCP-only, for hosted connectors like Claude.ai and ChatGPT, and ships in wave 2 — until then, those clients aren't supported and API-key clients (Claude Code, Cursor, custom-header clients) are the way in.

Every credential resolves to one account identity (GCID) and a set of scopes, shaped <product>:<resource>.<read|write> — e.g. link:links.write, artqr:qr.read — or <product>:* for everything in one product. write includes delete. Account-management scopes (issuing your own keys) are never granted to a key itself, only to a signed-in session — a leaked key can't mint more keys.

A call without the scope it needs fails before it does anything:

{ "code": "insufficient_scope", "status": 403, "title": "Insufficient scope" }

Sensitive actions need a fresh session. Creating or rolling an API key, or approving an OAuth grant, requires a session established in the last 10 minutes. Signed in longer ago? You'll see step_up_required (401) and need to sign in again before the action goes through. This is deliberate: it means a hijacked long-lived session alone can't mint new credentials.

Next: API keys · Errors