Sume 400 invalid_request: read the details array
A Sume 400 invalid_request means the body, query, path or headers are not valid. The error envelope has code, message, request_id and a details array.
400 invalid_request (or bad_request) means the request body, query, path or headers are not valid. The envelope has code, message, request_id and details (read 2026-10-06 in the errors docs).
How do I find the bad field?
Read details first; fix that field; resubmit with the same idempotency key only if the original request never created a job.
{
"error": {
"code": "invalid_request",
"message": "Invalid request body, parameters, or headers.",
"request_id": "req_...",
"details": []
}
}What should I do in practice?
A 400 is never fixed by waiting.
- Do not retry a 400 unchanged.
- Compare the body to the model's docs page.
- Log the request id.
Sources
Related posts
More in Developers
- Sume 401 halfway through a batch: stop every worker, do not retry
A 401 on a Sume submit means a missing, malformed or revoked key. The SDK does not retry it, and neither should you. Python sample that keeps job ids.
- 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.
- 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.
Written by Sume