Sume 401 and 404: wrong API key, or a resource in another workspace
401 unauthorized means the API key is missing or invalid. 404 not_found means the resource does not exist in the current workspace, so check which key you used.
401 unauthorized means the API key is missing or not valid; 404 not_found means the resource does not exist in the current workspace (read 2026-10-06 in the errors docs).
Why would a job id return 404?
A job created with one workspace's key is not visible to another workspace's key, so use the same key that created it.
What should I do in practice?
Use the request id for support.
- Check the Authorization header is
Bearer <key>. - Match the key to the workspace.
- Do not paste keys into issue reports.
Sources
Related posts
More in Developers
- Sume 402 insufficient_credits: top up, then retry the same request
A Sume 402 means the balance cannot cover the requested generation. Add funds or lower the request cost, then retry with the same Idempotency-Key.
- Sume 409 errors: job_not_completed, job_not_cancelable and more
A Sume 409 means the job operation does not fit the job's current status: job_not_completed, job_not_cancelable or job_generation_already_started.
- Sume 413 payload_too_large and 415: shrink the body, send JSON
413 means the request body is over the API limit. 415 means the body was not application/json, shown in details.received_content_type.
- Sume 429 rate_limited: honor retry-after and use an Idempotency-Key
On a Sume 429 rate_limited, back off using retry-after if present, and never retry an unsafe submit without an Idempotency-Key. Headers explained.
Written by Sume