Versions Compared

Old Version 19

changes.mady.by.user Mayuri Bhakta

Saved on

compared with

New Version Current

changes.mady.by.user Mayuri Bhakta

Saved on

Key

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

Please check this page regularly for functionality and feature updates to SMX For Apps - Reservation API.

Removed / Modified / Added to the specification.

Table of Contents

Upcoming Change Dec 2024

Addition of: ResStatus=”Redacted”

Impact

Reservations with a @ResStatus of “Redacted” will have all ‘PII’ data removed.

Important: The SMX partner application should be able to accept all ResStatus values and respond with Success (200 OK status). It will now need to handle the additional ‘Redacted’ value.

XML Sample of new ResStatus

Code Block
<HotelReservations>
  <HotelReservation ResStatus="Redacted" CreateDateTime="2017-09-19T18:02:44+00:00" CreatorID="LINDA-RESAGENT" LastModifyDateTime="2017-09-19T18:13:51+00:00" LastModifierID="651651651651">
    <POS>…</POS>
    <UniqueID ID="BDC-3685569477"/>
    <RoomStays>…</RoomStays>
    <ResGlobalInfo>…</ResGlobalInfo>
  </HotelReservation>
</HotelReservations>

Updated 08-February-2024

Addition of: second AddressLine

Impact

Reservations may include a second AddressLine under ResGuest / Profile and ResGlobalInfo / Profile rather than having the two address lines merged in one AddressLine.
LittleHotelier supports two-line addresses and have character limits for each. If there is data in the second line, it will be sent in the XML in a secondary AddressLine as below:

XML Sample of two AddressLine

<Profiles> <ProfileInfo> <Profile ProfileType
Code Block
Info

Please check this page regularly for functionality and feature updates to SMX For Apps - Reservation API.

Removed / Modified / Added to the specification.

Table of Contents

Upcoming Change Dec 2024

Addition of: ResStatus=”Redacted”

Impact

Reservations with a @ResStatus of “Redacted” will have all ‘PII’ data removed.

Important: The SMX partner application should be able to accept all ResStatus values and respond with Success (200 OK status). It will now need to handle the additional ‘Redacted’ value.

XML Sample of new ResStatus

Code Block
<HotelReservations>
  <HotelReservation ResStatus="Redacted" CreateDateTime="2017-09-19T18:02:44+00:00" CreatorID="LINDA-RESAGENT" LastModifyDateTime="2017-09-19T18:13:51+00:00" LastModifierID="651651651651">
    <POS>…</POS>
    <UniqueID ID="BDC-3685569477"/>
    <RoomStays>…</RoomStays>
    <ResGlobalInfo>…</ResGlobalInfo>
  </HotelReservation>
</HotelReservations>

Updated 08-February-2024

Addition of: second AddressLine

Impact

Reservations may include a second AddressLine under ResGuest / Profile and ResGlobalInfo / Profile rather than having the two address lines merged in one AddressLine.
LittleHotelier supports two-line addresses and have character limits for each. If there is data in the second line, it will be sent in the XML in a secondary AddressLine as below:

XML Sample of two AddressLine

Code Block
  <Profiles>
    <ProfileInfo>
      <Profile ProfileType="1">
        <Customer VIP_Indicator="false">
          <PersonName>
            <GivenName>Lucie</GivenName>
            <Surname>Marie-Claude</Surname>
          </PersonName>
          <Telephone PhoneTechType="1" PhoneNumber="555-101010"/>
          <Email EmailType="1">js@example.com</Email>
          <Address Type="1">
            <AddressLine>Bond store 3</AddressLine>
  <Customer VIP_Indicator="false">         <AddressLine>30 Windmill <PersonName>St</AddressLine>
            <GivenName>Lucie<<CityName>Sydney</GivenName>CityName>
            <Surname>Marie-Claude</Surname><PostalCode>2000</PostalCode>
            <<StateProv>NSW</PersonName>StateProv>
          <Telephone PhoneTechType="1" PhoneNumber="555-101010"/> <CountryName>Australia</CountryName>
          <Email EmailType="1">js@example.com</Email></Address>
        </Customer>
 <Address Type="1">      <CompanyInfo>
      <AddressLine>Bond store 3</AddressLine>  <CompanyName>Siteminder</CompanyName>
        </CompanyInfo>
 <AddressLine>30 Windmill St</AddressLine>   </Profile>
    </ProfileInfo>
    <CityName>Sydney</CityName>
   </Profiles>

Updated 09-January-2024

Addition of: ResGlobalInfo and ResGuests / Profiles / UniqueID / ID

Impact

Little Hotelier reservations will contain a Guest ID under Profiles / UniqueID / ID. This is a random generated ID and will not be visible in Little Hotelier.

XML Sample of GuestID

Code Block
<ResGuests>
    <ResGuest ResGuestRPH="2">
        <PostalCode>2000</PostalCode><Profiles>
            <StateProv>NSW</StateProv><ProfileInfo>
            <CountryName>Australia</CountryName>    <UniqueID       </Address>
        </Customer>ID="1139" Type="1"/>
        <CompanyInfo>        <Profile ProfileType="1">
 <CompanyName>Siteminder</CompanyName>         </CompanyInfo>      
</Profile><ResGlobalInfo>
    </ProfileInfo>
  </Profiles>

Updated 09-January-2024

Addition of: ResGlobalInfo and ResGuests / Profiles / UniqueID / ID

Impact

Little Hotelier reservations will contain a Guest ID under Profiles / UniqueID / ID. This is a random generated ID and will not be visible in Little Hotelier.

XML Sample of GuestID

Code Block
<ResGuests><Profiles>
        <ProfileInfo>
            <UniqueID <ResGuest ResGuestRPHID="1140" Type="21"/>
        <Profiles>    <Profile ProfileType="1">
                 <ProfileInfo><Customer VIP_Indicator="false">
                <UniqueID ID="1139" Type="1"/>  <PersonName>
              <Profile ProfileType="1">           <GivenName>*****</GivenName>
      <ResGlobalInfo>     <Profiles>         <ProfileInfo>    <Surname>*****</Surname>
        <UniqueID ID="1140" Type="1"/>            </PersonName>
<Profile ProfileType="1">                    <Customer<Address VIP_IndicatorType="false1">
                    <PersonName>    <AddressLine>*****</AddressLine>
                        <GivenName><CityName>*****</GivenName>CityName>
                        <Surname><StateProv>*****</Surname>StateProv>
                    </PersonName>Address>
                </Customer>
   <Address Type="1">         </Profile>
        </ProfileInfo>
      <AddressLine>*****</AddressLine>
        </Profiles>
</ResGlobalInfo>                <CityName>*****</CityName>

Updated 09-January-2024

Addition of: ResGuest / PrimaryIndicator

Impact

Little Hotelier reservations will now identify the primary guest as PrimaryIndicator=”true” to know which guest is checking in. If multiple ResGuest / Profile are sent, only one will be identified as primary.

XML Sample of PrimaryIndicator

Code Block
<ResGuests>
        <ResGuest ResGuestRPH="1">
        <ResGuest ResGuestRPH="1" PrimaryIndicator="true">
   <StateProv>*****</StateProv>         <Profiles>
           </Address> <ProfileInfo>
               </Customer><Profile ProfileType="1">
            </Profile>ProfileInfo>
        </ProfileInfo>     </Profiles>
</ResGlobalInfo>            </ResGuest>

Updated 09-February-2022

Addition of: ResGlobalInfo / Total / Taxes

OTA_HotelResNotifRQ

Element

Attribute

Number

Description

OTA_HotelResNotifRQ / HotelReservations / HotelReservation / ResGlobalInfo / Total

 

1

Mandatory
NOTE: If HotelReservations / HotelReservation / @ResStatus = 'Cancelled' the this element becomes optional.

 

@AmountBeforeTax

0..1

The total amount not including any associated tax (e.g., sales tax, VAT, GST or any associated tax).

 

@AmountAfterTax

0..1

The total amount including all associated taxes (e.g., sales tax, VAT, GST or any associated tax).

 

@CurrencyCode

0..1

An ISO 4217 (3) alpha character code that specifies a monetary unit.

OTA_HotelResNotifRQ / HotelReservations / HotelReservation / ResGlobalInfo / Total / Taxes

 

0..1

A collection of taxes relating to the total reservation cost.

 

@CurrencyCode

0..1

An ISO 4217 (3) alpha character code that specifies a monetary unit.

 

@Amount

0..1

A monetary amount of tax.

OTA_HotelResNotifRQ / HotelReservations / HotelReservation / ResGlobalInfo / Total / Taxes / Tax


0..99

This element allows for both percentages and flat amounts. If one field is used, the other should be zero since logically, taxes should be calculated in only one of the two ways.

 

@Code

0..1

Code identifying the fee (e.g.,agency fee, municipality fee). Refer to OpenTravel Code List Fee Tax Type (FTT).

 

@Amount

0..1

A monetary amount of tax.

 

@CurrencyCode

0..1

An ISO 4217 (3) alpha character code that specifies a monetary unit.

 

@Percent

0..1

Fee percentage; if zero, assume use of the Amount attribute (Amount or Percent must be a zero value).

OTA_HotelResNotifRQ / HotelReservations / HotelReservation / ResGlobalInfo / Total / Taxes / Tax / TaxDescription


0..5

Text description of the taxes.

OTA_HotelResNotifRQ / HotelReservations / HotelReservation / ResGlobalInfo / Total / Taxes / Tax / TaxDescription / Text


0..n

Textual description of Discount Reason.

Updated 07-February-2022

Removal of: ResGlobalInfo / DepositPayments / GuaranteePayment / AcceptedPayments / AcceptedPayment / DirectBill @amount @numberOfNights

OTA_HotelResNotifRQ

OTA_HotelResNotifRQ / HotelReservations / HotelReservation / ResGlobalInfo / DepositPayments / GuaranteePayment / AcceptedPayments / AcceptedPayment / DirectBill

 

0..1

Details of a direct billing arrangement.

 

@DirectBill_ID

0..1

Identifier for the organization to be billed directly for travel services.

@Amount

0..1

A monetary amount taken for the deposit.

@NmbrOfNights

0..1

The number of nights of the hotel stay that are used to calculate the fee amount.

Updated 04-February-2022

Removal of: HotelReservation / Services / Service / ServiceDetails / GuestCounts / TimeSpan

Addition of: HotelReservation / Services / Service / ServiceDetails / TimeSpan

OTA_HotelResNotifRQ

OTA_HotelResNotifRQ / HotelReservations / HotelReservation / Services / Service / ServiceDetails

0..1

Details on the Service including Guest Counts, Time Span of this Service, pointers to Res Guests, guest Memberships, Comments and Special Requests pertaining to this particular Service and finally financial information related to the Service, including Guarantee, Deposit and Payment and Cancellation Penalties.

OTA_HotelResNotifRQ / HotelReservations / HotelReservation / Services / Service / ServiceDetails / GuestCounts

0..1

A collection of Guest Counts associated to the whole Reservation or a particular Room Stay or Service.

OTA_HotelResNotifRQ / HotelReservations / HotelReservation / Services / Service / ServiceDetails / GuestCounts / TimeSpan

@Start

0..1

The starting value of the time span.

@End

0..1

The ending value of the time span.

OTA_HotelResNotifRQ / HotelReservations / HotelReservation / Services / Service / ServiceDetails / GuestCounts / GuestCount

0..99

A recurring element that identifies the number of guests and ages of the guests.

@AgeQualifyingCode

0..1

A code representing a business rule that determines the charges for a guest based upon age range (e.g. Adult, Child, Senior, Child With Adult, Child Without Adult). This attribute allows for an increase in rate by occupant class. Refer to Age Qualifying Code List.

@Age

0..1

Defines the age of a guest.

@Count

0..1

The number of guests in one AgeQualifyingCode or Count.

@AgeBucket

0..1

Defines the age range category or bucket a guest can be booked into. This is typically used in conjunction with the age qualifying code to further define the applicable age range.

OTA_HotelResNotifRQ / HotelReservations / HotelReservation / Services / Service / ServiceDetails / TimeSpan

0..1

The Time Span which covers the Service.

@Start

0..1

The starting value of the time span.

@End

0..1

The ending value of the time span.