# HTTP response codes

The Quable Team

●

Published 2023-09-30

200s http codes
400s http codes
500s http codes

Quable PIM API uses conventional HTTP response codes to indicate the success or failure of an API request.

In general:

Codes in the 2OO's range indicate success.
Codes in the 400's range indicate an error based on the information provided in the request (client errors). Errors can be caused by many factors, such as invalid parameters, lack of authentication / permission or rate limits.
Codes in the 500's range indicate servor errors.

You can find the details of http codes on this page. We provide a list of the most frequent ones below.

Http code	Description	Use case
200 Ok	The request was successful	Typically the response to a successul GET request or content successfully updated through PUT requests
201 Created	The ressource was successfully created	Typical response to successful POST requests
204 No content	The request succeeded but there is nothing to show	Typical response to successful DELETE requests

Http code	Description
400 Bad Request	The request contains errors
401 Unauthorized	The request lacks valid authentication credentials
403 Forbidden	The request uses credentials that are not authorized for access
404 Not found	The requested resource could not be found
405 Method Not Allowed	This can be that the method is not supported or relevant to the requested resource OR that the use does not have permission to access the resource
409 Conflict	The request conflicts with current data
422 Unprocessable Entity	The server understands the content type of the request entity, and the syntax of the requested entity is correct, but it was unable to process the contained instructions (this request should not be repeated without modification)
429 Too Many Requests	Too many requests have been sent within a specific amount of time. In this case, your applications must reduce the number of calls or wait a few seconds before resuming calls.

The volume of allowed API calls is detailed in your Quable PIM contract.

Http code	Description
500 Internal Error	The server has encountered a situation it does not know how to handle.
503 Service Unavailable	The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded.
504 Gateway Timeout	This error response is given when the server is acting as a gateway and cannot get a response in time.
505 Http Version Not Supported	The HTTP version used in the request is not supported by the server.