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.
413 payload_too_large means the request body is larger than the configured API limit; 415 unsupported_media_type means the body was not application/json, with the sent type in details.received_content_type (read 2026-10-06 in the errors docs).
How do I fix each?
For 413, send a media URL instead of embedding the file in the body. For 415, set Content-Type: application/json.
What should I do in practice?
Both errors are caught before any generation starts.
- Pass media by public HTTPS URL.
- Set the Content-Type header explicitly.
- Read
detailsin the error body.
Sources
Related posts
More in Developers
- 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.
- A 5xx on a Sume paid submit never proves no job: retry with the key
On Sume, only a validation, authorization or balance error proves a paid create was refused. A 5xx does not, so retry with the same Idempotency-Key.
- sume/auto 400 unsupported_capability: 11 s, 2 s, 480p and silent audio
sume/auto fails closed on 2 s, 11 s, 480p, 768p and generate_audio false. The request is rejected before any provider call. Here is what to send instead.
- AI video client timeout: the Sume job still runs and still bills
A timeout on your HTTP client does not cancel a Sume job. Save the job id, poll the polling_url, and cancel only before generation starts. Python example.
Written by Sume