HTTP Status Codes — Complete Reference
Every HTTP status code explained — with causes, fix guidance, and Express.js / Next.js code examples. Click any code for the full reference page.
1xx
Informational
The request was received and processing continues.
2xx
Success
The request was successfully received, understood, and accepted.
200201202204206
OK
The request succeeded.
Created
A new resource was successfully created as a result of the request.
Accepted
The request has been accepted for processing, but processing has not been completed — and may not complete.
No Content
The request succeeded but there is no content to send in the response body.
Partial Content
The server is delivering only a portion of the resource due to a Range request from the client.
3xx
Redirection
Further action must be taken to complete the request.
301302304307308
Moved Permanently
The resource has been permanently moved to the URL given in the Location header.
Found
The resource is temporarily at a different URL.
Not Modified
The cached version of the resource is still current — the client should use its cached copy instead of downloading again.
Temporary Redirect
The resource is temporarily at the URL in the Location header.
Permanent Redirect
The resource has permanently moved to the URL in the Location header, and the HTTP method must not change.
4xx
Client Error
The request contains bad syntax or cannot be fulfilled by the server.
400401403404405408409410413415422429
Bad Request
The server cannot process the request because of a client-side error: malformed syntax, invalid message framing, or deceptive request routing.
Unauthorized
Authentication is required and the request lacks valid credentials.
Forbidden
The server understood the request but refuses to authorise it.
Not Found
The server cannot find the requested resource.
Method Not Allowed
The HTTP method used in the request is not supported for the target resource.
Request Timeout
The server timed out waiting for the request.
Conflict
The request conflicts with the current state of the resource.
Gone
The resource has been permanently deleted and is no longer available at the server.
Content Too Large
The request body is larger than the server is willing or able to process.
Unsupported Media Type
The server refuses to process the request because the media format indicated by the Content-Type header is not supported by the endpoint.
Unprocessable Entity
The request is well-formed (correct syntax, valid Content-Type) but contains semantic errors that prevent processing.
Too Many Requests
The client has sent too many requests in a given amount of time (rate limiting).
5xx
Server Error
The server failed to fulfil an apparently valid request.
500501502503504507
Internal Server Error
An unexpected condition was encountered and the server cannot fulfil the request.
Not Implemented
The server does not support the functionality required to fulfil the request.
Bad Gateway
The server, acting as a gateway or proxy, received an invalid response from an upstream server.
Service Unavailable
The server is not ready to handle the request.
Gateway Timeout
The server, acting as a gateway or proxy, did not receive a timely response from an upstream server.
Insufficient Storage
The server is unable to store the representation needed to complete the request.
Need to debug JWT tokens?
Decode and verify any JWT in your browser — no server, no logs.
Open JWT Debugger