Response Codes

Announcement Box

Responses are grouped into:

Informational Responses - (100 - 199)
Successful Responses - (200 - 299)
Redirects - (300 - 399)
Client Errors - (400 - 499)
Server Errors - (500 - 599)

ERROR CODE	DESCRIPTION	USE-CASE
200 (OK)	The server successfully processed the request, and the response is as expected.	It is the standard response for successful HTTP requests and indicates that the request was received, understood, and processed.
400(Bad Request)	indicates that the client's request to the server is malformed or contains invalid syntax.	The client's request is missing required parameters, contains parameters with incorrect values, or includes parameters that the server does not recognize.
401 (Unauthorized)	The client's request lacks valid authentication credentials or the provided credentials are insufficient.	It is used when a user's login session has expired, their credentials are invalid, or the resource requires authentication, and none was provided.
404 (Not Found)	The requested resource could not be found on the server.	This status code is commonly returned when a URL or resource path does not exist on the server.
405(Method Not Allowed)	indicates that the HTTP method (GET, POST, PUT, DELETE, etc.) used in the request is not supported by the target resource.	The client may be sending an incorrect or unsupported HTTP method due to a coding or configuration error.
408 (Request Timeout)	The server did not receive a complete request from the client within the server's specified timeout period	It can occur when the client takes too long to send a request, and the server times out waiting for the request to complete.
429 (Too Many Requests)	The client has made too many requests in a given time frame, exceeding rate limits imposed by the server	It is used to throttle or limit the number of requests a client can make to prevent abuse or overloading the server.
500 (Internal Server Error)	A generic server error occurred that prevented it from fulfilling the client's request.	It indicates that something unexpected went wrong on the server, often due to a server misconfiguration or an unhandled exception.