Skip to content

Errors

All errors return a JSON body with an error string. Some add extra fields (issues, scope, Retry-After).

Error reference

HTTPBody errorMeaning
400invalid_request (+ issues)Body failed validation.
401unauthorizedMissing / bad / revoked / expired key, or suspended org.
403insufficient_scope (+ scope)Key lacks the required scope.
403high_sensitivity_requires_elevatedLive key, high-sensitivity class, org not elevated.
404not_foundRequest / grant not found under your org.
409grant_not_viewableGrant revoked, paused, or over its view cap.
429rate_limited (+ Retry-After)Slow down.

Key-minting errors (console)

These surface in the console when you try to mint a key, as 409:

Body errorMeaning
live_requires_verificationOrg not verified — can't mint a live key.
dpa_requiredDPA not accepted — can't mint a live key.

See Getting started for how to clear both gates.

Handling notes

  • 401 is deliberately opaque. Every auth failure looks identical, so don't try to branch on the reason — re-check the key and org status out of band.
  • 400 includes issues. Use the issues array to point callers at the exact invalid field.
  • 429 includes Retry-After. Always honor it — see Rate limits.

Next: API reference →

Upload once · Share many times · Track forever.