API
HTTP Status Code Reference
Search HTTP status codes by number or name and get what each one actually means - including distinctions like 401 vs 403 that are easy to mix up.
21 status codes match.
OK
The request succeeded.
Created
The request succeeded and a new resource was created.
Accepted
The request was accepted for processing, but isn't complete yet.
No Content
The request succeeded, no content to return.
Moved Permanently
The resource has permanently moved to a new URL.
Found
The resource temporarily lives at a different URL.
Not Modified
The cached version is still valid, no need to re-fetch.
Temporary Redirect
Like 302, but guarantees the method and body are not changed on redirect.
Permanent Redirect
Like 301, but guarantees the method and body are not changed on redirect.
Bad Request
The server can't process the request due to a client error (malformed syntax, invalid data).
Unauthorized
Authentication is required and has failed or not been provided.
Forbidden
The server understood the request but refuses to authorize it - unlike 401, re-authenticating won't help.
Not Found
The server can't find the requested resource.
Method Not Allowed
The HTTP method used isn't supported for this resource.
Conflict
The request conflicts with the current state of the resource.
Unprocessable Entity
The request is well-formed but contains semantic errors.
Too Many Requests
Rate limit exceeded - the client should back off before retrying.
Internal Server Error
A generic error occurred on the server.
Bad Gateway
The server, acting as a gateway, got an invalid response from the upstream server.
Service Unavailable
The server is temporarily unable to handle the request (overloaded or down for maintenance).
Gateway Timeout
The server, acting as a gateway, didn't get a response in time from the upstream server.
This is one question. ArchSetu answers it for a whole repository.
Call graph, dead code, blast radius and a health score, in about a minute.
Related tools
All API tools →Was this tool helpful?