HTTP 413
request_too_large — Shorty API error
Request too large (HTTP 413): when the Shorty API returns the request_too_large error, why, and how to fix it.
| Code | HTTP status | Type URI |
|---|---|---|
request_too_large | 413 | https://aishorty.com/docs/api/errors/request_too_large |
When it happens
The request payload exceeded the accepted size limit for the endpoint.
Example response
{
"type": "https://aishorty.com/docs/api/errors/request_too_large",
"title": "Request too large",
"status": 413,
"detail": "The request payload is too large.",
"instance": "urn:request:req_01J9Z8ABCDEFGH0123456789",
"code": "request_too_large",
"request_id": "req_01J9Z8ABCDEFGH0123456789"
}How to fix it
Reduce the payload — for large media, pass a URL the service fetches instead of inlining bytes.
Related errors
- validation_failed
Validation failed (HTTP 400)