MockFoxAdvertise

HTTP 202 Accepted

Updated Free mock REST & WebSocket APIs

HTTP 202 Accepted — The request was accepted for processing, but the processing hasn't finished.

Class
2xx Success
Defined in
RFC 9110 §15.3.3
Official
Yes (IANA registry)
Cacheable by default
No (unless Cache-Control/Expires say so)

Try it: get a real 202 response

Our test endpoint answers every request with 202 Accepted.

curl -i https://mockfox.dev/api/status/202

Use it in tests, health-check monitors or to see how your client handles a 202. Add ?delay=2000 to slow it down.

What does HTTP 202 mean?

Used for asynchronous work: the server queues a job (video encoding, report generation, bulk import) and returns 202 straight away, ideally with a Location or body pointing to a status endpoint the client can poll. A 202 promises nothing about the outcome — the job can still fail later.

Handling 202

  1. Visitors: Nothing to fix — this is a success status.
  2. Developers: Make sure clients handle this status as success (response.ok is true for 200–299) and know whether to expect a body.

Example 202 response

HTTP/1.1 202 Accepted
Location: /jobs/7f3a
Content-Type: application/json

{"status":202,"error":"Accepted"}

2xx Success: The request was received, understood and accepted. See the full list of HTTP status codes.

Related status codes

Related tools

Frequently asked questions

What does HTTP 202 Accepted mean?

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

Is 202 an error?

No. 202 is a success status.

Where is 202 defined?

In RFC 9110 §15.3.3. It's listed in the IANA HTTP Status Code Registry.

How can I test how my app handles a 202?

Call https://mockfox.dev/api/status/202 — it responds with 202 to any method, with CORS enabled. Add ?delay=2000 to simulate a slow response.