| Status code | 413 |
|---|---|
| Status text | Payload Too Large |
| Category | 4xx Client Error |
| Response has body | Usually |
| Specification | RFC 9110 |
What does 413 Payload Too Large mean?
The request body is larger than the server is willing to process. It belongs to the 4xx Client Error class, which means the request contains bad syntax or cannot be fulfilled. Something about the request needs to change.
When do APIs return 413?
Large file uploads or oversized JSON payloads.
How to fix a 413 Payload Too Large
Reduce the body size, enable compression, or use the API's chunked or multipart upload path. Note the limit may come from a reverse proxy rather than the application.
Reproduce a 413 response
The fastest way to understand a status code is to trigger one and read the full response. Open the
API tester and send a request to https://httpbin.org/status/413 — you will
see the 413 status along with every response header the server sent. Comparing those headers against
a working request is often what reveals the cause.
When you are debugging a real endpoint, check the response headers as carefully as the body, and confirm you are using the right HTTP method for the operation.
Related 4xx status codes
400 Bad Request
The server could not understand the request because it is malformed.
401 Unauthorized
The request lacks valid authentication credentials. Despite the name, this means unauthenticated.
402 Payment Required
The request cannot be processed until payment is made.
403 Forbidden
The server understood the request and knows who you are, but refuses to authorise it.
404 Not Found
The server cannot find the requested resource.
405 Method Not Allowed
The endpoint exists but does not support the HTTP method you used.