HTTP Status Codes
A practical reference for HTTP responses: search registered codes, copy handling examples, inspect a browser-visible response, and choose the right result for an API.
{{ item.code }} {{ item.name }} {{ item.descriptionEn }}
Only the endpoint you enter receives this request. The browser must be allowed by that endpoint’s CORS policy.
Headers
Sent URL-encoded as application/x-www-form-urlencoded, the same shape a browser <form> submission produces. Preview: {{ formBodyPreview || '(empty)' }}
{{ client.bodyType === 'xml' ? 'Invalid XML' : 'Invalid JSON' }}: {{ requestBodyState.error }}
Sent with Content-Type: {{ BODY_CONTENT_TYPES[client.bodyType] }} unless a header above already sets Content-Type.
{{ client.error }}
Response headers
{{ client.response.headers.length }}{{ header.value }}No response headers are visible to the browser.
Response body
{{ client.response.body || '(empty response body)' }}CRUD responses
| Operation | Usual response | Why |
|---|---|---|
| Create | Return the new resource or a Location header. | |
| Read | Return the representation. | |
| Update | or | Return the representation only when the client needs it. |
| Delete | The delete completed without a response body. |
Authentication & authorization
WWW-Authenticate when required.Validation & limits
Retry-After whenever you know the delay.Redirects & caching
Server and gateway failures
Retry-After when possible.About this tool
This reference tracks permanent entries in the IANA HTTP Status Code Registry, including WebDAV and widely used extension codes such as 429 and 451. It deliberately labels historical or unused values so they are not mistaken for recommended API behavior.
Browsers enforce CORS, so a cross-origin endpoint must explicitly permit your page to read its response. The client shows only headers the browser exposes.
The request body isn't assumed to be JSON: pick JSON (validated as you type), Form URL-encoded (a structured field list, sent the same way a browser <form> submit would encode it), Plain text (no validation — the endpoint decides what's valid), or XML (validated with the browser's own DOMParser). Whichever type is selected sets a matching default Content-Type header, but an explicit Content-Type you add above always wins — useful for deliberately testing how an endpoint reacts to a mismatched content type.
Privacy: the HTTP client runs entirely in your browser. It sends a request only to the URL you enter and does not upload request or response data to this site.
