HTTP Response Codes

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

In general:

  • Codes in the 2xx range indicate success.

  • Codes in the 4xx range indicate an error based on the information provided in the request. Errors can be caused by many factors, such as invalid parameters, authentication errors, and rate limits.

2xx Codes

HTTP CodeDescription
200 OkThe request was successful.

Typicaly responding to:
  • A first successful GET request, or
  • Content successfully updated via PUT/PATCH requests.
201 CreatedThe resource was created.

Typically responding to:
  • PUT and POST requests.
204 No ContentThe request succeeded but there is nothing to show.

Typically responding to
  • A successful DELETE request.

4xx Codes

HTTP CodeDescription
400 Bad RequestThe request is malformed.
401 UnauthorizedThe request lacks valid authentication credentials.
403 ForbiddenThe request uses credentials that are not authorized for access.
404 Not FoundThe requested resource could not be found.
405 Method Not AllowedEither:
  • The method is not supported/relevant for the resource, or
  • The user does not have permission to access the resource.
409 ConflictThe request conflicts with the current data.
422 Unprocessable EntityThe server understands the content type of the request entity, and the syntax of the request entity is correct, but it was unable to process the contained instructions.

Note: The request should not be repeated without modification.
429 Too Many RequestsToo 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.