HTTP Tool
HTTP Status Codes Reference
Quick reference for common HTTP status codes used in APIs.
HTTP Status Codes
HTTP status codes are standard response codes returned by servers to indicate the result of an HTTP request.
Common HTTP status codes
Search by code, label, category, or description.
| Code | Label | Category | Description |
|---|---|---|---|
| 200 | OK | Success | Request succeeded. |
| 201 | Created | Success | Resource created successfully. |
| 204 | No Content | Success | Request succeeded with no response body. |
| 301 | Moved Permanently | Redirection | Resource moved to a new permanent URL. |
| 302 | Found | Redirection | Resource temporarily available at another URL. |
| 304 | Not Modified | Redirection | Cached resource is still valid. |
| 400 | Bad Request | Client Error | Malformed request syntax or invalid parameters. |
| 401 | Unauthorized | Client Error | Authentication is required or failed. |
| 403 | Forbidden | Client Error | Server understood but refuses to authorize. |
| 404 | Not Found | Client Error | Requested resource does not exist. |
| 409 | Conflict | Client Error | Request conflicts with current resource state. |
| 422 | Unprocessable Content | Client Error | Request syntax is valid but semantic validation failed. |
| 429 | Too Many Requests | Client Error | Rate limit exceeded. |
| 500 | Internal Server Error | Server Error | Generic server-side error. |
| 502 | Bad Gateway | Server Error | Invalid response from upstream server. |
| 503 | Service Unavailable | Server Error | Service temporarily unavailable. |
| 504 | Gateway Timeout | Server Error | Upstream server did not respond in time. |
Using status codes in REST APIs
Use precise status codes to communicate success, validation errors, authentication issues, conflicts, and server failures clearly for API clients.
Overview
Search common response codes and their intent to improve API consistency and speed up debugging across teams.
Examples
Success code lookup
Input
201Output
Created - resource created successfully.Client error lookup
Input
422Output
Unprocessable Content - semantic validation failed.Use cases
- Choose correct response codes in REST endpoints.
- Explain unexpected responses during debugging.
- Align code usage in API docs and implementation.
FAQ
Does this include every HTTP status code?
It focuses on commonly used API status codes.
Can I search by description?
Yes. Search matches code, label, category, and description.
Is this suitable for API design reviews?
Yes. It helps validate code choices during design discussions.
Does the tool recommend one code automatically?
No. It provides reference information only.