| Status code | 202 |
|---|---|
| Status text | Accepted |
| Category | 2xx Success |
| Response has body | Usually |
| Specification | RFC 9110 |
What does 202 Accepted mean?
The request was accepted for processing, but the processing has not finished. It belongs to the 2xx Success class, which means the request was received, understood and accepted.
When do APIs return 202?
Asynchronous or queued work — the server took your job but the result is not ready.
How to fix a 202 Accepted
Not an error. Look for a status URL or job ID in the body so you can poll for completion.
Reproduce a 202 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/202 — you will
see the 202 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 2xx status codes
200 OK
The request succeeded and the response body contains the result.
201 Created
The request succeeded and a new resource was created as a result.
204 No Content
The request succeeded and there is deliberately no response body.
206 Partial Content
The server is delivering only part of the resource, as requested by a Range header.