HTTP Response Errors

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

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


Invalid JSON or XML request due to bad syntax. Please follow the guidance of the error message in order to fix the problem with the request. There are many examples of valid requests in our Postman collection.


The JSON or XML syntax is correct, however some of the fields contain incorrect data. Please check the documentation for the allowed values and follow the message returned in order to fix this error.


402 Payment Required - Booking requires payment information. Revise the paymentType of the rate and include the payment details.

Developer Inactive - The api-key sent in the header is wrong or inactive.

Not Authorized - The X-Signature parameter is incorrect. Please make sure your apikey - secret are correct and your system clock is set correctly.

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

Developer Over QPS- You have exceeded your API throttle limit.

Developer Over Rate - You have exceeded your API daily quota.

NOTE: Please check the response body or the response header "X-Mashery-Error-Code" to be sure which error you are having.

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.


This type of error occurs when the user is repeating a failed request which occurred in the past 15 minutes. The failed request was producing a product error and the text describes what that error was.

415 Unsupported Media Type - Use the Content-Type header to set application/json or application/xml based on the format of your payload.


These are internal server errors, please send us these errors together with the complete logs (JSON or XML requests and responses) at so that our team can review them.


This type of error is produced due to product restrictions or due to other account set-up limitations. In all cases, the end result is that the booking cannot be confirmed. Here is a list of common product errors:

Insufficient allotment: This means that the user is trying to book a room which is no longer available. This may happen if the room was still available in the Availability stage but someone else has made a reservation for this room or rooms. 

Price has increased: The price increase between booking steps has exceeded the allowed tolerance that was set (by default this is 2%). This is a setting to protect clients from booking a room with a higher price than expected.

Contract is closed/Office or branch not active/Cannot find channel quotation: There are problems related to the contract.

Stop sales: This means that the hotel is forbidding sales on the requested dates.


This type of error is produced by configuration restrictions set-up at account level. Usually this results in the inability to perform an specific operation. Here is a list of common configuration errors:

This apikey is not associated with a valid client: This means that the provided apiKey belongs to an inactive client/agency. If you need information regarding the cause for this please contact our support team at
502 Bad Gateway - The server was acting as a gateway or proxy and received an invalid response from the upstream server.


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.



Gateway Timeout - The server was unable to handle the request under the expected time due to a temporary condition which will be alleviated after some delay. You can choose to resend the request again.

NOTE: Be aware that in the event of receiving this error at booking confirmation, it's possible that the booking was made despite not having a response. You can check this using the BookingList operation.

513 Application error - Indicates that an involved backend application returned an error or warning, which is passed back in the response message.
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