SearchableAll CategoriesUse Cases
100
Continue
The server has received the request headers and the client should proceed to send the request body.
101
Switching Protocols
The server is switching protocols as requested by the client (e.g., upgrading to WebSocket).
103
Early Hints
Used to return some response headers before final HTTP message. Allows preloading resources.
200
OK
The request has succeeded. Standard response for successful HTTP requests.
201
Created
The request has been fulfilled, resulting in the creation of a new resource.
202
Accepted
The request has been accepted for processing, but the processing has not been completed.
204
No Content
The server successfully processed the request, but is not returning any content.
206
Partial Content
The server is delivering only part of the resource due to a range header sent by the client.
301
Moved Permanently
The resource has been permanently moved to a new URL. Search engines update their links.
302
Found
The resource is temporarily at a different URL. The client should continue using the original URL.
303
See Other
The response can be found at a different URL using a GET request.
304
Not Modified
The resource has not been modified since the last request. Used for caching.
307
Temporary Redirect
The request should be repeated at another URL, but future requests should still use the original.
308
Permanent Redirect
The resource has permanently moved. Similar to 301 but the method must not change.
400
Bad Request
The server cannot process the request due to invalid syntax or malformed request.
401
Unauthorized
Authentication is required. The client must provide valid credentials.
403
Forbidden
The server understood the request but refuses to authorize it.
404
Not Found
The requested resource could not be found on the server.
405
Method Not Allowed
The HTTP method used is not supported for the requested resource.
408
Request Timeout
The server timed out waiting for the request from the client.
409
Conflict
The request conflicts with the current state of the server (e.g., duplicate resource).
410
Gone
The resource is no longer available and will not be available again.
413
Payload Too Large
The request entity is larger than limits defined by the server.
415
Unsupported Media Type
The media format of the request data is not supported by the server.
422
Unprocessable Entity
The request was well-formed but could not be processed due to semantic errors.
429
Too Many Requests
The user has sent too many requests in a given amount of time (rate limiting).
500
Internal Server Error
A generic error message when the server encounters an unexpected condition.
501
Not Implemented
The server does not support the functionality required to fulfill the request.
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, often due to maintenance or overload.
504
Gateway Timeout
The server did not receive a timely response from the upstream server.
Love this tool? Explore 999+ more
Free online tools for images, PDFs, text, code, and more. All running in your browser.
Explore All Tools