Essentials
Response Codes
We use standard HTTP response codes to indicate request status.
Response Code Categories
- 2xx: Success
- 4xx: Client-side errors
- 5xx: Server-side errors
Common Response Codes
Code | Status | Description |
---|---|---|
200 | OK | Everything’s good—your request worked perfectly! |
201 | Created | Nice job! A new resource has been successfully created. |
202 | Accepted | Got it! Your request is in the queue for processing. |
204 | No Content | Done and dusted, but nothing to show for it—no content returned. |
400 | Bad Request | Oops! Something’s wrong with your request. Check your parameters. |
401 | Unauthorized | Access denied—are you sure you’ve logged in? |
403 | Forbidden | Nope, you can’t do that—permission denied. |
404 | Not Found | Lost? The resource you’re looking for doesn’t exist. |
405 | Method Not Allowed | Wrong move—this method isn’t allowed here. |
409 | Conflict | It’s complicated—your request conflicts with the current state. |
422 | Unprocessable Entity | You tried, but something doesn’t add up. Fix those semantic issues! |
429 | Too Many Requests | Slow down! You’re sending too many requests—take a breather. |
500 | Server Error | Yikes! Something went wrong on our side—hang tight. |
Was this page helpful?