The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, too large size, invalid request message framing, or deceptive request routing).
Indicates that the request could not be processed because of conflict in the request, such as an edit conflict between multiple simultaneous updates.
The request has been fulfilled, resulting in the creation of a new resource.
The request was a valid request, but the server is refusing to respond to it. The user might be logged in but does not have the necessary permissions for the resource.
The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
The server successfully processed the request and is not returning any content.
Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action.
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource.
HTTP Status Codes
This is a list of Hypertext Transfer Protocol (HTTP) response status codes
http://www.restapitutorial.com/httpstatuscodes.html