Developer
All toolsHTTP Status Codes
Browse and search every HTTP status code with descriptions.
HTTP status codes
100ContinueInitial request received, client should continue
101Switching ProtocolsServer is switching protocols as requested
200OKStandard successful response
201CreatedResource was successfully created
202AcceptedRequest accepted but not yet processed
204No ContentSuccess, but no response body
206Partial ContentRange request served partially
301Moved PermanentlyResource permanently moved to new URL
302FoundTemporary redirect
304Not ModifiedCached version is still valid
307Temporary RedirectSame method must be used at new URL
308Permanent RedirectPermanent move with method preserved
400Bad RequestMalformed or invalid request
401UnauthorizedAuthentication required
403ForbiddenAuthenticated but not allowed
404Not FoundResource does not exist
405Method Not AllowedHTTP method not supported here
408Request TimeoutClient took too long to send request
409ConflictRequest conflicts with current state
410GoneResource removed permanently
413Payload Too LargeRequest body too large
415Unsupported Media TypeBody format not supported
418I'm a teapotApril fools RFC 2324
422Unprocessable EntitySemantic validation failed
429Too Many RequestsRate limit exceeded
500Internal Server ErrorGeneric server error
501Not ImplementedFeature not implemented
502Bad GatewayUpstream server returned bad response
503Service UnavailableServer overloaded or down for maintenance
504Gateway TimeoutUpstream server did not respond in time
Frequently asked questions
- What's the difference between 401 Unauthorized and 403 Forbidden?
- 401 means the request lacks valid credentials and the client should authenticate, while 403 means the credentials are recognized but the resource is off-limits. Sending new credentials will not help a 403.
- When should an API return 422 versus 400?
- 400 Bad Request signals malformed syntax the server could not parse, while 422 Unprocessable Entity means the syntax was fine but the values failed business validation. Many APIs use 422 for form errors with a per-field detail object.
- What does a 304 Not Modified response actually return?
- A 304 has no body - the server is telling the client that its cached copy is still valid based on ETag or Last-Modified headers. The client reuses the previously stored response, saving bandwidth.