HTTP 202 Accepted — What It Means
What HTTP status code 202 Accepted means, when servers return it, and how to handle it correctly.
Published September 22, 2026
HTTP 202 Accepted means the server received the request and will process it later, asynchronously. The work may not be finished yet and might still fail.
What it means
It is used for queued jobs, long-running tasks and batch operations. The response often points to a status URL the client can poll.
Common causes: Queued background jobs; Video encoding or report generation; Webhook receivers deferring work.
On the wire
POST /reports HTTP/1.1
HTTP/1.1 202 Accepted
Location: /reports/42/status
Practical examples
Test it from the shell
curl -i https://example.com/path # look for HTTP 202Handling 202 in code or config
res.status(202).json({ jobId: 42, statusUrl: '/reports/42/status' })How to fix it
Provide a status endpoint or callback; Return a job id in the body; Do not promise the result is final.
1. Reproduce: curl -i <url>
2. Confirm the status is 202
3. Apply the fix above and re-testCommon mistakes
- Treating this as an error when it is a normal part of HTTP.
- Return a job id in the body
- Ignoring the response headers that explain the details.
Key takeaways
- 202 means Accepted.
- HTTP 202 Accepted means the server received the request and will process it later, asynchronously.
- Read the response headers and logs for the exact cause.
FAQ
202 vs 200?
200 means the work is done; 202 means it was accepted and will be done later.
Is 202 a client or server error?
It is a success status code, in the 2xx class.