← Back to home
HTTP Status Codes
Browse common HTTP response status codes with clear explanations and examples.
41 results — select a status code to view details
100 — Continue
The server received the request headers and the client should continue sending the request body.
101 — Switching Protocols
The server is switching protocols as requested by the client.
200 — OK
The request was successful and the server returned the expected response.
201 — Created
The request succeeded and a new resource was created on the server.
202 — Accepted
The request has been accepted for processing, but the work has not finished yet.
204 — No Content
The request was successful, but the server returned no response body.
206 — Partial Content
The server returned only part of the requested resource, usually because the client asked for a specific byte range.
300 — Multiple Choices
The request has multiple possible responses and the client can choose between them.
301 — Moved Permanently
The requested resource has been permanently moved to a new URL.
302 — Found
The resource is temporarily available under a different URL.
303 — See Other
The server tells the client to fetch another resource using a GET request.
304 — Not Modified
The resource has not changed, so the client can use its cached version.
307 — Temporary Redirect
The resource is temporarily available at another URL, and the original request method should be preserved.
308 — Permanent Redirect
The resource has been permanently moved, and the original request method should be preserved.
400 — Bad Request
The server could not understand the request because it was malformed or invalid.
401 — Unauthorized
Authentication is required and the current request does not include valid credentials.
403 — Forbidden
The server understood the request but refuses to authorize it.
404 — Not Found
The server could not find the requested resource.
405 — Method Not Allowed
The request method is not allowed for the requested resource.
406 — Not Acceptable
The server cannot generate a response matching the values in the request Accept headers.
408 — Request Timeout
The server timed out waiting for the client to complete the request.
409 — Conflict
The request could not be completed because it conflicts with the current state of the resource.
410 — Gone
The requested resource is no longer available and is not expected to come back.
411 — Length Required
The server requires a Content-Length header but the request did not include one.
412 — Precondition Failed
The request failed because one or more preconditions in the request headers were not met.
413 — Payload Too Large
The server refused the request because the request body is too large.
414 — URI Too Long
The request URI is longer than the server is willing to process.
415 — Unsupported Media Type
The server refused the request because the payload format is not supported.
418 — I'm a teapot
The server refuses the attempt to brew coffee with a teapot. This is an Easter egg status code from an April Fools' RFC.
422 — Unprocessable Entity
The server understood the request format, but the request data could not be processed because of validation or semantic errors.
423 — Locked
The resource is locked and cannot be modified right now.
424 — Failed Dependency
The request failed because it depended on another request that failed first.
426 — Upgrade Required
The server requires the client to switch to a different protocol before continuing.
428 — Precondition Required
The server requires the request to be conditional, usually to avoid conflicting updates.
429 — Too Many Requests
The client has sent too many requests in a given amount of time and has been rate limited.
431 — Request Header Fields Too Large
The server refused the request because one or more request headers are too large.
451 — Unavailable For Legal Reasons
The resource is unavailable because of legal or regulatory restrictions.
500 — Internal Server Error
The server encountered an unexpected error and could not complete the request.
502 — Bad Gateway
The server received an invalid response from an upstream server.
503 — Service Unavailable
The server is temporarily unable to handle the request.
504 — Gateway Timeout
The server did not receive a response from an upstream server in time.