HTTP Response Codes

Every HTTP request sent to the server should generate a response code. There are literally dozens of possible response codes, but the tables below list the most common ones you're likely to encounter.

Response codes generally represent either success or failure of the requested action.

Success Codes

200OKThe request has succeeded. The information returned with the response is dependent on the method used in the request.
201CreatedThe request has been fulfilled and resulted in a new resource being created.
204No ContentThe server has fulfilled the request but does not need to return an entity-body.

Error Codes

400Bad RequestThe request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
401UnauthorizedThe request requires user authentication.
403ForbiddenThe server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated.
404Not FoundThe server has not found anything matching the Request-URI.
409ConflictThe request could not be completed due to a conflict with the current state of the resource.
500Internal Server ErrorThe server encountered an unexpected condition which prevented it from fulfilling the request.
504Gateway TimeoutThe server, while acting as a gateway or proxy, did not get a response in time from the upstream server that it needed in order to complete the request.
524Timeout ErrorThis is a 100 sec timeout error. These errors are typically transient. If you continue to receive them on a regular basis or for a large period of time, contact our support team.

For a comprehensive list of response codes, see the MDN Web Docs Page