REST API HTTP Status Code Reference Guide
Browse RFC-standard HTTP status codes (2xx, 3xx, 4xx, 5xx) and generate API error documentation tables with standard JSON payloads.
200 — OK2xx SuccessStandard successful HTTP response for GET, PUT, or PATCH requests.
201 — Created2xx SuccessThe request has succeeded and a new resource was created (POST).
204 — No Content2xx SuccessRequest succeeded with no payload returned (common for DELETE).
301 — Moved Permanently3xx RedirectionTarget resource has been assigned a new permanent URI.
304 — Not Modified3xx RedirectionCached version is still valid; client does not need to re-download.
400 — Bad Request4xx Client ErrorMalformed syntax, invalid parameters, or payload validation failure.
401 — Unauthorized4xx Client ErrorMissing, invalid, or expired authentication credentials.
403 — Forbidden4xx Client ErrorAuthenticated caller lacks sufficient permission/role scope.
404 — Not Found4xx Client ErrorRequested URI endpoint or resource ID could not be located.
409 — Conflict4xx Client ErrorRequest conflicts with current resource state (e.g. duplicate email).
422 — Unprocessable Entity4xx Client ErrorSemantic errors in JSON payload (e.g. Zod validation failure).
429 — Too Many Requests4xx Client ErrorRate limit threshold exceeded; retry after specified backoff.
500 — Internal Server Error5xx Server ErrorUnhandled exception encountered by the server runtime.
502 — Bad Gateway5xx Server ErrorReverse proxy received invalid response from upstream origin service.
503 — Service Unavailable5xx Server ErrorServer temporarily overloaded or undergoing scheduled maintenance.
504 — Gateway Timeout5xx Server ErrorUpstream server failed to respond within reverse proxy timeout limit.
REST API HTTP Status Code Reference Guide
Browse RFC-standard HTTP status codes (2xx, 3xx, 4xx, 5xx) and generate API error documentation tables with standard JSON payloads.
How to Use the REST API HTTP Status Code Reference Guide
Input Content
Paste or compose your markdown or source data into the input editor.
Customize Settings
Select formatting options, syntax modes, or display options.
Copy or Download
Copy the processed output to your clipboard or download the generated file.
Key Features & Capabilities
Frequently Asked Questions
What is the difference between 401 Unauthorized and 403 Forbidden?
401 Unauthorized indicates the request lacks valid authentication credentials. 403 Forbidden indicates the server knows who the client is, but the client lacks permission to access the requested resource.
When should an API return 422 Unprocessable Entity versus 400 Bad Request?
400 Bad Request is reserved for syntactic errors (such as invalid JSON formatting). 422 Unprocessable Entity is used when the syntax is valid, but internal validation rules failed (e.g. invalid email format or password too short).
Related Markdown Tools
Markdown API Reference Generator
Build clean, structured REST API endpoint documentation with parameter tables, cURL request snippets, and JSON response models.
Table Generator
Interactive visual spreadsheet grid for designing and formatting Markdown pipe tables.
Markdown Incident Postmortem & Service Status Generator
Compile production outage postmortems, service status health matrices, and incident timeline tables for GitHub issues and DevOps wikis.
Markdown CLI Command Reference & Cheat Sheet Maker
Format command-line tool documentation cards with installation instructions, flag option tables, and runnable CLI syntax examples.