Searchable list of standard HTTP response codes.
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.
The request has succeeded.
The request has succeeded and a new resource has been created as a result.
The request has been received but not yet acted upon.
The server successfully processed the request and is not returning any content.
The URL of the requested resource has been changed permanently.
The URI of requested resource has been changed temporarily.
Indicates the resource has not been modified since the version specified by the request headers.
The server sends this response to direct the client to get the requested resource at another URI with same method.
The server sends this response to direct the client to get the requested resource at another URI with same method.
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 user might not have the necessary permissions.
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.
The user has sent too many requests in a given amount of time.
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
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.
Skip months of boilerplate. License a production-ready Next.js template or commission our engineering team to build your custom software or AI workflow.