HTTP Status Codes
What every HTTP response code means, why it happens and how to fix it. Pair this with the free HTTP header checker and uptime checker.
1xx Informational
100
ContinueThe server has received the request headers and the client should proceed to send the body.
101
Switching ProtocolsThe server agrees to switch to the protocol requested by the client in the Upgrade header.
102
ProcessingThe server has accepted the request but has not finished processing it (WebDAV).
103
Early HintsLets the server send preliminary headers (such as Link preload) before the final response.
2xx Success
200
OKThe request succeeded and the response contains the requested data.
201
CreatedThe request succeeded and a new resource was created.
202
AcceptedThe request was accepted for processing but is not complete yet.
203
Non-Authoritative InformationThe response was modified by a transforming proxy and may differ from the origin.
204
No ContentThe request succeeded and there is no body to return.
205
Reset ContentTells the client to reset the document view, such as clearing a form.
206
Partial ContentThe server is delivering only part of the resource because of a Range header.
207
Multi-StatusConveys multiple status codes for a batch operation (WebDAV).
3xx Redirection
301
Moved PermanentlyThe resource has a new permanent URL and clients should use it from now on.
302
FoundThe resource is temporarily at a different URL.
303
See OtherThe response to the request can be found at another URL using GET.
304
Not ModifiedThe cached copy of the resource is still valid so no body is sent.
307
Temporary RedirectThe resource is temporarily at another URL and the method and body must not change.
308
Permanent RedirectThe resource has moved permanently and the method and body must not change.
4xx Client errors
400
Bad RequestThe server cannot process the request because it is malformed or invalid.
401
UnauthorizedAuthentication is required or the supplied credentials are invalid.
402
Payment RequiredReserved for digital payment systems; used by some APIs when a plan limit is reached.
403
ForbiddenThe server understood the request but refuses to authorise it.
404
Not FoundThe server cannot find the requested resource.
405
Method Not AllowedThe HTTP method is not supported for this resource.
406
Not AcceptableThe server cannot produce a response matching the Accept headers sent.
408
Request TimeoutThe server timed out waiting for the request.
409
ConflictThe request conflicts with the current state of the resource.
410
GoneThe resource was intentionally removed and will not return.
411
Length RequiredThe server requires a Content-Length header.
412
Precondition FailedA precondition in the request headers evaluated to false.
413
Payload Too LargeThe request body is larger than the server allows.
414
URI Too LongThe request URL is longer than the server will process.
415
Unsupported Media TypeThe server does not support the request Content-Type.
418
I'm a teapotAn April Fools' joke status from RFC 2324 meaning the server refuses to brew coffee because it is a teapot.
422
Unprocessable ContentThe request is well-formed but contains semantic validation errors.
423
LockedThe resource is locked (WebDAV).
425
Too EarlyThe server is unwilling to risk processing a request that might be replayed.
426
Upgrade RequiredThe client must switch to a different protocol.
428
Precondition RequiredThe server requires the request to be conditional.
429
Too Many RequestsThe client has sent too many requests in a given time (rate limiting).
431
Request Header Fields Too LargeThe headers are too large for the server to process.
451
Unavailable For Legal ReasonsThe resource is blocked because of a legal demand.
5xx Server errors
500
Internal Server ErrorA generic error meaning the server hit an unexpected condition.
501
Not ImplementedThe server does not support the functionality needed to fulfil the request.
502
Bad GatewayA gateway or proxy received an invalid response from the upstream server.
503
Service UnavailableThe server is temporarily unable to handle the request.
504
Gateway TimeoutA gateway did not receive a timely response from the upstream server.
505
HTTP Version Not SupportedThe server does not support the HTTP version used in the request.
507
Insufficient StorageThe server cannot store the representation needed to complete the request (WebDAV).
508
Loop DetectedThe server detected an infinite loop while processing the request (WebDAV).
511
Network Authentication RequiredThe client needs to authenticate to gain network access.
Get alerted when your API starts returning errors
Monitor any endpoint and be notified the moment it returns the wrong status code.