Transfers API ERRORS

API ERRORS

HTTP status code

Description

200

OK - The request has succeeded. The client can read the result of the request in the body and the headers of the response.

201

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

204

OK - No availability. There was no transfer services available for the given dates and passenger group.

400

Bad Request - The request could not be understood by the server due to malformed syntax. The message body will contain more information

401

Unauthorized - Invalid or expired token

403

Forbidden - The server understood the request, but is refusing to fulfill it

Developer Over Qps - You have exceeded your API quota

Please check the response body or the response header "X-Mashery-Error-Code" to be sure which error you are having (Forbidden or Developer Over Qps)

404

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

406

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 - Use the Content-Type header to set application/json and be sure the format of your payload matches the format

500

Internal Server Error - Not handled error

502

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

503

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 - an invalid endpoint has being reached. Please check that the endpoint you are using to send the petitions is correct.

Docs Navigation