Digital Toolchest

HTTP 2xx Success Codes List

Get a complete, ordered reference of HTTP 2xx status codes for successful request outcomes.

HTTP 2xx success codes(10 registered status codes)

Based on the IANA HTTP Status Code Registry for the 2xx range. Includes any registered special entries and excludes unassigned ranges.

How to use this list

Apply HTTP 2xx codes in 3 steps

Takes ~5 seconds
  1. 1
    Choose output format

    Select text for docs, JSON for constants, or HTML for form controls.

  2. 2
    Copy or download

    Use one-click copy or download the output file.

  3. 3
    Use in your workflow

    Paste into runbooks, tests, SDK docs, or monitoring rules.

Need dropdown options for 2xx handling? Use HTML <select> output.

Common use cases

  • Developers documenting expected API response classes
  • QA teams creating focused response-code test coverage
  • Platform teams standardizing logs and alert labels

Examples

2xx example code.

Input
200
Output
200 OK

Additional code in the same class.

Input
204
Output
204 No Content

HTML output for select menus.

Input
200 OK
Output
<option value="200 OK">200 OK</option>

Reliable HTTP 2xx response reference

This list provides a focused reference of HTTP 2xx entries so teams can standardize behavior across implementation, testing, and operations.

Every HTTP 2xx code means the request succeeded, but the class covers several distinct outcomes: 200 OK for a standard success response, 201 Created after a POST that adds a new resource, 202 Accepted for work that's been queued rather than finished, and 204 No Content for successful requests with nothing to send back. This list gives you the full IANA-registered 2xx range in copy-ready text, JSON, or HTML <option> format, so you can wire up accurate success-path handling in API docs, client SDKs, and integration tests without cross-referencing the full status code registry.

200, 201, or 204?

2xx codes all mean success, but the right one signals what actually happened — an existing resource, a newly created one, or no body at all.

  • 200 for a general success with a body
  • 201 for a resource just created
  • 204 for success with nothing to return
One click, three formats

Grab the range as plain text, a JSON array, or ready-to-paste HTML <option> tags.

  • Plain text list
  • JSON array
  • HTML <option> tags
Scoped to success only

No redirects, client errors, or server errors mixed in — just the codes that confirm a request worked.

  • Response contract docs
  • Success-path test fixtures
  • Dashboard status grouping

Choosing the right 2xx code

Picking the specific success code, not just "200 for everything," makes your API easier to consume correctly.

  • Return 201 with a Location header when a request creates a new resource — don't default to 200.
  • Use 204 for actions that succeed but return no body, like a DELETE or a settings update.
  • Reserve 202 for requests you've accepted but will finish processing asynchronously.

Frequently asked questions

What's the actual difference between 200 and 201?>
200 is a general success response with a body. 201 specifically means a new resource was created, typically in response to a POST, and should include a Location header pointing to it.
When should an endpoint return 204 instead of 200?>
Use 204 when the request succeeded but there's no content to return, such as a successful DELETE or an update that doesn't echo the resource back.
Are 2xx codes ever used to signal partial failure?>
No. Every code in the 2xx class means the request was received, understood, and accepted successfully — partial or conditional outcomes belong in the response body, not the status code.

Related Developer lists

Application MIME Types List | Copy-Ready Text, JSON & HTML

Copy common application/* MIME types in text, JSON, or HTML format for API content negotiation, downloads, and file validation.

Audio MIME Types List | Copy-Ready Text, JSON & HTML

Copy common audio MIME types in text, JSON, or HTML format for uploads, playback support checks, and processing pipelines.

Common MIME Types List | Copy-Ready Text, JSON & HTML

Copy a practical common MIME types list in text, JSON, or HTML format for uploads, APIs, validation, and content handling.

HTTP 3xx Redirect Codes List | Copy-Ready Text, JSON & HTML

Copy all HTTP 3xx redirect codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows, ready to paste.

HTTP 4xx Error Codes List | Copy-Ready Text, JSON & HTML

Copy all HTTP 4xx client error codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows.

HTTP 5xx Error Codes List | Copy-Ready Text, JSON & HTML

Copy all HTTP 5xx server error codes in text, JSON, or HTML format for API docs, tests, and monitoring workflows.

HTTP Request Methods List | Copy-Ready Text, JSON & HTML

Copy a clean http request methods list (GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS, TRACE, CONNECT) in text, JSON, or HTML for API docs and tooling.

HTTP Status Codes List | Copy-Ready Text, JSON & HTML

Copy the complete IANA-registered HTTP status codes list in text, JSON, or HTML format for APIs, docs, testing, and observability workflows.

Image MIME Types List | Copy-Ready Text, JSON & HTML

Copy common image MIME types in text, JSON, or HTML format for upload validation, image processing, and media tooling.

Video MIME Types List | Copy-Ready Text, JSON & HTML

Copy common video MIME types in text, JSON, or HTML format for upload policies, streaming workflows, and player support checks.