Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

There are identifiers that are used on different request/response chains.

...

15.1.1. HOTELRESERVATIONIDS

The HotelReservationIDs is used as unique identifier of a booking.

...

"supplier". Each actual reservation returns "supplier" identifier - the unique identifier of the booking in supplier's system. Normally this value should be further used in hotel voucher. ResID_SourceContext attribute identifies the supplier. It is not necessary to pass the " supplier" identifier in all following requests; only "client" is required.

You have to store all values of HotelReservationIDs in your system, and use it unchanged through whole booking's life cycle.

...

Diagram 1415.1.1.1. HotelReservationIDs flow

...

Code Block
languagexml
<HotelReservationIDs>
   <HotelReservationID ResID_Source="agent" ResID_Value="66589"/>
   <HotelReservationID ResID_Source="client" ResID_Value="264888"/>
   <HotelReservationID ResID_Source="supplier" ResID_Value="LL7F090498" ResID_SourceContext="kuoni"/>
</HotelReservationIDs>

...

15.1.2. BOOKINGCODE

The BookingCode attribute in RoomRate element is used as unique identifier of an offer starting Hotel Availability response and till the time the booking is confirmed. The BookingCode is valid for limited time (normally 15 minutes); if the reservation was not confirmed (or at least initiated) during this time limit, then new search should be performed again.

...

BookingCode may change between Availability search and Reservation Initiate response (it depends on supplier specific). In Reservation Confirm request, the BookingCode must be taken from the Reservation Initiate response.

...

Diagram 1415.1.2.1. BookingCode usage

Since a room booked, the BookingCode does not play role for the reservation any more. The HotelReservationIDs should be used for the booking modification or cancellation.

...

15.1.3. TRANSACTIONIDENTIFIER

Hotel Reservation, Modification and Cancellation should always be done in two steps: 1) Initiation (request/response) and 2)Confirmation or Ignore (request/response). Both these steps have to be done within one transaction.

The TransactionIdentifier allows to recognize which Confirmation or Ignore request relates to a Initiation response.

...

Diagram 1415.1.3.1. TransactionIdentifier usage

14.1.4. ECHO TOKEN

The EchoToken is the identifier that can be used by client for its internal purposes. GP Travel HUB does not use or change it.