HTTP status codes / 2xx — Success
202 Accepted
Accepted for asynchronous processing; the result comes later.
What it means
The server accepted the request but has not completed it — typical for queued jobs, batch imports and webhooks. The response should tell the client how to track progress, e.g. a status URL.
Common causes
- The work was queued for async processing — completion is NOT confirmed
- Look for a status URL or job ID in the response body
Reproduce it in cURL
curl -i https://httpbin.org/status/202
Same request, no terminal: paste this into the cURL converter for native code, or straight into ReqPad on your phone.
How to debug it
Treating 202 as a final success is a common bug: poll the status endpoint or listen for the callback to learn the real outcome.
The fastest way to pin down a 202 is to reproduce the exact request and inspect what actually went over the wire — status, headers, timing and body, without your app code in the way. That is what an API client is for; ReqPad does it from your phone, with every request saved to history.
Related codes
200 OK · 201 Created · 203 Non-Authoritative Information · 204 No Content · 205 Reset Content · 206 Partial Content — or the full reference.
Reproduce that 202 in 10 seconds.
Build the request, send it, read status + headers + timing — on your iPhone. Free to start.