Services · APIs
Hotel booking API: live rates, mapped properties, reliable bookings
Hotels look simpler than flights until you connect a second source. Suddenly the same property appears under two names, one room type is called four things, and a 'free cancellation' rate turns out to be non-refundable after midnight hotel time. Avunzo's hotel booking API exists to absorb that mess before it reaches your customers.
Built for
- OTAs
- Hotel wholesalers
- Super-apps
- Corporate booking tools
- Tour operators
In brief
What is a hotel booking API?
A hotel booking API lets software search hotel availability, show live rates, and confirm and cancel reservations programmatically. Voraal's Avunzo connects hotel aggregators, bedbanks and direct chain connections through one REST/JSON schema, with normalised property content, images and policies, real-time pricing and cancellation terms, so your product books rooms without integrating each hotel source separately.
By the Voraal team · Updated
The two problems a hotel booking API must solve
The first is content: names, addresses, star ratings, images, amenities and room descriptions arrive in different shapes from every source. Without mapping, one hotel appears twice in your results, or two different hotels with similar names merge into one. The second is rates: a room rate is a combination of room type, board basis (room only, breakfast, half board), occupancy, cancellation policy and payment terms, and it is only valid for a short time.
A hotel booking API handles both. Avunzo returns normalised property content with images and policies, and live rates with their cancellation terms attached, through the same schema used for flights and ground services. For hotel distribution in Pakistan specifically, see the hotel booking API for Pakistan.
A hotel booking, step by step
| Stage | What your app does | What to watch |
|---|---|---|
| Search | Send destination or property list, dates, rooms and occupancy | Child ages change price; send them, not just a count |
| Choose a rate | Show room, board basis, total and cancellation policy | Show taxes and fees that are payable at the hotel separately |
| Re-check | Confirm the selected rate is still available at that price | Rates can expire within minutes of search |
| Book | Create the order with guest names and contact details | Use an idempotency key so a retry does not book twice |
| Confirm and service | Store the confirmation and voucher; cancel within policy | Deadlines are often in the hotel's local time |
Key features
Multiple hotel sources
Aggregators, bedbanks and direct chain connections behind one integration.
Normalised property content
One property record with images, descriptions and policies, whatever the source.
Real-time rates
Live pricing with the cancellation terms that belong to each rate.
Dynamic packages
Bundle hotels with flights and ground services; package pricing in one call.
Channel markups
Markups and filters per channel, so B2C and partner channels can price differently.
Booking webhooks
Booking status changes pushed to your system.
How Avunzo answers a hotel search
- 01
Resolve the destination
A city, area or list of property IDs is turned into the set of properties to query.
- 02
Query sources in parallel
Connected hotel sources are called at the same time, with caching to keep repeated searches fast.
- 03
Map and merge
Rates from different sources for the same property are grouped under one normalised property, so customers compare offers for the same hotel.
- 04
Return comparable rates
Each rate carries room, board, total price and cancellation terms in the same structure.
Business applications
An OTA adds hotels to its flight product and raises basket value with packages. A super-app offers stays in its marketplace with its own checkout. A hotel wholesaler that also sells through agent portals can use Voraal's Rezencia for agents and Avunzo for partners with their own systems. Rezencia users also get hotel price-drop rebooking; ask during discovery which post-booking features are exposed through the API. For the request lifecycle behind every hotel call, read how travel APIs work.
Implementation process
- 01
Define your markets
List the destinations that matter to your customers. Hotel coverage per source is confirmed during discovery.
- 02
Build search and content display
In the sandbox, build the property page from normalised content and decide how to show multiple rates for one hotel.
- 03
Handle policy and payment terms
Display cancellation deadlines clearly and store them on your side for customer service.
- 04
Test cancellations and go live
Run book-and-cancel scenarios, including late cancellations, before production credentials are issued.
Common challenges
Typical hotel integration problems
- Duplicate hotels from overlapping sources
- Room names that do not match across suppliers
- Cancellation deadlines shown in the wrong time zone
- Taxes payable at the property left out of the total
- Rates that expire between search and booking
How the API and your app share the load
- Avunzo maps properties into one normalised record
- Show board basis and occupancy alongside the room name
- Display deadlines with the hotel's local date and time
- Present pay-at-hotel charges as a separate line
- Re-check the rate immediately before booking
How Voraal delivers this
The products behind it.
Where does the hotel inventory come from?
From hotel aggregators, bedbanks and direct chain connections connected to the Voraal core, plus your own contracted rates if you load them in Rezencia. Voraal does not publish a list of named hotel suppliers; coverage for your markets is confirmed during discovery.
How are duplicate hotels handled when two sources sell the same property?
Avunzo normalises property content so that offers from different sources for the same hotel can be shown under one property, letting customers compare rates for the same building rather than seeing it twice.
Can we combine hotels with flights in one booking?
Yes. Dynamic packages bundle flights, stays and ground services through the same API, with package pricing in one call and one order and confirmation.
What does the hotel booking API return for cancellation terms?
Each rate carries its cancellation terms with real-time pricing, so you can show the deadline and any penalty before the guest books.
Do guests pay us or the hotel?
That depends on the rate and the source. Most API-sold rates are prepaid through your platform, while some taxes or fees may be payable at the property. Your checkout should show both clearly.
Let’s build what comes next.
Tell us how your travel business works. We’ll recommend the right products and walk you through them on your own use case.