202
Success
202 Accepted
The request has been accepted for processing, but processing has not been completed.
Definition (RFC 9110)
HTTP status code 202 202 Accepted is defined in RFC 9110 (HTTP Semantics), Section 15.3.3 — the current authoritative specification for HTTP semantics, published June 2022, which obsoletes the older RFC 7231 and RFC 2616.
Description
202 Accepted means the server has accepted the request but hasn't finished processing it yet. This is used for asynchronous operations — like sending an email, generating a report, or running a background job — where the result isn't immediately available.
The response may include a URL to check the status or an estimated completion time.
Common Causes
- Async job submission (email sending, report generation)
- Webhook delivery endpoints
- Queue-based architectures (Kafka, RabbitMQ, SQS)
- Batch import APIs
How to Fix
- Include a
Locationheader pointing to a job status endpoint - Document the async contract clearly in API docs
- Return a job ID in the response body for polling
- Consider using webhooks to notify on completion
Check your website's HTTP status code
Check now →