Live demo

Multi-supplier hotel API

Hotel booking system API: many hotel suppliers, one engine

Every bed bank, GDS hotel module and channel manager has its own API, data model and errors. PHPTRAVELS normalises them into one search, pre-book, booking and cancellation flow for your website, agent portal and integrations.

  • One normalised API layer
  • Content mapping and deduplication
  • Pre-book rate checks
  • B2C and B2B from one engine

What it does

What a hotel booking system API does in plain terms

A hotel booking system API sits between your hotel suppliers and the screens where customers and agents book. Instead of building search, rate checks, booking and error handling once per supplier, you connect each source once and PHPTRAVELS returns one result set, applies your pricing rules and runs the same confirmation flow whether the room comes from Hotelbeds, a GDS, a channel manager or a direct contract.

  1. Add credentials and endpoints for each hotel supplier, REST or SOAP
  2. Import static content and map properties so the same hotel appears once
  3. Set markups, commissions, taxes and cancellation rules per supplier and channel
  4. Use the ready search and checkout, or call the API from your own front end
  5. Activate payments, vouchers and notifications, then monitor supplier errors
Try the hotels demoSee pricing
Supplier
Hotelbeds · Bed bank
Environment
Test
Credentials
API key: •••• · Secret: ••••
Static content sync
Nightly import · Mapping on
Markup
B2C 12% · B2B 6%

Booking flow

From search to cancellation through one API

The same steps run whether the request comes from your B2C site, the B2B portal or a third-party integration.

  1. Search

    Destination, dates and occupancy sent to every connected supplier.

  2. Check rates

    The chosen room is re-priced with its current cancellation penalty.

  3. Pay

    Card, wallet or agent credit captured and linked to the booking record.

  4. Book

    The reservation is created and the supplier reference stored.

  5. Voucher and invoice

    Confirmation, voucher and accounting entry produced in one step.

  6. Amend or cancel

    Booking detail, amendments and cancellations with the applicable fee.

Supplier layers

Every layer of hotel distribution behind one interface

Each source differs in coverage, pricing model and content quality. Mix them for your market and let the API layer hide the differences.

  • Bed banks and wholesalers

    Hotelbeds, Hotelston, Stuba and regional wholesalers with contracted net rates and rich content APIs.

  • GDS and OTA feeds

    Amadeus, Sabre and Travelport hotel modules, plus Booking.com, Expedia and Agoda feeds for long-tail coverage.

  • Channel managers and contracts

    SiteMinder-connected hotels with live rates and availability, and your direct contracts loaded as own inventory.

Hotel suppliers you can connect:

  • Agoda
  • Amadeus
  • Booking.com
  • Hotelbeds
  • Hotelston
  • RateHawk
  • Stuba
  • TBO Holidays
  • Travelport
  • Wanderbeds
See every hotel integration

Back office

Pricing, credit and records across all suppliers

One admin replaces the separate supplier portals, spreadsheets and invoice tools agencies juggle as they grow.

  • Markup per channel

    Markups, commissions and taxes per supplier, destination, agent group and channel.

  • Agent credit limits

    Per-agency credit, deposits and booking caps checked during the booking flow.

  • Roles and access

    Customers, agents, sub-agents and corporate buyers each see their own rates and permissions.

  • Margin per booking

    Supplier cost, selling price and margin recorded in one transaction log.

  • Audit trail

    Every booking, change and cancellation logged against the user who made it.

  • Vouchers and invoices

    Produced in one system and linked to each booking reference.

Compare

Building hotel supplier APIs in-house vs PHPTRAVELS

Some teams code each hotel supplier themselves. This is typically what that involves, next to a ready multi-supplier booking system.

AreaCustom in-house buildPHPTRAVELS
Supplier coverageCustom in-house buildEach new bed bank or GDS is a separate integration projectPHPTRAVELSBed banks, GDS hotels, channel managers and OTA feeds in one admin
Content and mappingCustom in-house buildImport and mapping pipeline built separatelyPHPTRAVELSContent imported, mapped and deduplicated across sources
B2B pricingCustom in-house buildMarkup, credit and commission engine designed from scratchPHPTRAVELSPer-agency markup, credit and commission built in
Booking engineCustom in-house buildSearch, checkout and agent portal still to buildPHPTRAVELSB2C site and B2B portal ready, with full branding control
MaintenanceCustom in-house buildYour team owns every supplier API changePHPTRAVELSPlatform updates from PHPTRAVELS, with the source code in your hands
Other productsCustom in-house buildFlights, tours and transfers are new projectsPHPTRAVELSFlights, tours, cars and more as modules in the same installation

Use cases

Who runs hotels on one booking API

  • OTAs

    Large hotel catalogues from several suppliers, deduplicated and sold next to flights.

  • B2B agencies and wholesalers

    Sub-agents book net rates with their own markup, credit and vouchers.

  • Package builders

    Bed bank rooms combined with tours and transfers in one itinerary and checkout.

Why PHPTRAVELS

Your suppliers, your rules, your code

  • Source code included

    Self-hosted under a commercial licence, so your developers can extend any supplier flow.

  • One-time licence

    Plans from $2499 one-time, with no platform fee on every booking.

  • Travel-specific logic

    Pre-book, rate check, allotment, board type and cancellation penalties are built-in concepts.

  • Your supplier accounts

    You hold the supplier agreements and keys, stored in your own installation.

FAQ

Hotel booking system API questions

What agencies and OTAs ask before connecting several hotel suppliers.

Talk to sales

It connects your website or agent portal to hotel suppliers through standard calls for search, availability, rate checks, booking, amendment and cancellation, so you work through one layer instead of separate supplier portals.

Typically search, check rates or pre-book, book, booking detail and cancel. Many suppliers also offer a static content endpoint for descriptions, images and amenities that is imported in bulk.

A content API delivers static data such as names, stars, amenities and images, imported nightly or weekly and served from cache. A booking API returns live availability, rates and penalties on every search. PHPTRAVELS uses both.

A mapping layer, such as GIATA, assigns one internal ID to each property during content import. A hotel sold by two suppliers then appears once, and the booking goes to the supplier holding the selected rate.

Bed banks such as Hotelbeds, Hotelston and Stuba, GDS hotel modules from Amadeus, Sabre and Travelport, OTA feeds such as Booking.com and Agoda, channel managers such as SiteMinder, and your own contracts. Access depends on the agreements you hold with each supplier.

The API is the back-end layer that connects suppliers, normalises data and applies pricing rules. The booking engine is the screen where customers and agents search and book. PHPTRAVELS includes both, with the source code.

Keep exploring

More from the platform