2xx Success

202 Accepted

The request was accepted for processing, but isn't finished.

What 202 means

Used for asynchronous work: the server queued the job and will do it later. The response often includes a URL to poll for the result.

Common causes

A long-running job (exports, video processing, bulk imports) was queued.

How to fix it

If you're calling an API

Poll the status URL in the response (or wait for a webhook) instead of assuming the work is done.

If you run the server

Return a status URL or job ID, and a Retry-After hint for polling.

Should you retry?

Don't resubmit; poll the job's status instead.

Example response

HTTP

HTTP/1.1 202 Accepted
Location: /v1/jobs/7f3c
Retry-After: 5
Content-Type: application/json

{"jobId": "7f3c", "status": "queued"}

Related headers: Location, Retry-After.

Defined in: RFC 9110 (HTTP Semantics). 202 is a success.

HTTP 202 FAQ

What does HTTP 202 mean?

202 Accepted: The request was accepted for processing, but isn't finished. Used for asynchronous work: the server queued the job and will do it later. The response often includes a URL to poll for the result.

Is 202 a client or server error?

Neither: 202 is a success response (2xx). The request was received, understood and accepted.

How do I fix a 202 error?

Poll the status URL in the response (or wait for a webhook) instead of assuming the work is done.

Should I retry after a 202?

Don't resubmit; poll the job's status instead.

Other 2xx status codes

All HTTP status codes