Skip to content

Error Codes

All API errors follow this shape:

{
"eventId": "...",
"error": {
"code": "<numeric code>",
"type": <error type>,
"message": "<human-readable description>"
}
}
Type Description
SYSTEM Internal system error
VALIDATION Input validation error
APPLICATION Business logic error
SECURITY Auth / permission error
Code Meaning
UNKNOW_INTERNAL Internal error unknown
UNAVAILABLE_SERVICE Service not available
TIME_OUT Request resolution timed out
INVALID_FORMAT Invalid data format
INVALID_DATA Invalid value in data content
UNAUTHORIZED No access to the application
FORBIDDEN Insufficient privileges
INVALID_TOKEN Token invalid or expired
NOT_FOUND Requested resource does not exist
SOLD_OUT Product no longer available
PRICE_MISMATCH Rate has changed
PAYMENT_PROCESS Error in payment processing
NOT_PAYABLE Cannot pay with provided info
INVALID_BOOKING Invalid reservation request
CANCELLED Reservation cancelled
LIMIT_EXEEDED Too many requests

Code HTTP Message Cause / Fix
900 401 The authorization header is invalid Missing Bearer prefix
902 401 The authorization token is invalid Token corrupted or signed by another tenant
903 401 The authorization token has expired Generate a new token
1001 401 No authorization token provided Missing Authorization header
1003 401 The channel id <X> is not enabled to be used in <env> Channel not provisioned in this environment — escalate to PT. Returned after the token, not by the token.
Code HTTP Message Cause / Fix
1003 400 invalid_client Credentials rejected — id, secret, or inactive credentials. The response does not distinguish. See Authentication.
1004 400 invalid_client_id_for_env_<env> Using credentials from another environment
1005 400 invalid_client_secret Wrong secret — verify rotation
Code HTTP Message Cause / Fix
429 429 Request rate limit per minute exceeded Throttle requests; increase delay
1002 401 agency configuration not Found Channel/agency setup pending — escalate
1003 400 Invalid agency templateId Agency template not configured
3001 400 CheckIn can not be a past date Use today or future
3002 400 CheckOut can not be earlier or equal to CheckIn Fix dates
3003 400 Can’t quote more than 28 days Split into multiple queries
3004 400 All rooms must contain at least one adult (18+) Add adult to room criteria
4001 500 Invalid Channel Id on Rate Limiter Internal — escalate with eventId
5001 500 Miss-match of channel Id Channel mismatch — escalate
Code HTTP Message Cause / Fix
1002 401 agency configuration not Found Channel/agency setup pending
1003 400 Invalid agency templateId Agency template not configured
4001 400 The RateKey must be valid rateKey expired, corrupted, or empty
4002 400 More hotels than expected rateKey contains multiple hotels — invalid here
4003 400 You don’t have enough credit Channel credit/line balance exhausted
4004 400 RateKey older than 60 minutes Re-search via /hotels/rates
4005 200 No results Rate no longer available — sold out
4006 200 <provider message> (e.g. “not allotment for the rate”) Supplier-specific error — re-search
5001 500 Miss-match of channel Id Internal — escalate
5007 401 Mismatch of channel id. Channel id from previous step: <X> The rateKey was generated with another channel’s credentials. Run the whole flow, from HotelRates on, with the same credentials.
Code HTTP Message Cause / Fix
201 500 Invalid booking id / reservation number. Only numbers are allowed bookingId must be numeric
1101 400 The provided key has already been used previously BookingHold: rateKey reused — get fresh one
1101 500 The provided key has already been used previously. BookingNew: bookingKey already used. Do not obtain a new key to restart the flow — see BookingNew
1201 500 The itinerary does not contain valid services Booking corrupt — escalate
1202 500 Locator’s not found for the requested channel Booking not visible from this channel
3003 500 Cannot get a valid response from the cancellation service Supplier failure — escalate
3005 500 Cancellation timeout Retry after 1-2 min, verify with BookingGet
4001 400 Invalid Hold Request, can not parse the rateKey rateKey corrupted or mis-encoded
4002 400 You cannot invoke ‘Hold’ without first performing a ‘CheckRates’ Use rateKey from CheckRates, not Rates
4003 400 Hold rateKey older than 20 min Repeat CheckRates
4008 400 The requested rate is no longer available. Not defined. The response does not state the reason. Observed in one response. The Hold request was sent less than 20 seconds after a successful CheckRates. 4008 and 4009 return the same message; the difference between them is not defined. Request a new rateKey by repeating Rates and CheckRates. Do not use the code to tell the cause apart.
4009 400 The requested rate is no longer available. Not defined. The response does not state the reason. Observed in one response. The Hold request was sent less than 20 seconds after a successful CheckRates. 4008 and 4009 return the same message; the difference between them is not defined. Request a new rateKey by repeating Rates and CheckRates. Do not use the code to tell the cause apart.
5001 500 Invalid Policy Internal — escalate
6001 400 Invalid New Request, can not parse the BookingKey bookingKey corrupted/expired
6002 400 You cannot use the 'New' operation if more than 20 minutes have passed since obtaining the BookingKey from 'Hold'. Not defined. BookingNew returned this code with this message; the condition that triggers it is not defined. Obtain a new bookingKey with BookingHold. Do not use the code or the number in the message to tell the cause apart.
6102 400 Invalid range, only 31 days are allowed BookingReservations returned this code with this message. The message states that the range is not valid and gives a number of allowed days; how the days are counted is not defined. Reduce the range, or split the period into several requests.
7001 400 A valid client data was not provided Missing/invalid name, surname, or contactData
7002 400 A valid credit card was not provided The Payment object is deprecated: do not send it
Code HTTP Message Cause / Fix
1001 404 hotel not found Invalid hotelId
1002 400 hotelId must be an integer Non-numeric path parameter

The same numeric code can mean different things depending on the operation that returned it, so the code alone is not enough to branch on — read it together with the endpoint you called. The table below covers only the variants verified against captures; it is not the full list of places these codes appear in the API. For the token variant of 1003 the response does not distinguish between a wrong id, a wrong secret and inactive credentials — see Authentication.

Code Operation HTTP Meaning in that context
1003 Token 400 invalid_client, with no eventId and no message — the response does not say which credential check failed
1003 HotelRates 401 The channel id <X> is not enabled to be used in <env> — returned by the call made after the token, not by the token
1101 BookingNew 500 The provided key has already been used previously. — the bookingKey was already used by a previous BookingNew. Do not obtain a new key to restart the flow; see BookingNew
1203 BookingDelete 400 Your reservation is currently being created. Please wait a moment before accessing it.

HTTP Type Meaning
200 Success OK (note: 4005/4006 also return 200)
301 Redirect URL is wrong — check trailing slash
400 Client error Invalid data or structure
401 Auth Token missing/invalid
403 Forbidden No access to resource
404 Not found Resource does not exist
406 Not acceptable Wrong Accept header
410 Gone Resource permanently unavailable
415 Unsupported media Wrong Content-Type
429 Rate limited Too many requests
500 Server Internal API error
502 Bad gateway Upstream supplier error
503 Unavailable API temporarily down
504 Gateway timeout Upstream timeout
513 App error Internal services error
596 Not found Endpoint does not exist

When you see an error, ask:

  1. What’s the HTTP status? (filters category)
  2. What’s the error.code? (specifies cause within category)
  3. Which endpoint? (some codes change meaning by endpoint, e.g. 4001)
  4. What’s the eventId? (always include when escalating to PT)
  5. Are time windows respected? (60min / 20min / 5min / 90s)

When in doubt, escalate with: endpoint, full request, full response, eventId, and timestamp.

For an uncertain BookingNew outcome without a bookingId, include clientReference, the attempt timestamp in UTC, and eventId if available.