The request was received, continuing process.
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 action was successfully received, understood, and accepted.
Standard response for successful HTTP requests.
The request has been fulfilled, resulting in the creation of a new resource.
The request has been accepted for processing, but the processing has not been completed.
The server successfully processed the request and is not returning any content.
The server is delivering only part of the resource due to a range header sent by the client.
Further action must be taken in order to complete the request.
This and all future requests should be directed to the given URI.
The resource was found, but at a different URI (temporary redirect).
Indicates that the resource has not been modified since the version specified by the request headers.
The request should be repeated with another URI; however, future requests should still use the original URI.
The request and all future requests should be repeated using another URI.
The request contains bad syntax or cannot be fulfilled.
The server cannot or will not process the request due to an apparent client error.
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
The request was valid, but the server is refusing action.
The requested resource could not be found but may be available in the future.
A request method is not supported for the requested resource.
The server timed out waiting for the request.
Indicates that the request could not be processed because of conflict in the current state of the resource.
The user has sent too many requests in a given amount of time.
The server failed to fulfill an apparently valid request.
A generic error message, given when an unexpected condition was encountered.
The server either does not recognize the request method, or it lacks the ability to fulfill the request.
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
The server is currently unavailable (because it is overloaded or down for maintenance).
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
Covers common 1xx through 5xx status codes.
Browse by informational, success, redirect, client, or server errors.
Find status codes instantly with keyword search.
All lookups happen locally in your browser.
Identify why requests fail by interpreting status codes.
Map codes to user-facing messages in apps.
Reference accurate descriptions in API docs.
Analyze logs to spot recurring status patterns.
Type a status code or browse by category.
Review the description and common usage.
Use the info to diagnose API or server responses.