202 Accepted

What it means

Used for asynchronous jobs. The response usually tells the client where to check progress.

Common causes

• The server queued a background job.

How to fix it

1. Poll the status URL provided by the API, or wait for a webhook.

Example response

HTTP/1.1 202 Accepted
Location: /jobs/123
Retry-After: 5

Worked example

A report-generation request is accepted into a background queue and returns 202 Accepted before the file exists. The client follows the Location status URL, waits according to Retry-After, and fetches the finished report when processing completes. Acceptance is not a promise that the job will eventually succeed, so the status endpoint should also report failure.

How to read this response

1. Find the status line in your browser's Network panel, API client, or server access log.
2. Read the response body and headers shown above; headers such as Location, Allow, Retry-After, and WWW-Authenticate explain the next step.
3. Use the code's class to orient your diagnosis: informational, successful, redirected, request-related, or server-side.

How to check a status code

Enter a URL in the HTTP Status Checker to see its status code, every redirect hop, and response time. For redirect-heavy pages, the Website Speed Test shows how much time redirects add.

Frequently asked questions

What it means: HTTP 202

202 Accepted: The request was accepted for processing, but processing has not finished.

Common causes: 202

The server queued a background job.

How to fix it: HTTP 202

Poll the status URL provided by the API, or wait for a webhook.

Tools