All HTTP status codes

HTTP 202 Accepted

Success

The request was accepted for processing, but processing hasn't completed — and may still fail. Common for queued/asynchronous jobs.

Defined in RFC 9110

Common causes

  • Async job queues, batch imports, long-running tasks behind an API

How to fix it

  1. Provide a status URL or webhook so clients can track completion

  2. Clients should not assume the work succeeded — poll the job status

Related status codes

200 OK

The request succeeded. The response body contains the result — a page for GET, the operation outcome for POST.

201 Created

The request succeeded and a new resource was created. The Location header usually points at the new resource — the canonical response for a successful POST in REST APIs.

Want to explore status codes interactively? Try the free HTTP Status Code Reference — search, categories and example responses, right in your browser.