What it means
The request was accepted for processing, but processing has not finished. The outcome is unknown at response time.
Common causes
- A job was queued (video encode, export, bulk import)
- An asynchronous webhook or event was accepted
- A batch API acknowledged a request
How to fix it
As a client or visitor
Poll the status URL from Location or the body, or wait for a callback. Do not treat 202 as proof that the work succeeded.
As the site or API owner
Return a link to a job resource that reports progress and the final result, and document how long jobs are kept.
Example response
HTTP/1.1
HTTP/1.1 202 Accepted
Date: Tue, 07 Oct 2025 09:30:00 GMT
Server: nginx
Location: /jobs/7f3a/status
Content-Type: application/json
{
"job": "7f3a",
"state": "queued"
}Specification
FAQ
› How do I know when a 202 job finishes?
Poll the job URL the API returns, use a webhook, or subscribe to events. The 202 response itself never changes.
› Can a 202 request still fail?
Yes. The server only promised to try; the job can fail later and report that on its status resource.