Technical

What is hotel XML integration? Static vs. dynamic data

Hotel XML integration is when an agency or booking platform connects to a supplier's system through a web service and receives hotel data automatically. Static data (name, address, coordinates, room types, images) changes rarely and is downloaded and stored in advance. Dynamic data (availability, price, cancellation terms) is queried live on every search and linked to the static record by the supplier code.

Author
hotelmapping.org Editorial Team
Last updated:
9 min read

What does hotel XML integration mean?

Instead of entering the information and prices of the hotels they sell by hand, online agencies connect to suppliers such as bedbanks, wholesalers, booking platforms or channel managers through a web service. Hotel information, prices and availability arrive automatically over this connection. In the industry this connection is simply called XML integration.

An integration has two ends. At one end, the supplier offers its inventory and prices as a service. At the other end, the agency, tour operator or metasearch site calls this service, converts the response into its own system and shows it to its customer. As the number of suppliers grows, this conversion work grows too, because each supplier sends the same hotel with its own name, its own code and its own data structure.

For more on supplier types, see the what is a bedbank guide and the bedbank and channel manager glossary entries.

Why is it called “XML”?

XML (Extensible Markup Language) is a text format in which data is structured with tags, and it is standardized by the W3C. Most of the first web services in the travel industry were built on SOAP and XML. That is why the phrase “XML integration” stuck.

Today many suppliers offer REST APIs that use JSON; some still work with XML. In business language both are mostly referred to as “XML integration.” Technically, what matters is not the format but the content of the data and whether the two sides recognize the same hotel as the same hotel.

The difference between static and dynamic data

The data arriving in a hotel XML integration splits into two groups. This distinction is the foundation of system design: it determines which data is stored, which is asked for each time, and where matching is done.

Feature Static data Dynamic data
Example fields Hotel name, address, coordinates, star rating, description, images, facilities, room type list Availability, price, quota, cancellation terms, real-time board options
Rate of change Slow; over days or weeks Fast; within minutes or even seconds
How it is obtained Bulk download (full dump), then changed records (delta) Live query on every search
Where it is kept In your database In a short-lived cache or not at all
Need for mapping High; the same hotel is written differently by each supplier Indirect; codes in the response are linked to the static record
If something goes wrong Duplicate hotels, wrong location, missing content Wrong price displayed, booking error

What does static data cover?

Static hotel data is the information that makes up a property’s identity and description. Typical fields are:

  • The supplier’s hotel code and hotel name
  • Address, city, country and the supplier’s destination code
  • Coordinates (latitude, longitude)
  • Star rating or category
  • Description texts and images
  • Property and room facilities
  • Room type list and sometimes a board type list
  • Phone, email, web address

Because this data changes little, it is not requested again on every search. The agency downloads it in advance, stores it in its own database and displays it on screen.

What does dynamic data cover?

Dynamic data is the information valid right now for a specific date, room and number of guests: is the room available, what is the price, which board options exist, what are the cancellation terms. This information is obtained live from the supplier on every search request. The response contains identifiers such as hotel code, room code and board code; to put a meaningful result on screen, these codes need to be combined with the static data.

The flow of a typical hotel XML integration

Although names and details vary from supplier to supplier, most integrations follow similar steps:

  1. Static content download: The hotel list, descriptions, images and room types are retrieved in bulk and stored.
  2. Search (availability): The user’s destination, dates and guest details are sent to the supplier; available hotels return with their prices.
  3. Recheck (recheck or prebook): When the user selects an option, the price and availability are verified again; cancellation terms are finalized.
  4. Booking (book): The booking is created with guest details; the supplier returns a booking reference.
  5. Retrieval and cancellation: The booking status is queried or the booking is canceled.

The first step involves static data, the others dynamic data. hotelmapping.org cleans and maps only the data produced by the first step; the search, booking and cancellation steps stay between your system and your supplier.

Example: the same hotel, two suppliers, two formats

In the example below, the fictional “Lara Palm Hotel” comes from two suppliers. The first supplier sends XML:

<Hotel code="LPH-20931">
  <Name>LARA PALM HTL</Name>
  <Address>Guzeloba Mah., Lara Cad. No:112</Address>
  <City code="AYT">Antalya</City>
  <Position lat="36.8571" lng="30.7962"/>
  <Category>5</Category>
  <Rooms>
    <Room code="DBL-SV">Double Room Sea View</Room>
    <Room code="FAM-2B">Family Room 2 Bedrooms</Room>
  </Rooms>
</Hotel>

The second supplier sends the same hotel as JSON, with a different name and code:

{
  "hotelId": "770512",
  "hotelName": "Lara Palm Hotel - Adults Friendly",
  "destination": "Lara / Antalya",
  "latitude": 36.8569,
  "longitude": 30.7965,
  "stars": "5*",
  "roomTypes": [
    { "id": "R1", "name": "DBL ROOM SEAVIEW" },
    { "id": "R4", "name": "Family Suite 2 Bdr" }
  ]
}

If these two records are used without matching, the hotel appears twice in the list. When matched, they are gathered under a single permanent ID:

{
  "hm_id": "HM-1052207",
  "name": "Lara Palm Hotel",
  "destination_id": "TR-07-MURATPASA-LARA",
  "destination": ["TR", "Antalya", "Muratpaşa", "Lara"],
  "geo": { "lat": 36.8570, "lng": 30.7963 },
  "supplier_codes": {
    "A": "LPH-20931",
    "B": "770512"
  },
  "rooms": [
    { "hm_room_id": "HM-1052207-R02", "name": "Double Room, Sea View", "supplier_codes": { "A": "DBL-SV", "B": "R1" } },
    { "hm_room_id": "HM-1052207-R04", "name": "Family Room, 2 Bedrooms", "supplier_codes": { "A": "FAM-2B", "B": "R4" } }
  ]
}

This is sample data; the hotel name, address and codes do not belong to a real property. Here the HM ID links both supplier codes to the same hotel. Rooms are grouped on the same logic; this work is the subject of the room mapping product.

Why does static data require mapping?

For an agency working with a single supplier, the mapping problem is small. The moment a second supplier is added, two records of the same hotel exist. As the number of suppliers grows, the problem grows:

  • Duplicate listing: The same hotel appears in search as multiple cards; the customer cannot tell which one is correct. We cover the business impact of this in the duplicate hotel cost article.
  • Broken price comparison: Prices that suppliers give for the same hotel cannot be gathered on one card.
  • Inconsistent content: One supplier’s description may be incomplete and another’s coordinates wrong. To combine the right fields, you first need to know that the records are the same hotel.
  • Room and board confusion: “DBL ROOM SEAVIEW” and “Double Room Sea View” are the same room; “AI” and “All Inclusive” are the same board type. These too must be linked to a standard code.

We describe the details of the mapping process in the what is hotel mapping guide. On the product side, its counterparts are the hotel mapping, board type mapping and hotel content pages.

How is a dynamic response linked to the static record?

A search response usually carries only codes. For example, supplier B’s availability response may contain a fragment like this:

{
  "hotelId": "770512",
  "offers": [
    { "roomId": "R1", "board": "AI", "price": { "amount": 412.50, "currency": "EUR" }, "refundable": true }
  ]
}

To display this response on screen, your system must answer these questions: which hotel is “770512”? Which room is “R1”? Which standard board type is “AI”? If the static side has been mapped, the answer is found with a single lookup: the supplier code is translated to the HM ID, the room code to the HM room ID, and the board code to the standard code. That way, offers from different suppliers can be shown side by side on the same hotel card, under the same room and board heading.

Because this translation is repeated on every search, it must be fast. That is why mapping results are mostly kept on your side as a table, and at search time only this table is consulted. The source of the table can be an API, a daily dump or a combination of the two. The matching API can also be used to look up codes one by one.

How is static data kept up to date?

Static data changes slowly, but it does change: hotels open, close, change their name or owner; suppliers delete codes or issue new ones. There are three common methods for tracking these changes:

Method How it works When it fits
Full dump The entire catalog is downloaded again from scratch at set intervals Initial setup, small catalog, periodic full check
Delta dump Only records added, changed and deleted since the last dump are retrieved Large catalog, regular updates
Webhook The other side sends you a notification when a change occurs Code changes that need a fast response

In the delta dump approach, it is important that deleted or merged records are also explicitly reported. Otherwise a hotel code that no longer exists remains in your system and causes errors in search.

Common mistakes in integration projects

  • Never updating static data: After the first download the data goes stale; closed hotels stay on sale and new hotels do not appear.
  • Treating the supplier code as the only ID: A supplier code is meaningful only for that supplier. With multiple suppliers you need your own permanent ID.
  • Matching by name only: Different hotels share the same name; the same hotel arrives under different names. Coordinates, address, phone and web address should be evaluated together.
  • Leaving room and board codes as free text: “DBL ROOM SEAVIEW” and “Double Room Sea View” appear side by side on screen; comparison breaks.
  • Not validating coordinates: Suppliers sometimes send the coordinates of the city center or a wrong point. This breaks both map display and matching.
  • Not tracking code changes: When a supplier deletes a code and issues a new one, the old match silently breaks.

Checklist when connecting a new supplier

Before starting a new XML integration, clarifying the answers to these questions will make your job easier:

  1. In what format and through which channel does static data arrive (API, file, FTP)?
  2. How often are the full dump and delta published; are deleted records reported?
  3. Are room and board types coded, or free text?
  4. What hierarchy do the destination codes follow?
  5. Are the codes in the search response exactly the same as in the static data?
  6. What are the cache and recheck rules?

If you are choosing a mapping service, we have collected the more detailed questions to ask in 12 questions to ask when choosing a hotel mapping API. The list of ready-made supplier connections is on the integrations page; for example, the Hotelbeds page shows which fields we map in a bedbank’s static data.

Where does hotelmapping.org fit in this structure?

hotelmapping.org works on the static side of XML integration. It takes your suppliers’ static data, normalizes it and links the same hotel to a single permanent HM ID. It converts room names, board types and destination codes into their standard equivalents. It delivers the result as a REST API and as daily full or delta dumps.

The price, availability, booking and cancellation steps stay between your system and your supplier; hotelmapping.org does not carry or store this data. That way, without adding a new layer to your dynamic flow, you can combine the codes in search responses with the mapping table on your side. API endpoints and sample responses are on the developers page.

Frequently asked questions

Is XML integration the same as API integration?

In the industry the two are mostly used to mean the same thing. The phrase "XML integration" is a holdover from the days when the first web services used XML. Today many suppliers offer JSON-based REST APIs; even so, in business language these connections are still generally called XML integrations.

How often does static data need to be updated?

There is no single right frequency; it depends on the supplier's rate of change and the size of your catalog. A common approach is to take a full dump at the start, then process only the changed records (delta) at regular intervals.

Is it right to cache price and availability data?

A short-lived cache can speed up search, but because price and availability change quickly, you need to re-check with the supplier (recheck) before booking. Cache duration and recheck rules may be part of the supplier's integration terms; check them at the contract stage.

Does hotelmapping.org provide dynamic data too?

No. hotelmapping.org works only on the static hotel data side: hotel, room, board type and destination mapping, plus hotel content. The price, availability and booking flow stays between you and your supplier.

Sources

  1. W3C: Extensible Markup Language (XML)

hotelmapping.org Editorial Team

DIJI.TECH hotel data team

The DIJI.TECH team working on hotel mapping, supplier integration and travel software.