API keys
Issuing, scoping, rotating and revoking API keys.
API keys authenticate REST and MCP calls made outside the Solved web apps — scripts, backends, AI agents.
Create one. Keys are account-level (not per product) and issued from your account settings
(account.solved.group once the cabinet ships; until then, from the API-keys page of any product you're
signed into). Creating a key requires a session less than 10 minutes old — if yours is older you'll be
asked to sign in again (step_up_required) before the key is issued.
A key looks like slv_live_e17Hk2Qp…9xZr4fT2aB. It's shown once, in full, at creation time — copy it then,
because we only ever store a salted hash. If you lose it, don't try to recover it: roll it instead.
Scope it. Every key is created with one or more scopes, e.g. link:links.write, artqr:qr.read, or
link:* for everything in one product. Grant the narrowest scope that does the job — a key only needs
write if it creates or changes things.
Use it.
Rotate it without downtime: POST /v1/api-keys/{key_id}/roll issues a new key and keeps the old one
valid for a grace window you choose (up to 7 days), so you can redeploy before it stops working.
Revoke it instantly from account settings, or by calling the revoke endpoint. Revocation reaches every service within 30 seconds. If you ever think a key leaked, use "Secure my account" instead of a plain revoke — it revokes every key and OAuth grant on the account at once.
Next: Quickstart: REST · Quickstart: MCP · Concepts: auth and scopes