Accepted
The request was accepted but hasn't been processed yet. Used for async operations — the server is saying "I got it, I'll handle it later." Common with job queues and webhooks.
COMMON CAUSES
HOW TO FIX IT
What this means for monitoring
For async endpoints, 202 is the expected response. The actual processing happens later. You may want a separate monitor for the downstream job.
Related status codes
2xx Success
The request succeeded. This is the response you want to see. For GET requests, the body contains the requested resource. For POST requests, the body contains the result of the action.
The request succeeded and a new resource was created. Typically returned by POST endpoints. The Location header usually points to the new resource.
The request succeeded but there's nothing to send back. Common for DELETE requests and PUT/PATCH updates where you don't need the updated resource returned.
The server is delivering only part of the resource. Used for range requests — downloading a large file in chunks, or resuming a broken download.
Get alerted when your endpoints return unexpected status codes.
Larm checks your HTTP endpoints from multiple global locations and alerts you when they return status codes outside your expected range.