Skip to main content

​
Error Scenarios

This section describes the most common and important errors and causes that can be found in our B2B interface. An error is considered when the response has the following format: 
<OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="_12345_" Version="2016.2">
  <Errors>
    <Error Type="3" Code="392">Invalid hotel code</Error>
  </Errors>
</OTA_HotelResRS>
What do we see?
  • No Success element present in the response.
  • An Errors element containing all encountered errors from the request.
  • A Code that identifies each type of error.
  • A brief description of the cause.
Not every single error is present in this page, only the common and important ones. If needed, when “unknown” errors are returned, contact Integrations.

​
Price

Price related error responses or incidences.
  • Case: Price retrieved from the Cache file or XML interface does not match with the price received in a quote response.
  • Error received: None.
  • Test steps:
    • Do a search for hotel xxx, room xxx, board xxx from xxx to xxx, get details.
    • Do a following search or quote for hotel xxx, room xxx, board xxx from yyy to yyy, price will mismatch. Take time ranges from different seasons to force the error.
  • Complete error response: N/A.

​
Availability

Availability related error responses or incidences.
  • Case: Search, quote or commit has more than 5 rooms.
  • Error received:
    • Type 3
    • Code 378
    • Detail: Invalid - max number of rooms (5) exceeded
  • Test steps:
    • Do a search or quote for more than 5 rooms, return error and ensure proceeding to Commit is not possible.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="2008.1" EchoToken="_12345_">
  <Errors>
    <Error Type="3" Code="378">Invalid - max number of rooms (5) exceeded</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: After doing a book request system returns “Stop Sale” error. This can happen when the stop sales in contract was activated after a succesful search (pull) or after the last delivered file (push).
  • Error received:
    • Type 3
    • Code 158
    • Detail: Stop-Sale: HOTEL_CODE-HOTEL_NAME
  • Test steps:
    • Do a quote for room with Stop Sales. Contact integrations if the case is needed.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="2008.1" EchoToken="_12345_">
  <Errors>
    <Error Type="3" Code="158">Stop-Sale: AMTSES0008-Garden Beach</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: After doing a book request system returns “Close Out” error. This can happen when the close out in contract was activated after a succesful search (pull) or after the last delivered file (push).
  • Error received:
    • Type 3
    • Code 507, 508
    • Detail:
      • NotAvailable. Room Restrictions failed: Restriction 1, DateRestriction 1 - stay start failure
      • NotAvailable. Room Restrictions failed: Restriction 1, DateRestriction 1 - stay end failure
  • Test steps:
    • Very uncommon case, if test is required it needs to be forced, contact integrations.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="2008.1" EchoToken="506737044">
  <Errors>
    <Error Type="3" Code="507" Tag="STORE">NotAvailable. Room Restrictions failed: Restriction 1, DateRestriction 1 - stay start failure</Error>
    <Error Type="3" Code="508" Tag="STORE">NotAvailable. Room Restrictions failed: Restriction 1, DateRestriction 1 - stay end failure</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: Room no longer available, last room for the specified dates sold, subsequent requests fail with an availability error.
  • Error received:
    • Type 3
    • Code 5000
    • Detail: NotAvailable. Insufficient remaining allotments
  • Test steps:
    • Do a quote for a room with 0 allotment. Contact integrations if the case is needed.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="0.1" EchoToken="_12345_">
  <Errors>
    <Error Type="3" Code="5000" Tag="STORE">NotAvailable. Insufficient remaining allotments</Error>
    <Error Type="3" Code="5403" Tag="STORE">NotAvailable. SubAllotment: insufficient remaining allotments for requested hotel AMTSES0FDO, room JSSD00SVA0 and board code</Error>
    <Error Type="3" Code="5404" Tag="STORE">NotAvailable. SubAllotment: insufficient remaining allotments for requested hotel AMTSES0FDO, room JSSD00SVA0</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: Hotel code not specified or wrong code element construction.
  • Error received:
    • Type 3
    • Code 392
    • Detail: Invalid hotel code
  • Test steps:
    • Do a quote for room xxx, board xxx from xxx to xxx without the HotelCode element or leaving it empty.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="_12345_" Version="2016.2">
  <Errors>
    <Error Type="3" Code="392">Invalid hotel code</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: Hotel no longer available, hotel not assigned to the portfolio.
  • Error received:
    • Type 3
    • Code 14
    • Detail: No suitable services found
  • Test steps:
    • Do a search for hotel xxx, room that does not exist, board xxx from xxx to xxx, get details for hotel not existent, service not available error will be returned.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="_12345_" Version="0.10">
  <Errors>
    <Error Type="3" Code="14">No suitable services found</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: Room code not specified or not following room code element structure.
  • Error received:
    • Type 3
    • Code 402
    • Detail: Invalid room type
  • Test steps:
    • Do a quote without the RoomCode element or leaving it empty.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="_12345_" Version="2016.2">
  <Errors>
    <Error Type="3" Code="402">Invalid room type</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: Room no longer available, room not available for a specific hotel.
  • Error received:
    • Type 3
    • Code 14
    • Detail: Invalid service unit: ROOM_CODE. Valid unit codes for HOTEL_CODE: ROOM_CODE_LIST
  • Test steps:
    • Do a search for hotel xxx, wrong room, board xxx from xxx to xxx, get details.
    • Do a following search or quote for hotel yyy, wrong room, board xxx from xxx to xxx, room not available error returned with a list of available rooms.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="_12345_" Version="0.10">
  <Errors>
    <Error Type="3" Code="14">
      Invalid service unit: APSDDM00A0. Valid unit codes for AMTSES0Z7K: APSD0000A0, APSD0000A0, APSD00SV00, APSD00SV00, APSDIN00A0, APSDIN00A0!
    </Error>
  </Errors>
</OTA_HotelResRS>
  • Case: Board code not specified or not following room code element structure.
  • Error received:
    • Type 3
    • Code 115
    • Detail: Invalid board basis/meal plan
  • Test steps:
    • Do a quote without the Board Code element or leaving it empty.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="_12345_" Version="2016.2">
  <Errors>
    <Error Type="3" Code="14">Invalid board basis/meal plan</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: Board no longer available, board not available for a specific hotel and/or room.
  • Error received:
    • Type 3
    • Code 14
    • Detail: Invalid board: BOARD_CODE. Valid boards for product HOTEL_CODE and unit ROOM_CODE: BOARD_CODE_LIST
  • Test steps:
    • Do a search for hotel xxx, room xxx, wrong board from xxx to xxx, get details.
    • Do a following search or quote for hotel xxx, room xxx, wrong board from xxx to xxx, board not available error returned with a list of available boards.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="_12345_" Version="0.10">
  <Errors>
    <Error Type="3" Code="14">
      Invalid board: SC. Valid boards for product AAEFJR1WHS and unit RMCSDB00B0: AI,BB,FB,HB,RO
    </Error>
  </Errors>
</OTA_HotelResRS>
  • Case: No hotels/transfers/excursions available for specified parameters.
  • Error received:
    • Type: N/A
    • Code: N/A
    • Detail: Empty response
  • Test steps:
    • Do a search with correct but not existent parameters.
  • Complete error response: 
    <OTA_HotelAvailRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="1234" Version="2008.1">
  <Success/>
  <Warnings>
    <Warning Type="3" Code="427">No rooms available for requested dates</Warning>
  </Warnings>
</OTA_HotelAvailRS>

<OTA_GroundAvailRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="1234" Version="0.1">
  <Success/>
  <Warnings>
    <Warning Type="3" Code="427">No services available for requested dates</Warning>
    <Warning Type="3" Code="427">No services available for requested dates</Warning>
  </Warnings>
</OTA_GroundAvailRS>

<OTA_TourActivityAvailRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="1234" Version="2008.1">
  <Success/>
  <Warnings>
    <Warning Type="3" Code="427">No Amenities available for requested dates</Warning>
  </Warnings>
</OTA_TourActivityAvailRS>
  • Case: Release condition not accomplished. Request date is too close to the booking start date, restriction defined at room or hotel level.
  • Error received:
    • Type 3
    • Code 515, 415
    • Detail:
      • NotAvailable. Room Restrictions failed: Restriction 1, DateRestriction 1 - release time failure
      • NotAvailable. Hotel Restrictions failed: Restriction 1, DateRestriction 1 - release time failure
  • Test steps:
    • Do a quote for hotel with release, 1 day prior to the start date, release error will be returned. Contact integrations if the case is needed.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="_12345_" Version="0.10">
  <Errors>
    <Error Type="3" Code="515" Tag="STORE">NotAvailable. Room Restrictions failed: Restriction 1, DateRestriction 1 - release time failure</Error>
  </Errors>
</OTA_HotelResRS>

<OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="0.1" EchoToken="">
  <Errors>
    <Error Type="3" Code="415" Tag="STORE">NotAvailable. Hotel Restrictions failed: Restriction 1, DateRestriction 1 - release time failure</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: Allotment status is not open; allotment is set to OnRequest, StopSale or closed.
  • Error received:
    • Type 3
    • Code 5200, 5100, 5300
    • Detail:
      • NotAvailable. Allotment Closed
      • NotAvailable. Allotment OnRequest
      • NotAvailable. Allotment StopSale
  • Test steps:
    • Very uncommon case, if test is required it needs to be forced, contact integrations.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="b36e89a740ca-414c-95a2-cb10aa62c762" Version="0.1">
  <Errors>
    <Error Type="3" Code="5200" Tag="STORE">NotAvailable. Allotment Closed</Error>
    <Error Type="3" Code="5423" Tag="STORE">NotAvailable. SubAllotment: allotment closed for requested hotel AMTSES0S6S, room RMSD000000 and board code</Error>
    <Error Type="3" Code="5424" Tag="STORE">NotAvailable. SubAllotment: allotment closed for requested hotel AMTSES0S6S, room RMSD000000</Error>
  </Errors>
</OTA_HotelResRS>

<OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="0.1" EchoToken="0fb632e1401ff7ad7a24813b428e74b3">
  <Errors>
    <Error Type="3" Code="5100" Tag="STORE">NotAvailable. Allotment OnRequest</Error>
    <Error Type="3" Code="5413" Tag="STORE">NotAvailable. SubAllotment: allotment on request for requested hotel AMTSBG2AXK, room RMSD00000E and board code</Error>
  </Errors>
</OTA_HotelResRS>

<OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="_12345_" Version="0.10">
  <Errors>
    <Error Type="3" Code="5300" Tag="STORE">NotAvailable. Allotment StopSale</Error>
    <Error Type="3" Code="5400" Tag="STORE">NotAvailable. SubAllotment: insufficient remaining allotments</Error>
    <Error Type="3" Code="5403" Tag="STORE">NotAvailable. SubAllotment: insufficient remaining allotments for requested hotel AMTSES0F74, room RMSD000000 and board code</Error>
    <Error Type="3" Code="5434" Tag="STORE">NotAvailable. SubAllotment: allotment stop sale for requested hotel AMTSES0F74, room RMSD000000</Error>
  </Errors>
</OTA_HotelResRS>

​
Occupancy

Occupancy related error responses or incidences.
  • Case: Pax names are missing or child age is not provided for AgeQualifyingCode 7 and 8.
  • Error received:
    • Type 3
    • Code 27
    • Detail: Passenger details are mandatory
  • Test steps:
    • Do a search for hotel xxx, room xxx, board xxx from xxx to xxx and xxx adults, get details.
    • Do a following search or quote for hotel xxx, room xxx, board xxx from xxx to xxx and YYY adults, without specifying first name and/or last name.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="2008.1" EchoToken="506714670">
  <Errors>
    <Error Type="3" Code="27">Passenger details are mandatory</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: Pax number is over or under the limits of the room, the room cannot hold the pax requested.
  • Error received:
    • Type 3
    • Code 14
    • Detail:
      • Invalid occupancy. No. of pax (ACTUAL_PAX_NUMBER) exceeds the maximum allowed! (MAX_PAX_NUMBER)
      • Invalid occupancy. No. of pax (ACTUAL_PAX_NUMBER) falls below the minimum required! (MIN_PAX_NUMBER)
  • Test steps:
    • Do a search for hotel xxx, room xxx, board xxx from xxx to xxx and xxx adults, get details.
    • Do a following search or quote for hotel xxx, room xxx, board xxx from xxx to xxx and YYY+5 adults, room can’t hold that number of pax.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="2008.1" EchoToken="506714670">
  <Errors>
    <Error Type="3" Code="14">Invalid occupancy. No. of pax (4) exceeds the maximum allowed! (3)</Error>
  </Errors>
</OTA_HotelResRS>

<OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="2008.1">
  <Errors>
    <Error Type="3" Code="14">Invalid occupancy. No. of pax (1) falls below the minimum required! (2)</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: Pax type is over or under the limits of the room, the room cannot hold the pax type requested.
  • Error received:
    • Type 3
    • Code 14
    • Detail:
      • Invalid occupancy. No. of PAX_TYPE (PAX_TYPE_NUMBER) exceeds the maximum allowed! (MAX_PAX_TYPE_NUMBER)
      • Invalid occupancy. No. of PAX_TYPE (PAX_TYPE_NUMBER) falls below the minimum required! (MIN_PAX_TYPE_NUMBER)
  • Test steps:
    • Do a search for hotel xxx, room xxx, board xxx from xxx to xxx with xxx child, get details.
    • Do a following search or quote for hotel xxx, room xxx, board xxx from xxx to xxx and YYY children, room can’t hold children.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="0.1" EchoToken="c8db3cf6421fdbd97d6e41e1c9decda5">
  <Errors>
    <Error Type="3" Code="14">Invalid occupancy. No. of children (1) exceeds the maximum allowed! (0)</Error>
  </Errors>
</OTA_HotelResRS>

<OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="0.1" EchoToken="1ca197dc0962383c5b66acc0f9cf3b05">
  <Errors>
    <Error Type="3" Code="14">Invalid occupancy. No. of adults (1) falls below the minimum required! (2)</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: A restriction for a specific occupancy has been set, quote for that specific occupation will fail.
  • Error received:
    • Type 3
    • Code 209
    • Detail: NotAvailable. Invalid Occupancy: combination of adults+children not allowed
  • Test steps:
    • Very uncommon case, if test is required it needs to be forced, contact integrations.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="2008.1" EchoToken="506740574">
  <Errors>
    <Error Type="3" Code="209" Tag="STORE">NotAvailable. Invalid Occupancy: combination of adults+children not allowed</Error>
    <Error Type="3" Code="142">Invalid Occupancy: 3 Adult/s + 1 Child/ren are not allowed!</Error>
  </Errors>
</OTA_HotelResRS>

​
Stay

Stay related error responses or incidences.
  • Case: Stay requested in the search is over the maximum that can be provided (28 days).
  • Error received:
    • Type 3
    • Code 356
    • Detail: Searches over 99 days are not permitted
  • Test steps:
    • Do a search for hotel xxx, room xxx, board yyy from xxx to xxx, stay is over 28, search will be responded with error.
  • Complete error response: 
    <OTA_HotelAvailRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="" Version="0.1">
  <Errors>
    <Error Type="3" Code="356">Searches over 99 days are not permitted</Error>
  </Errors>
</OTA_HotelAvailRS>
  • Note: Booking is possible up to 180 nights for push clients.
  • Case: Minimum stay condition not met, stay is lower than the minimum specified.
  • Error received:
    • Type 3
    • Code 517
    • Detail: NotAvailable. Room Restrictions failed: Restriction A_NUMBER, StayRestriction A_NUMBER - duration min. failure
  • Test steps:
    • Do a quote for hotel with min stay with less stay than allowed. Contact integrations if the case is needed.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="2008.1" EchoToken="107311225">
  <Errors>
    <Error Type="3" Code="517" Tag="STORE">NotAvailable. Room Restrictions failed: Restriction 3, StayRestriction 1 - duration min. failure</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: Stay includes days not available, contract does not cover all the stay.
  • Error received:
    • Type 3
    • Code 145
    • Detail: Duration period or dates incorrect
  • Test steps:
    • Do a search or quote without start and/or end dates, leaving them empty, use a wrong format or with a start date in the past.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="_12345_" Version="2016.2">
  <Errors>
    <Error Type="3" Code="145">Duration period or dates incorrect</Error>
  </Errors>
</OTA_HotelResRS>

​
References

References related error responses or incidences.
  • Case: A booking cancellation or retrieve is requested using a non-existing reference; booking cannot be found in the system.
  • Error received:
    • Type 3
    • Code 127
    • Detail: Booking reference not found
  • Test steps:
    • Do a cancellation for a booking with an inexistent reference; booking won’t be found in the system and an error will be returned.
  • Complete error response: 
    <OTA_CancelRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="2008.1" CancelType="Commit">
  <Errors>
    <Error Type="3" Code="127">Booking reference not found</Error>
  </Errors>
</OTA_CancelRS>
  • Case: A booking cancellation or retrieve is requested using a non-existing item reference in a booking; booking item cannot be found in the system.
  • Error received:
    • Type 3
    • Code 150
    • Detail: FATAL BOOKING ERROR! Contact Support!
  • Test steps:
    • Do a cancellation for a booking item with an inexistent reference; booking item won’t be found in the system and an error will be returned.
  • Complete error response: 
    <OTA_CancelRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="2008.1">
  <Errors>
    <Error Type="3" Code="150">FATAL BOOKING ERROR! Contact Support!</Error>
  </Errors>
</OTA_CancelRS>
  • Note: This specific error is raised as a FATAL error, as it means a possible mismatch between the status of the items of a booking. An immediate communication with integrations is required.

​
Credentials

Credential related error responses or incidences.
  • Case: A request with wrong or inexistent authentication is sent; user and password validation fails and the message is rejected.
  • Error received:
    • Type 3
    • Code 175, 182
    • Detail:
      • Username or Password invalid
      • Username and Password required
  • Test steps:
    • Do a request using either invalid user + password values or without the authentication section; an error response will be returned according to the case.
  • Complete error response: 
    <OTA_HotelAvailRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="2008.1">
  <Errors>
    <Error Code="175" Type="3">Username or Password invalid</Error>
  </Errors>
</OTA_HotelAvailRS>

<OTA_HotelAvailRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="2008.1">
  <Errors>
    <Error Type="3" Code="182">Username and Password required</Error>
  </Errors>
</OTA_HotelAvailRS>
  • Case: A request with wrong credential (ClientID) is sent; system rejects the message as partner is not configured in the system.
  • Error received:
    • Type 3
    • Code 305
    • Detail: Invalid client code
  • Test steps:
    • Do a request using either invalid user + password values or without the authentication section; an error response will be returned according to the case.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" Version="0.10" EchoToken="_12345_">
  <Errors>
    <Error Type="3" Code="305">Invalid client code</Error>
  </Errors>
</OTA_HotelResRS>

​
Miscellaneous

Miscellaneous error responses or incidences.
  • Case: Room no longer available for the contract; room not available for a specific hotel but was previously included.
  • Error received:
    • Type: Internal-Error
    • Code: 7001
    • Detail: NotAvailable. Hotel EDF not found
  • Test steps:
    • Not applicable; internal error occurring in between contract updates.
  • Complete error response: 
    <OTA_HotelResRS xmlns="http://www.opentravel.org/OTA/2003/05" EchoToken="_12345_" Version="0.10">
  <Errors>
    <Error Type="Internal-Error" Code="7001" Tag="STORE">NotAvailable. Hotel EDF not found</Error>
  </Errors>
</OTA_HotelResRS>
  • Case: Request XML is not well-formed.
  • Error received:
    • Type: N/A
    • Code: N/A
    • Detail: OTA request validation failed. ERROR_DETAIL_DESCRIPTION
  • Test steps:
    • N/A; general validation errors should be here.
  • Complete error response: 
    <OTA_HotelAvailRS xmlns="http://www.opentravel.org/OTA/2003/05" TransactionIdentifier="0-0/0" Target="Production" Version="2006">
  <Success>false</Success>
  <Error>OTA request validation failed. No guests found.</Error>
  <RoomStays/>
</OTA_HotelAvailRS>