HTTP status code 202 — Accepted
Quick answer
Status code 202 (Accepted): Request accepted for processing, but not completed yet. Typical for async jobs — poll a status URL or wait for a webhook.
Typical for async jobs — poll a status URL or wait for a webhook.
202 is not failure; work may still fail later. Pair it with a job id or status endpoint so clients can track progress.
Common causes
- Queued background job (video encode, bulk import, email send)
- Webhook-based integrations that process off the request thread
How to fix it
Poll the status/job endpoint the API returned, or subscribe to its webhook — do not assume 202 means done.
Frequently asked questions
What is status code 202?
202 Accepted: Request accepted for processing, but not completed yet. Typical for async jobs — poll a status URL or wait for a webhook.
When should I expect HTTP 202?
202 is not failure; work may still fail later. Pair it with a job id or status endpoint so clients can track progress.
What usually causes HTTP 202?
Queued background job (video encode, bulk import, email send); Webhook-based integrations that process off the request thread.
How do I fix HTTP 202?
Poll the status/job endpoint the API returned, or subscribe to its webhook — do not assume 202 means done.
Where can I see all status codes?
Open the HTTP status codes hub on TryDevSnip for the full reference list.
Does TryDevSnip log my API traffic?
No. These pages are static reference. TryDevSnip does not proxy or inspect your HTTP calls.