| 200 | OK – The request has succeeded . Request include GET and POST |
| 201 | Created – The request has succeeded and a new resource has been created as a result of it. This is typically the response sent after a PUT request. |
| 202 | Accepted – The request has succeeded and has been added to the queue, but the resource has not yet been created. This is typically the response sent after PUT and POST requests. |
| 204 | No Content – There is no content to send for this request. This is common for DELETE requests. |
| 400 | Bad Request – This response means that server could not understand the request due to invalid syntax. |
| 401 | Unauthorized – Authentication is needed to get requested response. This is similar to 403, but in this case, authentication is possible. |
| 403 | Forbidden – Client does not have access rights to the content so server is refusing to give proper response. |
| 404 | Not Found – Server cannot find the requested resource. |
| 405 | Method Not Allowed – The request method is known by the server but has been disabled and cannot be used. Double check your method type (i.e. GET, POST, PUT, DELETE) |
| 406 | Not Acceptable – You requested a format that isn’t json |
| 410 | Gone – The kitten requested has been removed from our servers |
| 418 | I’m a teapot |
| 429 | Too Many Requests – You’re requesting too many kittens! Slow down! |
| 500 | Internal Server Error – We had a problem with our server. Try again later. |
| 503 | Service Unavailable – We’re temporarially offline for maintanance. Please try again later. |
| 504 | Gateway Timeout – This error response is given when the server is acting as a gateway and cannot get a response in time. |
