• Q: Regarding the OTA_HotelDescriptiveInfo API response parameters, should we follow the sample responses in the documentation or the interface documentation itself? I noticed some discrepancies between the sample and the documentation.
    A: You can give priority to the interface documentation as the primary reference. For any specific discrepancies you encounter, please bring them to our attention. 


  • Q: What’s the data structure of the OTA_HotelDescriptiveInfo API? Is it following the below table?
    A: The structure for room types differs from standard implementations. Detailed room-specific information is located under FacilityInfo.GuestRooms, while the room type list and count can be viewed in HotelInfo.CategoryCodes.GuestRoomInfo.

    For other data hierarchy levels, refer to specific level markers from this article Content Solutions Distributor Content API (e.g., GuestRooms = Level 4, FacilityInfo = Level 3). Hotel images are primarily stored at Level 3 within MultiMediaDescriptions.


  • Q: ‌Room Type Images‌: Is the storage node for room type images located under [GuestRooms] → [MultimediaDescription]?
    A: FacilityInfo.GuestRooms.GuestRoom.MultimediaDescriptions.ImageItems


  • Q: ‌Attraction Information‌: Are business district attraction details stored in the [Attraction] node?
    A: Both RefPoint and Attraction under AreaInfo contain hotel surrounding information, depending on how the Supplier provides it. The specific type of surrounding information can be parsed by reading the CategoryCode. For example, @RefPointCategoryCode=30 corresponds to Shopping center.


  • Q: ‌Hotel Alias‌: Is there a dedicated parameter for hotel alias (alternative name)?
    A: Currently supported fields: @HotelName and @HotelShortName.


  • Q: ‌Front Desk Contact‌: Which parameter maps to the hotel's front desk phone number?
    A: Please refer to ContactInfos node.


  • Q: ‌Staff Count Calculation‌: Is the total customer service staff count aggregated from room type quantities in the [CategoryCodes] node?
    A: For total room counts per room category, values can be retrieved from the CategoryCodes > GuestRoomInfo node. Regarding customer service staff headcounts, no field is currently supported, and Suppliers are temporarily unable to provide this information.


  • ‌Q: Star Rating‌: Does [SegmentCategory] designate hotel star ratings (e.g., 3-star, 5-star)?
    A: Awards. Could refer to this example:
    <Awards>
         <Award Rating="5" RatingSymbol="Star"/>
    </Awards>


  • Q: ‌Hotel Type Classification‌: Is [HotelCategory] used to define hotel types (e.g., boutique, luxury)?
    A: Yes


  • Q: ‌Geographic Scope‌: Is there a parameter to distinguish domestic vs. international locations?
    A: Could distinguish by CountryName.Code


  • Q: ‌Child/Extra Bed Policies‌: Are explicit parameters defined for child policies and extra bed services?
    A: Check child-related policies under PolicyInfo. For unmet cases, reference FeePolicy Code enumeration values.
    During actual integration, follow Supplier recommendations – some Suppliers provide child/bed policies via ARI or offline tables, others may recommend policies from Content.


  • ‌Q: Sub-City Codes‌: What parameter encodes district/county-level administrative divisions?
    A: PostalCode


  • ‌Q: Room Type Naming‌: Is the primary identifier for room types labeled [Type Room Name]?
    A: Reference @RoomTypeName provisionally. For specific Supplier scenarios, TypeRoom@Name may be needed.


  • ‌Q: Bed Type Metadata‌: If [BedTypeCode] defines bed types, is there an accompanying descriptive field?
    A: Reference @BedTypeCode's corresponding OTA Code Description.