Hotel API integration is how a travel platform connects to live hotel rooms, prices and bookings. Your app sends a request; a supplier sends back rooms and rates; your user books in seconds. In practice it is not one call but a short chain of them — find the location, search, open a hotel’s rooms, re-check the price, book, issue the voucher — and most of the work sits in the steps between the first search and the confirmed booking. Tripgic’s hotel booking API, for example, runs this chain in eleven calls across 2M+ properties from 50+ suppliers.

This guide walks that chain call by call. It shows what each step returns, where integrations usually break, how to test them, and how to choose a provider. It uses two real, public examples: the Hotelbeds Booking API and the Tripgic Hotel API, whose endpoints are listed in the Tripgic API docs. By the end you will know what it takes to add hotels to your platform, and where the time really goes.

What Is Hotel API Integration?

Hotel API integration is the work of connecting your platform to a hotel supplier through an API. API stands for Application Programming Interface — a fixed set of requests one system accepts from another, with a fixed shape for the answers. Your platform asks “which hotels in Paris have a room for two adults on these dates?” and the supplier answers in a structure your code can read.

Without an API, someone updates rooms and prices by hand, or logs into each supplier’s website to book. That is slow, it does not scale, and it is full of errors. With an API, availability and prices arrive live, and a booking made on your site is a booking in the supplier’s system a second later.

Two different things share this name

Search results for “hotel API integration” mix two jobs, and it helps to know which one you are doing:

Selling hotels (distribution side) Running a hotel (property side)
Who does it OTAs, travel agencies, TMCs, booking engines, travel apps Hotels and hotel groups
What it connects Your booking platform to hotel suppliers The hotel’s PMS to its channel manager, POS, door locks and so on
The goal Show and sell many hotels to travellers Keep one hotel’s own systems in sync

This guide is about the first job: selling hotel rooms on your own platform. If you run a single hotel and want your systems to talk to each other, you need a property-management integration instead, and most of what follows will not apply.

The Hotel Booking Flow, Call by Call

Almost every hotel booking API follows the same order. The names change from supplier to supplier; the steps do not.

Step You send You get back If you skip or rush it
1. Location lookup Text the user typed: “par” Matching cities, areas, landmarks, hotel names, each with an ID Free-text searches return nothing or the wrong Paris
2. Search Location ID, dates, rooms and guests per room A list of hotels with a “from” price Wrong occupancy per room gives wrong prices
3. Rooms for one hotel The chosen hotel, same dates and guests Every room type and rate plan, with board and cancellation terms You show a “from” price the user cannot actually book
4. Hotel details The hotel ID Photos, description, amenities, location A thin hotel page users do not trust
5. Price and policy check The exact room and rate The current price and cancellation policy, or “no longer available” You charge a price that has changed
6. Traveller details Lead guest name and contact, sometimes every guest A booking ready to confirm The hotel has the wrong name at check-in
7. Book The checked rate and guests A booking reference and status —
8. Voucher The booking reference A voucher or confirmation the guest shows at the hotel The guest arrives with nothing to show
Beside the flow Booking look-up, cancellation Current status; the refund under the policy You cannot answer “is my booking real?”

Hotel API integration flow: search, availability, price check, booking, and confirmation steps

A traveller sees this as one smooth path that takes a minute. Your platform makes five or more separate calls along it. On a busy site that is thousands of calls a minute, so each one must be fast and each failure must be handled — which is why the rest of this guide spends more time on the middle of the flow than on the first search.

Search is cheap, booking is not

The search call is made constantly and most of its results are never booked. The booking call is made rarely and every one of them moves money. Design for that difference. Searches can be fast, broad and partly cached at the content level. Everything from the price check onwards must be live, exact and logged.

Two Real Hotel APIs, Side by Side

Generic flows are easy to agree with. Real endpoint lists show where suppliers differ.

Hotelbeds: three methods

Hotelbeds, one of the largest hotel wholesalers, documents its Booking API as three methods: Hotels (availability), CheckRates and Bookings. Its own page says most of its hotels “are bookable in two steps”, but some “require obtaining up-to-date availability and prices”: those rates carry the value recheck in the rateType attribute, and the CheckRates method returns the current price before you book. The Bookings method then covers confirming, listing, looking up, modifying and cancelling a booking — including simulating a cancellation to see its conditions. Hotelbeds also notes that its Booking API works together with a separate Content API for photos, descriptions and facilities.

Tripgic: eleven calls on one base URL

The Tripgic API docs list the hotel family as eleven POST calls, each with a JSON body:

Endpoint (as listed in the docs) What it does
/hotel/auto-suggetion Location suggestions for the search box
/hotel/search Hotel search by location and occupancies
/hotel/rooms Availability for one hotel and its rooms
/hotel/get-hotel-details Content for one hotel
/hotel/validate Price and policy validation
/hotel/validation-price-get-detail Details of that price validation
/hotel/update-travellers Add or change travellers on a booking
/hotel/create Create the booking
/hotel/booking-details Look up one booking
/hotel/issue-voucher Issue the voucher
/hotel/cancel-booking Cancel the booking

The paths are copied exactly as the docs print them — including the spelling of the first one — because a developer will paste them.

What the two have in common

The shapes differ: Hotelbeds folds several jobs into one Bookings method, while Tripgic gives each job its own call. But both make the same point. Between seeing a rate and booking it, there is a dedicated step to confirm it is still true. Hotelbeds makes it conditional on a flag; Tripgic makes it a call in the standard flow. Whichever supplier you use, find that step on day one and never route around it.

Example: One Hotel Booking, Step by Step

Here is the chain with a real-looking case. Sara wants a hotel in Paris for two nights, for two adults.

  1. Sara types “par”. Your platform calls the location lookup and shows “Paris, France” first. She picks it, so you now hold a location ID rather than a string.
  2. You call search with that ID, her dates and one room for two adults. A list of hotels comes back, each with a lowest price.
  3. Sara opens a boutique hotel in the 9th arrondissement. You call the rooms endpoint for that hotel. A Deluxe King comes back with two rate plans: refundable with breakfast, and a cheaper non-refundable rate.
  4. In parallel you fetch the hotel’s details — photos, amenities, location — to fill the page.
  5. Sara picks the refundable rate. You call the price and policy check. The price is unchanged and the free-cancellation deadline is confirmed, so you show both before payment.
  6. Sara enters her name and her partner’s. You attach the travellers to the booking.
  7. Sara pays. You create the booking and receive a reference with a confirmed status.
  8. You issue the voucher and email it to her.

Sara saw one smooth flow. Your platform made seven calls and held three IDs: the location, the hotel and the rate. That is the core of any hotel API integration — not the first request, but keeping the right IDs moving through every step.

The Tripgic hotel API page shows a trimmed sample of this kind of response: a hotel ID, name, star rating and guest score, a location with neighbourhood and coordinates, amenities, images, then rooms with rate plans carrying a price, currency, breakfast flag and cancel-by time, plus a booking token. It is the same shape whichever supplier fulfilled it.

What Data You Get From a Hotel API

A hotel API returns two kinds of data, and you treat them differently.

Data type Examples How often it changes
Static content Hotel name, address, coordinates, photos, description, amenities, star rating Rarely — weeks or months
Live (dynamic) data Room price, availability, rate plan, board type, cancellation policy Constantly — by the minute

Static content is what makes a hotel page trustworthy. Good APIs return high-resolution photos, structured descriptions, amenity lists and room-level images. Coordinates let you build a map view or a “near me” search. Content in several languages saves you a translation pipeline.

Live data is what makes a booking work. It is only true at the moment you ask, which is why it is never stored as fact.

Rate plans and board types

One room usually comes with several rate plans — different prices for the same room under different terms. The common ones are:

  • Refundable — free cancellation until a deadline, then a penalty.
  • Non-refundable — cheaper, with no money back after booking.
  • Advance purchase — a lower price for booking well ahead, often non-refundable.
  • Member or loyalty rates — prices for a closed group of users.

Each rate also has a board type, which says which meals are included:

Board Meaning
Room only No meals
Bed and breakfast Breakfast included
Half board Breakfast and dinner
Full board Breakfast, lunch and dinner
All-inclusive All meals and usually drinks

Your search filters and your room cards both depend on these fields. If a supplier returns them as free text, you will spend weeks normalizing them; if it returns them as structured values, a filter like “breakfast included, free cancellation” is a few lines of code.

Cancellation policies

A cancellation policy is a deadline plus a penalty — for example, “free until 23:59 on 4 May, then the first night is charged”. Store it per booking, exactly as the supplier returned it at the price check, not as it looked in search. Two details catch teams out:

  • Time zones. Deadlines may come in UTC or in the hotel’s local time. Show the guest the deadline in a time zone you name on the screen.
  • Currency. A penalty can be in a different currency from the price the guest saw. Convert it with the same rate you used for the price, or say plainly that it may vary.

Where Hotel Rooms Come From

Hotel rooms reach an API from several kinds of source, each with its own coverage, price level and data quality.

  • Bedbanks (wholesalers): they contract rooms with hotels and resell them to travel sellers. One connection gives wide global coverage, which makes them the fastest way to add many hotels.
  • Channel managers: they sit on the hotel’s own systems, so you get the property’s direct rates and live availability.
  • Direct contracts: you sign with a hotel or a chain yourself. This can give better rates on key hotels, but every contract is its own project.
  • GDS hotel content: global distribution systems carry hotel rooms too, which suits agencies already booking flights there.

Most strong platforms blend these. A bedbank gives reach, direct contracts add margin on the hotels that sell most, and GDS content serves corporate travellers. For named providers in each group, see our hotel API providers comparison.

Caching: Static Yes, Prices No

Speed decides whether a hotel search converts. Caching is how you get it — if you cache the right things.

  • Cache static content. Store names, photos, descriptions and amenities in your own database. Refresh on a schedule, and refresh one hotel at once when its content looks wrong.
  • Never cache a price as the truth. You may keep a recent search price to show a “from” figure, but confirm the price and availability live before payment, every time.
  • Cache location lookups. “Paris” will still be Paris tomorrow. Caching suggestions cuts a large share of your calls.
  • Respect rate limits. Suppliers cap how many requests you can send. Caching static content and location data is what keeps you inside those limits during a busy hour.

The rule fits in one line: cache what describes the hotel, never what you are about to charge for.

Direct vs Aggregator: Two Paths to Hotel Supply

You can reach hotels in two ways.

Path 1: direct connections

A direct connection links you to one supplier. You sign a contract, receive credentials, read that supplier’s documentation and build to its format. You get full control and sometimes better rates. But every supplier has its own API, its own data model, its own certification and its own changes over time. Fifty suppliers means fifty integrations to build and to keep working.

Path 2: an aggregator

An aggregator gives you one API in front of many suppliers; Tripgic’s hotel aggregator API is one example. You build one integration and reach every source behind it, in one data format. To see why that matters beyond hotels, read our guide to multi-supplier travel inventory.

Factor Direct connection Aggregator
Integrations to build One per supplier One
Data format Different for each supplier One schema
Time to launch Months per supplier Days to weeks
Keeping it working You track every supplier change The aggregator absorbs most of it
Matching duplicate rooms Your job Often handled for you — ask
Best for Large platforms with a dedicated supply team OTAs, agencies, startups, platforms adding hotels to another product

For most growing platforms the aggregator path wins on time and cost. Large platforms often do both: an aggregator for reach, plus a few direct contracts where the volume justifies them. For how long each path takes, see our travel API integration timeline.

Hotel Room Mapping: The Hidden Cost

Room mapping becomes your problem the moment you have more than one supplier. Two suppliers may sell the same room under different names — “Deluxe King”, “DLX KNG 1 Bed”, “Superior Double, King Bed”. The same hotel may also arrive twice, with slightly different names or addresses.

If you do not match them, your search shows the same hotel or the same room several times. Users lose trust, and at worst they book a rate they did not mean to choose.

Hotel room mapping linking different supplier room names into one clean room record

Good mapping uses hotel IDs, coordinates, room codes, bed types and occupancy, plus rules for the cases those miss. It is real work and it never quite ends, because suppliers keep adding hotels and renaming rooms. Our hotel room mapping guide covers the methods in detail. When you compare providers, ask a direct question: do you return one record per hotel and per room, or do I de-duplicate?

Booking Edge Cases That Break Integrations

The first search works on day one. These are the cases that surface in week three.

Case What happens What to do
The price changed at the check The check returns a higher or lower price than search Show the new price clearly and ask the user to accept it before payment
The room sold out at the check The rate is no longer available Return the user to the room list with fresh results, not to an error page
The booking call times out You do not know whether the booking exists Look it up with the booking-details call before retrying. Never retry blind
Payment succeeded, booking failed You hold money for nothing Refund automatically and log it; never leave this to a manual check
Wrong guest names The hotel has no record of the person at the desk Validate names before booking; use the traveller-update call where the supplier allows it
Taxes paid at the hotel City tax or resort fees appear at check-in Show “payable at the hotel” amounts separately, if the supplier returns them
Cancellation after the deadline The guest expects a refund the policy does not give Show the deadline at booking and in the voucher, in a named time zone
Supplier outage Calls fail or slow down Time out quickly, show a clear message, and keep the rest of the site working

The timeout row deserves a second look. A booking request that times out may have succeeded on the supplier’s side. If you send it again, the guest can end up with two rooms and two charges. The safe order is always: look up, then decide. This is why a booking look-up call matters as much as the booking call itself.

How to Test Your Hotel API Integration

A hotel integration moves real money and real rooms, so test it like payment code.

  • Start in the sandbox. Every serious provider has a test environment. Run the whole flow there before you touch live inventory.
  • Book end to end. Location lookup to voucher, not just search. A test that stops at search proves almost nothing.
  • Cancel what you booked. Check that the refund matches the policy the price check returned.
  • Test the awkward searches. Sold-out dates, one night and thirty nights, three rooms with different guests, children with ages, a city with thousands of hotels.
  • Force the failures. Simulate a timeout on the booking call and confirm your code looks the booking up instead of retrying. Simulate a price change at the check.
  • Check the voucher. Open it as the guest would. Is the name right, the address clear, the cancellation deadline visible?

A short list of scenarios to keep and re-run before every release:

Scenario Expected result
1 room, 2 adults, refundable, 2 nights Booked, voucher issued, cancel refunds in full before the deadline
1 room, 2 adults, non-refundable Booked; cancel returns the penalty, no refund
2 rooms, different occupancy Each room priced for its own guests
Price changes at the check User sees the new price and must accept it
Booking call times out Booking looked up, no duplicate created
Supplier returns an error Clear message, no charge

Automate these. Suppliers change their APIs, and an automated run is how you find out before your guests do.

A Realistic Integration Plan

Teams underestimate hotel integrations because the first search is easy. A sensible order is:

  1. Read the docs and map the flow. Write down every call you will make, in order, and which IDs pass between them.
  2. Build search and content. Location lookup, search, rooms and hotel details, with static content cached.
  3. Build the booking path. Price check, travellers, booking, voucher — with the timeout and price-change cases handled from the start, not added later.
  4. Build cancellation and look-up. Your support team will need both on day one.
  5. Test the scenario list above in the sandbox, then with a small amount of live traffic.
  6. Go live and watch. Track failed checks, failed bookings and timeouts per supplier. These numbers tell you where users drop out.

Step 3 is where most of the time goes, and it is where an aggregator saves the most: you build the booking path once instead of once per supplier.

How to Choose a Hotel API Provider

Use these questions when you compare providers. For eleven named providers side by side, see our hotel API providers comparison.

Question Why it matters
How many properties, suppliers and countries? Coverage decides how often a user finds what they searched for
Is there a separate price-and-policy check? It is what stops failed bookings at payment
Are rate plans, board types and cancellation rules structured? Free text means weeks of normalizing
Do you de-duplicate hotels and rooms across suppliers? Otherwise mapping is your job
Is there a booking look-up and a cancellation call? Your support team cannot work without them
How do you charge — per booking, per night, a percentage, a subscription? It decides your margin on every sale. See our guide to travel API pricing models
How do I get sandbox credentials, and how long until a test booking? It tells you how fast you can learn whether the API fits
What other products does the same API cover? Adding flights or transfers later should not mean a second integration

There is no single best answer for everyone. A startup may weigh a fast sandbox and clear docs most; a large OTA may weigh coverage and direct-rate options. Score each provider against what your platform needs.

Tripgic Hotel API: What You Get

Tripgic is a B2B travel API: one integration for hotels and seven other product families. For hotels specifically, here is what its Hotel API page and API docs state:

  • Coverage: 2M+ properties from 50+ supply partners, across 190+ countries — from luxury resorts and business hotels to budget stays, serviced apartments and vacation rentals.
  • One schema: every response has the same shape “regardless of which underlying supplier fulfilled it”, so you build your room card once.
  • Live rates: availability and pricing are queried in real time from the underlying suppliers.
  • The full flow in eleven calls: location suggestions, search, rooms, hotel details, price and policy validation, travellers, booking, booking look-up, voucher and cancellation — the same chain this guide walks through.
  • Structured rate plans and policies: room-only, bed and breakfast, half board, full board, all-inclusive, advance purchase, non-refundable and member rates, each with cancellation deadlines and penalty amounts.
  • Content you can show: photos, room-level images, amenities, coordinates and neighbourhood data, in major languages.
  • Filters: by property type, star rating, amenities, price range, distance from a point or landmark, and rate type such as refundable-only or breakfast-included.
  • A fee that does not grow with the room price: hotel bookings carry a flat amount per night, never a percentage commission. Current figures and the plans that include hotels are on the pricing page.
  • The same pattern for everything else: 73 endpoints across 8 product families on one base URL, so adding flights, transfers or activities later reuses the integration you already built.

Getting started: you book a short call, register, and receive free sandbox credentials before you pay anything; Tripgic says teams typically go from first call to a test booking in days. The contact page has the details.

Final Thoughts

Hotel API integration looks like one search request and is really a chain of calls. The search is the easy part. The work — and the difference between a platform that converts and one that fails at payment — sits in the price check, the booking, the timeout handling, the cancellation and the room mapping.

Build the full chain, test it end to end, cache only what describes the hotel, and look up a booking before you ever retry one. If you would rather build that chain once for many suppliers instead of once per supplier, an aggregator is the shorter road.

Want to see the Tripgic hotel flow with your own use case? Book a demo and get sandbox credentials after a short call.