Available tool
JSON Schema Generator
Generate a starter JSON Schema from example JSON locally in your browser for API contracts, validation, tests, and documentation.
Open toolDeveloper Tools
HTTP Status Code Lookup
Search common HTTP status codes locally in your browser with REST API usage notes, retry guidance, and backend examples.
Runs locally in your browser
HTTP Status Code Lookup
Search common HTTP status codes with REST API usage notes and retry guidance.
| Code | Meaning | Class | Common API use | Retry guidance |
|---|
How to use it
What this HTTP Status Code Lookup is for
Use this HTTP Status Code Lookup when designing API responses, debugging logs, reviewing SDK behavior, or deciding whether a client should retry a failed request.
The lookup runs locally in your browser. It does not upload search terms, filters, or copied output to a server.
How to use it
Search by status code, reason phrase, category, or usage note. You can also filter by status class: informational, success, redirection, client error, or server error.
Use the result as a practical reference, then check your team’s API contract before changing behavior that clients may already depend on.
Related reading
Read REST API Status Codes Explained for the article version of this reference. For retry and conflict behavior, read Idempotency in APIs Explained. Use the UUID Generator for request ID examples and the JSON Formatter when checking error response bodies.
Related tools
Keep the workflow moving
These local-first tools often pair well with HTTP Status Code Lookup.
Available tool
JSON to TypeScript Types Generator
Generate TypeScript interfaces or type aliases from JSON locally in your browser for API responses, fixtures, and backend contracts.
Open toolAvailable tool
JSONPath Tester
Test common JSONPath expressions against JSON locally in your browser for API debugging, fixtures, logs, and documentation.
Open toolFAQ
HTTP Status Code Lookup questions
Does this HTTP Status Code Lookup send searches to a server?
No. Searching and filtering run locally in your browser, and search input is not sent to a server.
Does this include every registered HTTP status code?
The first version focuses on the common status codes backend developers use most often in REST APIs.
Which status code should I use for validation errors?
Many APIs use 400 Bad Request, while some use 422 Unprocessable Entity for semantically invalid request bodies. The key is to be consistent and document the contract.
Which status codes are usually retryable?
Transient 5xx responses such as 502, 503, and 504 are often retryable with backoff. 429 may be retryable after the rate-limit window. Most 4xx responses are not retryable without changing the request.