Complete reference guide for HTTP status codes. Understand what each error means, what causes it, and how to fix it.
These errors indicate a problem with the request sent by the client. Check your request parameters, authentication, or URL.
The server cannot process the request due to malformed syntax or invalid parameters.
The request requires user authentication. The client must authenticate itself to get the requested response.
The server understood the request but refuses to authorize it. Authentication won't help.
The server can't find the requested resource. The URL may be incorrect or the resource was deleted.
The request method (GET, POST, etc.) is not supported for the requested resource.
The server timed out waiting for the request. The client didn't produce a request in time.
The request conflicts with the current state of the server resource.
The media format of the requested data is not supported by the server.
The server understands the content type but can't process the instructions—often due to validation errors.
The user has sent too many requests in a given time period (rate limiting).
These errors indicate a problem on the server side. The request was valid, but the server failed to fulfill it.
The server encountered an unexpected condition that prevented it from fulfilling the request.
The server, while acting as a gateway, received an invalid response from the upstream server.
The server is currently unable to handle the request due to maintenance or overload.
The server, while acting as a gateway, didn't receive a timely response from the upstream server.
DevConsole shows you exactly what's causing your API errors. Inspect headers, decode tokens, and replay failed requests.
Get DevConsole Pro