| Previous | Next |
| HTTP_STATUS_CREATED | HTTP_STATUS_NON_AUTH_INFORMATION |
HTTP_STATUS_ACCEPTED
The server accepted the request, but processing has not completed and might later be rejected or fail. HTTP does not provide a second response on the original connection when asynchronous work finishes.
A useful 202 response provides a status document, job identifier, or monitor URL. Clients should poll or subscribe to that separate status mechanism rather than treat 202 as completion.
Because processing may finish later, a 202 response is useful only when the application gives the caller a way to observe progress or obtain the eventual result. APIs commonly return a job identifier, status URI, or other tracking information. The final operation can still fail even though the initial request was accepted.
Looking for a different code? Search another status or error code.