success RFC 9110
HTTP 202 Accepted
Request was accepted for processing but not yet completed.
What it means
The server acknowledged the request and is processing it asynchronously. Common for background jobs, batch imports, video processing, or any operation that would take too long to complete inside a single HTTP request. The response typically includes a URL where the client can poll for status.
When servers send it
- •Queueing a background job (video encode, report generation, batch import)
- •Long-running workflow that will be completed asynchronously
What the client does
Polls the URL provided (usually in a `Location` header or JSON body) until the job completes.
When you see it
- •Asynchronous processing — expected behavior
Similar codes
200 OK success
The request succeeded and the response body contains the requested data.
201 Created success
Request succeeded and a new resource was created as a result.
204 No Content success
Request succeeded but there is no body in the response.
206 Partial Content success
Server is returning part of a resource due to a Range header from the client.
← All HTTP status codes · HTTP status cheat sheet · HTTP headers reference