HTTP Status Code

HTTP defines a list of status codes that can be returned from your service or web API and these status can help to client API to understand response and route or process it accordingly.

There are few series, which can tell us the high level meaning of HTTP status code

• 2xx Success – this series of status code tells that request is successfully accepted and processed
• 3xx Redirection - this series of status code tells that client must take additional action to complete the request.
• 4xx Client errors - this series of status code tells that there is error due to the client
• 5xx Server errors - this series of status code tells that server failed to fulfil a request

There are few important HTTP status codes

2xx Success

• 200 OK - Response to a successful GET, PUT, PATCH or DELETE. Can also be used for a POST that doesn't result in a creation.
• 201 Created - Response to a POST that results in a creation. Should be combined with a Location header pointing to the location of the new resource
• 204 No Content - Response to a successful request that won't be returning a body (like a DELETE request)

3xx Redirection

• 304 Not Modified - Used when HTTP caching headers are in play
• 400 Bad Request - The request is malformed, such as if the body does not parse
• 401 Unauthorized - When no or invalid authentication details are provided. Also useful to trigger an auth popup if the API is used from a browser

4xx Client errors

• 403 Forbidden - When authentication succeeded but authenticated user doesn't have access to the resource
• 404 Not Found - When a non-existent resource is requested
• 405 Method Not Allowed - When an HTTP method is being requested that isn't allowed for the authenticated user
• 410 Gone - Indicates that the resource at this end point is no longer available. Useful as a blanket response for old API versions
• 415 Unsupported Media Type - If incorrect content type was provided as part of the request
• 422 Unprocessable Entity - Used for validation errors
• 429 Too Many Requests - When a request is rejected due to rate limiting
• 5xx Server errors
• 500 Internal Server Error - A generic error message for unexpected error
• 501 Not Implemented - The server either does not recognize the request method, or it lacks the ability to fulfil the request. Usually this implies future availability (e.g., a new feature of a web-service API)

For more information, visit on Wikipedia url

Thanks for visiting !!