About the HTTP Status Codes
HTTP Status Codes is a searchable reference of the status codes servers return — what each one means and when to use it.
Search by number, name or description to quickly find the code you need.
🛰️HTTP Status Codes
Search and look up HTTP status codes
100
Continue
The server has received the request headers and the client should proceed to send the body.
101
Switching Protocols
The requester has asked the server to switch protocols.
200
OK
The request succeeded.
201
Created
The request succeeded and a new resource was created.
202
Accepted
The request has been accepted for processing, but is not complete.
204
No Content
The server successfully processed the request and is not returning any content.
206
Partial Content
The server is delivering only part of the resource due to a range header.
301
Moved Permanently
The resource has been permanently moved to a new URL.
302
Found
The resource resides temporarily under a different URL.
304
Not Modified
The cached version of the resource is still valid.
307
Temporary Redirect
The request should be repeated with another URL, keeping the method.
308
Permanent Redirect
The resource is now permanently located at another URL, keeping the method.
400
Bad Request
The server cannot process the request due to a client error.
401
Unauthorized
Authentication is required and has failed or not been provided.
403
Forbidden
The server understood the request but refuses to authorize it.
404
Not Found
The requested resource could not be found.
405
Method Not Allowed
The request method is not supported for the resource.
409
Conflict
The request conflicts with the current state of the server.
410
Gone
The resource is no longer available and will not be available again.
418
I'm a teapot
The server refuses to brew coffee because it is, permanently, a teapot.
422
Unprocessable Entity
The request was well-formed but had semantic errors (often validation).
429
Too Many Requests
The user has sent too many requests in a given time (rate limiting).
500
Internal Server Error
A generic error occurred on the server.
501
Not Implemented
The server does not support the functionality required.
502
Bad Gateway
The server received an invalid response from an upstream server.
503
Service Unavailable
The server is not ready to handle the request (overloaded or down).
504
Gateway Timeout
The upstream server failed to respond in time.
Common use cases
- Looking up what a status code means while debugging
- Choosing the right code for an API response
- Learning the HTTP status families (1xx–5xx)
- Explaining errors to teammates
How to use the HTTP Status Codes
- Type a code, name or keyword in the search box.
- Browse the matching status codes.
- Read the meaning and typical use.
Frequently asked questions
What is the difference between 401 and 403?
401 means you are not authenticated; 403 means you are authenticated but not allowed to access the resource.
When should I use 422?
Use 422 Unprocessable Entity when a request is well-formed but fails validation.
Is 301 or 302 better for redirects?
Use 301 for permanent moves (passes SEO value) and 302/307 for temporary redirects.