| Status code | 408 |
|---|---|
| Status text | Request Timeout |
| Category | 4xx Client Error |
| Response has body | Usually |
| Specification | RFC 9110 |
What does 408 Request Timeout mean?
The server timed out waiting for the client to finish sending the request. 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 408?
A slow or stalled upload, or an idle keep-alive connection the server decided to reclaim.
How to fix a 408 Request Timeout
Distinct from 504: here the client was too slow, not the upstream server. Check for a slow network path or a request body that is being generated lazily. Retrying is usually safe.
Reproduce a 408 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/408 — you will
see the 408 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.