📡
Search & Filter HTTP Codes
100Informational
Continue
The server has received the request headers and the client should proceed to send the request body.
Common Use Case: Typically used in POST/PUT requests with 'Expect: 100-continue' header.
101Informational
Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to do so.
Common Use Case: Used when upgrading HTTP connection to WebSocket standard.
200Success
OK
Standard response for successful HTTP requests. The actual response will depend on the request method.
Common Use Case: Standard successful GET, PUT, or POST request payload delivery.
201Success
Created
The request has been fulfilled, resulting in the creation of a new resource.
Common Use Case: Sent as confirmation after a successful POST request creating a new user or entity.
202Success
Accepted
The request has been accepted for processing, but the processing has not been completed.
Common Use Case: Commonly used in asynchronous queuing or background jobs.
204Success
No Content
The server successfully processed the request and is not returning any content.
Common Use Case: Often returned on a successful DELETE request or preflight OPTIONS request.
301Redirect
Moved Permanently
This and all future requests should be directed to the given URI.
Common Use Case: SEO URL redirection or shifting from HTTP to HTTPS URL formats.
302Redirect
Found (Temporary Redirect)
Tells the client to look at another temporary URL, keeping original URL for future requests.
Common Use Case: Redirecting unauthenticated users to a login page temporarily.
304Redirect
Not Modified
Indicates that the resource has not been modified since the version specified by the request headers.
Common Use Case: Saves bandwidth by serving assets straight from local client browser cache.
400Client Error
Bad Request
The server cannot or will not process the request due to an apparent client error.
Common Use Case: Returned when request parameters fail schema validation or contain malformed JSON.
401Client Error
Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed.
Common Use Case: Sent when OAuth access token or basic authentication header is invalid or missing.
403Client Error
Forbidden
The request was valid, but the server is refusing action. The user might not have the necessary permissions.
Common Use Case: A standard logged-in user trying to access administrator-only dashboard endpoints.
404Client Error
Not Found
The requested resource could not be found but may be available in the future.
Common Use Case: User visits a URL routing slug that does not exist in your database or static paths.
405Client Error
Method Not Allowed
A request method is not supported for the requested resource.
Common Use Case: Attempting a POST request on a route that only supports GET.
409Client Error
Conflict
Indicates that the request could not be processed because of conflict in the current state of the resource.
Common Use Case: User registers with an email address that is already active in the system.
422Client Error
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
Common Use Case: Missing a required form field in an API post payload.
429Client Error
Too Many Requests
The user has sent too many requests in a given amount of time ('rate limiting').
Common Use Case: An API client calling endpoints past their allocated hourly rate limit threshold.
500Server Error
Internal Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
Common Use Case: Backend code crashes due to unhandled promise rejections or database service failure.
502Server Error
Bad Gateway
The server, while acting as a gateway or proxy, received an invalid response from the upstream server.
Common Use Case: Nginx proxy cannot reach the underlying Express or Node application port.
503Server Error
Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance).
Common Use Case: Temporary downtime during code deployments or handling peak server traffic spikes.
504Server Error
Gateway Timeout
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server.
Common Use Case: The upstream database query takes longer to execute than Nginx's connection timeout limit.
🚀 Interactive Endpoint Mock Generator
Select any status code card above (currently targeting 404) and pick your backend language to generate the code block.
// Node.js (Express.js)
app.get('/api/resource', (req, res) => {
res.status(404).json({
error: "Not Found",
message: "The requested resource could not be found but may be available in the future."
});
});