The HTTP Status Code 202 means that the client's request has been accepted for processing, but the processing has not been completed.
Note that this does not guarantee that the request will eventually be acted upon. It's still possible even if a code 202 is returned that the request may be disallowed when processing occurs.
Frequently Asked Questions
What does HTTP 202 mean?
HTTP 202 Accepted means the server has received and accepted the client's request, but processing has not been completed yet. It is part of the 2xx success family, signaling that the request was understood — not that the work is done.
When does a server return a 202 status code?
A server returns 202 when a request is queued for asynchronous or batch processing rather than handled immediately. Common examples include video processing jobs, report generation, bulk data imports, and email campaigns where the outcome will not be ready by the time the response is sent.
Does a 202 response guarantee the request will succeed?
No. A 202 is intentionally non-committal — it only confirms the request was accepted, not that it will be fulfilled. Processing may still fail or be disallowed once the server actually attempts to carry it out.
What is the difference between HTTP 202 and HTTP 200?
HTTP 200 OK means the request completed successfully and the result is included in the response. HTTP 202 Accepted means the request was received and will be processed later — the final outcome is not yet known at the time of the response.
What is the difference between HTTP 202 and HTTP 201?
HTTP 201 Created means the request succeeded and a new resource was immediately created on the server, typically in response to a POST or PUT. HTTP 202 means the request was accepted but processing is deferred, so no resource has necessarily been created yet.
How should a client know when processing is complete after a 202 response?
Because HTTP has no built-in mechanism for a server to send an asynchronous follow-up, the server should include a status endpoint URL — either in the Location header or the response body — so the client can poll for the final result. The response body may also include the current processing state or an estimated completion time.
