Success HTTP Status Codes (2xx)

Use this hub to confirm that your API and web responses return the correct success semantics for creation, async processing, partial responses, and body expectations.

What this group covers

A 2xx code means the request was accepted and processed according to protocol, but payload shape, idempotency, and downstream behavior vary by exact code.

What to check first

Match response code to method semantics (GET/POST/PUT/DELETE).
Verify whether the endpoint should return a body (200) or intentionally omit one (204).
For async workflows, confirm you return 202 only when processing is not complete.

How related 2xx codes differ

200/201/202/204 are commonly swapped incorrectly. Choose based on resource creation and processing completion, not convenience.

Success HTTP Status Codes (2xx) list with quick summaries

HTTP 200 OK — HTTP 200 OK indicates a success response outcome.
HTTP 201 Created — HTTP 201 Created indicates a success response outcome.
HTTP 202 Accepted — HTTP 202 Accepted indicates a success response outcome.
HTTP 203 Non-Authoritative Information — HTTP 203 Non-Authoritative Information indicates a success response outcome.
HTTP 204 No Content — HTTP 204 No Content indicates a success response outcome.
HTTP 205 Reset Content — HTTP 205 Reset Content indicates a success response outcome.
HTTP 206 Partial Content — HTTP 206 Partial Content indicates a success response outcome.
HTTP 207 Multi-Status — HTTP 207 Multi-Status indicates a success response outcome.
HTTP 208 Already Reported — HTTP 208 Already Reported indicates a success response outcome.
HTTP 226 IM Used — HTTP 226 IM Used indicates a success response outcome.

When to escalate

Escalate when clients depend on one success code but backend teams return another, causing contract or SDK mismatches.

Next steps

Browse all status classes · Compare similar codes · Read implementation FAQ