📖

HTTP Status Codes

Complete reference of HTTP status codes with descriptions and use cases.

HTTP status codesstatus code listHTTP response codeserror codes
100
Continue
Server received the request headers and client should proceed to send the request body.
101
Switching Protocols
Server is switching protocols as requested by the client.
102
Processing
Server has received and is processing the request, but no response is available yet.
103
Early Hints
Used to return some response headers before final HTTP message.
200
OK
Standard response for successful HTTP requests.
201
Created
Request has been fulfilled, resulting in the creation of a new resource.
202
Accepted
Request has been accepted for processing, but processing has not been completed.
204
No Content
Server successfully processed the request but returns no content.
206
Partial Content
Server is delivering only part of the resource due to a range header.
301
Moved Permanently
Resource has been permanently moved to a new URL.
302
Found
Resource temporarily resides under a different URI.
303
See Other
Response can be found under a different URI using GET method.
304
Not Modified
Resource has not been modified since the version specified by the request headers.
307
Temporary Redirect
Request should be repeated with another URI but future requests should still use the original URI.
308
Permanent Redirect
Request should be repeated with another URI and future requests should use the new URI.
400
Bad Request
Server cannot process the request due to client error.
401
Unauthorized
Authentication is required and has failed or has not been provided.
403
Forbidden
Server understood the request but refuses to authorize it.
404
Not Found
Requested resource could not be found on the server.
405
Method Not Allowed
Request method is not supported for the requested resource.
408
Request Timeout
Server timed out waiting for the request.
409
Conflict
Request could not be completed due to a conflict with the current state of the resource.
410
Gone
Resource is no longer available and will not be available again.
422
Unprocessable Entity
Request was well-formed but contained semantic errors.
429
Too Many Requests
User has sent too many requests in a given amount of time (rate limiting).
451
Unavailable For Legal Reasons
Resource is unavailable due to legal reasons.
500
Internal Server Error
Generic error message when server encounters an unexpected condition.
501
Not Implemented
Server does not recognize the request method or lacks the ability to fulfill it.
502
Bad Gateway
Server received an invalid response from an upstream server.
503
Service Unavailable
Server is currently unavailable (overloaded or down for maintenance).
504
Gateway Timeout
Server did not receive a timely response from an upstream server.
507
Insufficient Storage
Server is unable to store the representation needed to complete the request.

What is HTTP Status Codes?

HTTP Status Codes Reference provides a comprehensive list of all HTTP status codes with descriptions and common use cases. From 1xx informational to 5xx server errors, understand what each code means and when to use it.

Common Use Cases

API Development

Choose appropriate status codes for your API responses.

Debugging

Understand error codes returned by servers and APIs.

Learning

Learn HTTP protocol and proper status code usage.

Documentation

Reference for writing API documentation.

How to Use This Tool

  1. Browse status codes by category (1xx-5xx)
  2. Search for specific codes or keywords
  3. Click on a code to see detailed description
  4. Learn when to use each status code

Frequently Asked Questions

What is 200 OK?
200 indicates the request succeeded. It's the standard success response for GET, PUT, PATCH, or DELETE requests.
What is 404 Not Found?
404 means the requested resource doesn't exist. It's one of the most common error codes.
500 vs 502 vs 503?
500 is a generic server error, 502 means a gateway received an invalid response, 503 means the service is temporarily unavailable.