Quick reference for all HTTP status codes. Search by code number or description.
The server has received the request headers and the client should proceed to send the request body.
The requester has asked the server to switch protocols and the server has agreed to do so.
The request has succeeded.
The request has been fulfilled and resulted in a new resource being created.
The request has been accepted for processing, but the processing has not been completed.
The server successfully processed the request but is not returning any content.
The server is delivering only part of the resource due to a range header sent by the client.
The URL of the requested resource has been changed permanently.
The URI of requested resource has been changed temporarily.
The resource has not been modified since the version specified by the request headers.
The request should be repeated with another URI but future requests should still use the original URI.
The request and all future requests should be repeated using another URI.
The server cannot process the request due to something perceived to be a client error.
Authentication is required and has failed or has not yet been provided.
The server understood the request but refuses to authorize it.
The requested resource could not be found on the server.
The request method is known by the server but not supported by the target resource.
The server timed out waiting for the request.
The request could not be processed because of conflict in the current state of the resource.
The resource requested is no longer available and will not be available again.
The request is larger than the server is willing or able to process.
The media format of the requested data is not supported by the server.
The request was well-formed but unable to be followed due to semantic errors.
The user has sent too many requests in a given amount of time.
The server has encountered a situation it doesn't know how to handle.
The server received an invalid response from the upstream server.
The server is not ready to handle the request (overloaded or down for maintenance).
The server is acting as a gateway and cannot get a response in time.
Enter a status code or keyword.
Matching codes are displayed.
Read detailed descriptions and use cases.
Use the HTTP Status Codes reference when debugging API responses, designing REST APIs, or troubleshooting web application errors. It is essential for backend developers choosing the correct status code for each endpoint response. Frontend developers reference it when handling API errors to display appropriate user messages based on the status code received.
HTTP status codes are grouped into five classes: 1xx Informational (request received, processing), 2xx Success (request accepted and processed), 3xx Redirection (further action needed), 4xx Client Error (bad request or unauthorized), and 5xx Server Error (server failed to fulfill a valid request). Understanding these classes helps quickly categorize API responses during debugging.
200 OK is the standard success response indicating that the request was received, understood, and processed successfully. It is the most common status code you will encounter when everything works correctly. The response body typically contains the requested resource data. Different HTTP methods return different content — GET returns data, POST returns the created resource.
404 Not Found indicates that the server cannot find the requested resource at the specified URL. This could mean the URL is incorrect, the resource has been deleted, or the route does not exist. It is one of the most well-known HTTP status codes and is different from 410 Gone, which explicitly indicates a permanently removed resource.
