Transfers API ERRORS

HTTP Response Errors

The error description will be returned in a basic format in the response body.

HTTP status code

Description

200 OK

The request was succesful - The client can read the result of the request in the body and the headers of the response.

201 CREATED

The request was succesful - The client can read the result of the request in the body and the headers of the response.

204 NO CONTENT

No content - There's no available content for the requested parameters.

400 BAD REQUEST

BAD_REQUEST_ERROR - The request is not compliant with the specified version of the API. The message body will contain more information

401 UNAUTHORIZED

Not authorizedInvalid or expired token

403 FORBIDDEN

Developer Inactive - The key is not active in our system.

Developer Over QPS - You have exceeded your API quota.

404 NOT FOUND

Not found - The requested resource could not be found. This error can be due to a temporary or permanent condition.

406 NOT ACCEPTABLE

Not Acceptable - The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.

415 UNSUPPORTED MEDIA TYPE

Unsupported Media Type - Use the Content-Type header to set application/json and be sure the format of your payload matches the format.

500 INTERNAL SERVER ERROR

SYSTEM_ERROR - An unexpected error occurred while processing your request. Please try again later.

502 BAD GATEWAY

Bad Gateway - The server was acting as a gateway or proxy and received an invalid response from the upstream server.

503 SERVICE UNAVAILABLE

Service Unavailable - The server is currently unable to handle the request due to a temporary condition which will be alleviated after some delay. You can choose to resend the request again.

596 SERVICE NOT FOUND

Service Not Found - an invalid endpoint has being reached. Please check that the endpoint you are using to send the petitions is correct.

Docs Navigation