HTTP Status Codes | 200, 404, 500 Explained
HTTP API Debug Web
When calling an API, do you sometimes forget what a status code means? Here’s a quick reference for common codes.
2xx: Success
- 200 OK — Request succeeded. GET data, PUT update, etc.
- 201 Created — Resource created. Often returned after POST.
- 204 No Content — Success with no response body. Common after DELETE.
4xx: Client Error
- 400 Bad Request — Invalid request. Check JSON syntax, required params.
- 401 Unauthorized — Auth required. Missing or invalid token. Check Authorization header.
- 403 Forbidden — Authenticated but not authorized for this resource.
- 404 Not Found — Resource doesn’t exist. Wrong URL or deleted.
- 422 Unprocessable Entity — Valid format but invalid content. Validation errors.
5xx: Server Error
- 500 Internal Server Error — Server-side error. Check server logs.
- 502 Bad Gateway — Gateway/proxy received invalid response from upstream.
- 503 Service Unavailable — Temporarily down. Overload or maintenance.
Debug Tip
4xx = fix your request. 5xx = check the server. Use the Network tab and response body for clues.