HTTP Status Codes Reference
NEWComplete HTTP status codes reference with descriptions
Search
100
Continue
The server has received request headers and client should proceed.
101
Switching Protocols
The server is switching protocols as requested by the client.
200
OK
Standard response for successful HTTP requests.
201
Created
Request fulfilled and new resource has been created.
202
Accepted
Request accepted for processing, but not yet completed.
204
No Content
Server processed request successfully, no content to return.
206
Partial Content
Server delivering only part of the resource (byte serving).
301
Moved Permanently
Resource has been permanently moved to a new URL.
302
Found
Resource temporarily resides at a different URI.
304
Not Modified
Resource has not been modified since last request.
307
Temporary Redirect
Redirect should use same method (not change to GET).
308
Permanent Redirect
Permanent redirect preserving the request method.
400
Bad Request
Server cannot process request due to client error.
401
Unauthorized
Authentication required and has failed or not been provided.
403
Forbidden
Server understood request but refuses to authorize it.
404
Not Found
Requested resource could not be found on the server.
405
Method Not Allowed
HTTP method is not supported for this resource.
408
Request Timeout
Server timed out waiting for the request.
409
Conflict
Request conflicts with the current state of the resource.
410
Gone
Resource is permanently unavailable with no forwarding address.
422
Unprocessable Entity
Request well-formed but unable to process due to semantic errors.
429
Too Many Requests
User has sent too many requests in a given time (rate limiting).
500
Internal Server Error
Generic error — unexpected condition on the server.
501
Not Implemented
Server does not support the functionality required.
502
Bad Gateway
Server received an invalid response from an upstream server.
503
Service Unavailable
Server temporarily unable to handle requests.
504
Gateway Timeout
Server did not receive a timely response from an upstream server.
How to use HTTP Status Codes Reference
- 1
Search or scroll to find a specific status code (e.g. 404) or browse by category.
- 2
Each entry shows the code, its standard name, and what it means in practice.
- 3
Use the category grouping (1xx–5xx) to quickly understand what class of response you're dealing with.
Common use cases
- •Looking up what an unfamiliar status code returned by an API actually means
- •Deciding which status code to return from your own API for a given situation
- •Double-checking the difference between similar codes like 401 vs 403, or 301 vs 302