Response codes

The Xeneta API uses standard HTTP response codes to indicate the status of an API request.

As a rule, codes in the 2xx range indicate success, while codes in the 4xx range indicate an issue with the request. Codes in the 5xx range indicate an error with our servers.

All endpoints available in the Xeneta API can return the following status codes:

Response code
Description
200 - OKThe request was processed successfully.
204 - No ContentThe request was processed successfully, but there was no data in the response.
400 - Bad RequestThe request failed due to missing or incorrect input parameters.
401 - UnauthorizedThe API key was either not provided or incorrect.
403 - ForbiddenThe API key doesn't have permissions to access the requested resource.
422 - Unprocessable ContentThe request was understood by the API server, but could not be processed correctly.
429 - Too Many RequestsThe API server received too many requests in a short span of time.
500 - Internal Server Error
502 - Bad Gateway
504 - Gateway Timeout
Something went wrong on our end.
Xeneta Footer - Fixed