Skip to main content
Static, non-bookable content used for hotel mapping (rooms, boards, amenities, geo, media). Pairs with OTA_HotelDescriptiveInfoRQ.

Purpose

This response delivers Non‑Bookable Content (NBC) for one or multiple properties so partners can map hotels, rooms, boards, amenities, locations, images, and DRV/third‑party codes. It is optimized for periodic full loads and daily deltas.

Structure – Root Element

Key Attributes
  • Version — specification version (e.g., 2009.1).
  • TransactionIdentifier — reports the count/range of hotels included in the payload.

Structure – Core Elements

HotelDescriptiveContent

Container and item for each property returned.
Common Attributes on HotelDescriptiveContent:
  • LanguageCode — ISO language code of the content.
  • RPH — sequence reference.
  • HotelCode — partner hotel code.
  • HotelName — marketing name.
  • HotelCodeContext — GIATA code when licensed.
  • ChainName (optional) — brand/chain.
  • LastModifiedDate — last modification timestamp for the property’s static data.

HotelInfo

High‑level static details. CategoryCodesHotelCategory and repeated GuestRoomInfo (room master data).
Check Hotel Related Codes. DescriptionsDescriptiveText consists of a long‑form factsheet text; may contain multiple paragraphs.
Position (Latitude, Longitude) — geo coordinates placed under HotelInfo.
Services → repeated Service entries; each Service may include Features/Feature and OperationSchedules.
Service@CodeDetail encodes a hierarchy using line breaks (pipes in textual examples). Related values can appear under Features/Feature@CodeDetail with a DescriptiveText value. Duration windows may be modeled with OperationSchedules/OperationSchedule.

AreaInfo

Location taxonomy and airports. Airports may specify:
  • Nearest (boolean), PrimaryIndicator (main airport),
  • Distance (km) with UnitOfMeasureCode="2", and Proximity (travel time in minutes).

AffiliationInfo

Optional star rating via Award@Rating (e.g., 4 Stars).

MultimediaDescriptions

Image catalog per property.
  • ImageItem (category via Category/ID) and optional LastModifyDateTime.
  • ImageFormat includes DimensionCategory (thumbnail, display, print, print_lead), Width, Height, and a file URL (filename only).
  • Description:
    • It can define a short descritpion of the content of the image shown in ImageItem. It includes the attribute Language.
    • If the attribute Caption is included, and the node is inside of ImageFormat, it shows to the unit that this image is corresponding.
  • Prefer ordering by Sort (ascending).
Standard Image Sizes
  • print_lead ≈ 2400 px (≈ 2.5 MB)
  • print ≈ 1200 px (≈ 1 MB)
  • display ≈ 450 px (≈ 130 KB)
  • thumbnail ≈ 200 px (≈ 40 KB)
Download rule: construct the full image URL using the hotel code and filename; store images locally for runtime use. http://tkimages.axisdata.net/ImageConverter.php?size={DimensionCategory}&height={Height}&hotel={HotelCode}&filename={URL} Example: size=print&height=1200&hotel=AMTSBG11C&filename=01.jpg
  • Images are not for hotlinking; partners must download & serve from their CDNs.
  • Test systems don’t serve images; use production. Show images by Sort (lower = higher priority).
  • If originals are low quality, some sizes/categories may be missing.

ContactInfos

Postal address, phone, email, and web URL for the property and/or supplier contact.

CodeConversions

DRV GlobalType mappings for hotel, room, and board levels. Requires DRV license. Entries use repeated CodeConversion elements with nested DRVGlobalTypes/DRVGlobalType/GTAttribute and optional Description. Check complete example below to view in response.

Behavior & Switches

If an enrichment switch is present in the request and set to false, the corresponding section is omitted in the response.
  • HotelInfo SendData="false" → omits Descriptions and Services.
  • ContactInfo SendData="false" → omits address block.
  • AreaInfo SendRefPoints="false" → omits RefPoints.
  • AffiliationInfo SendAwards="false" → omits Awards.
  • MultimediaObjects SendData="false" → omits images.

Complete Examples

Best Practices

  1. Use a two-step flow: Hotel List (minimal) → Hotel Details (per property, in needed languages).
  2. Prefer LastUpdateDate deltas daily; subtract ~3 hours as a safety margin for time-zone skew.
  3. When downloading media, sort and present by ImageFormat@Sort; issue HTTP HEAD to compare Last-Modified before downloading.
  4. Persist images and static data; do not hotlink image URLs at runtime.
  5. DRV and GIATA/TTI codes are license‑bound; enable per partner before relying on those fields.