Live demo

Supplier directory and integration guide

Travel XML API suppliers list for bedbanks, wholesalers, GDS and more

A filterable register of hotel bedbanks, wholesalers, DMCs, GDS providers, attraction, car rental and cruise suppliers that distribute through XML or JSON APIs, with the regions they serve, how access works, and the qualification, mapping and dedupe steps that take a shortlist to live sales.

  • Filter by category and brand
  • Supplier type comparison
  • Readiness scorecard
  • Five-step integration flow

The register

Travel XML API suppliers list by category

Filter the travel XML API suppliers list by category or type a brand name. Each row shows the supplier type, the regions where its inventory is strongest and how connectivity is granted.

Rows link to the detailed guides where one exists, such as Hotelbeds API integration and Bedsonline integration. For the GDS side read GDS system for travel agents, and for the way every feed enters the platform see Travel API integration.

25/25suppliers shown

SupplierTypeRegionsAccessNotes
HotelbedsBedbankGlobalXML or JSON APIApitude and HotelX distribution; a common primary source for broad coverage
YalagoBedbankGCC and global leisureXML or JSON APIStrong leisure rates on Gulf routes and outbound leisure
BedsOnlineWholesalerEurope and AmericasXML or JSON APITrade-only access with contracted rates
SunhotelsBedbankEuropeXML or JSON APICity and leisure hotel portfolio
Miki TravelWholesalerGlobalXML or JSON APIGroups and FIT programmes
YouTravelWholesalerEurope and MediterraneanXML or JSON APILeisure inventory with live availability and board types
TouricoWholesalerGlobalXML or JSON APINow part of the Hotelbeds group
Travco DubaiDMCUAE and MENAXML or JSON APIDMC contracts and inbound services for the UAE and nearby markets
VOTBookingsWholesalerEuropeXML or JSON APISelective inventory by contract; often a secondary price-check source
DOTWWholesalerMiddle East and globalXML or JSON APIAccount-based endpoints and rules
RoomsXMLAggregatorGlobalXML or JSON APINeeds a mapping and dedupe policy before go-live
W2MWholesalerSpain and EuropeXML or JSON APILeisure city and beach mix
DidaTravelWholesalerAsia PacificXML or JSON APIAsia Pacific strength with multi-currency support
AC ToursDMCGlobalPartner programmePartner-enabled inventory for group series and contracted programmes
AmadeusGDSGlobalXML or JSON APIAir distribution with a global footprint; setup requirements vary by market
SabreGDSGlobalXML or JSON APIBroad air content with ancillaries and branded fares by programme
TravelportGDSGlobalXML or JSON APIGalileo and Worldspan; air, hotel and car distribution
Attraction WorldAttractionsUnited KingdomXML or JSON APIAggregated tickets and vouchers delivered through API
Do Something DifferentAttractionsUnited KingdomPartner programmeExperiences catalogue for resellers with market-specific enablement
Tourico AttractionsAttractionsGlobalPartner programmeActivities portfolio through partner programmes
AvisCar rentalGlobalPartner programmeFleet, rates, extras and voucher flows through partner connectivity
Holiday TaxisTransfersGlobalXML or JSON APIShared and private transfers with booking and vouchering
RCCL GroupCruise lineGlobalPartner programmePartner-based access to sailings, fares, cabins and booking flows
MSC CruisesCruise lineGlobalPartner programmeMarket-specific enablement for cruise content and booking
Princess CruisesCruise lineUnited KingdomPartner programmePremium cruise products with partner distribution programmes

No supplier matches that search. Clear it or pick another category.

Regions and notes are an editorial summary of public supplier information. Confirm coverage, commercial terms and API access with each supplier before you plan an integration.

Quick supplier selection

Build a supplier stack around how you sell

Most agencies combine two to four suppliers rather than one. Pick the model closest to yours and the layers below show which supplier types to put first, second and alongside.

Sales model

The stack runs inside one platform: the Hotel booking engine handles the hotel feeds and the Flight booking software handles the GDS side, each with its own markups and routing rules.

  1. 01Primary sourceOne bedbank with global content and clean hotel codes gives you most cities on day one.Examples from the listHotelbedsYalagoSunhotels
  2. 02Secondary sourceOne wholesaler for price checks and gaps, routed only where it wins or where the bedbank has nothing.Examples from the listVOTBookingsYouTravelDOTW
  3. 03AlongsideA routing rule that names the primary supplier per region so the same hotel never appears twice.Examples from the listRoomsXML
  1. 01Primary sourceA DMC supplier for contracted hotels, transfers and services in your core destinations.Examples from the listTravco DubaiAC ToursMiki Travel
  2. 02Secondary sourceA bedbank to fill the destinations your DMC contracts do not cover.Examples from the listHotelbedsDidaTravel
  3. 03AlongsideAttraction and transfer feeds so a package can be priced and vouchered end to end.Examples from the listAttraction WorldHoliday Taxis
  1. 01Primary sourceA GDS for fares, ancillaries and PNR management, under your own agreement and market setup.Examples from the listAmadeusSabreTravelport
  2. 02Secondary sourceA bedbank layered on the flight search so hotels can be added to the same booking.Examples from the listHotelbedsBedsOnline
  3. 03AlongsideCar rental and transfer suppliers for the ground side of the itinerary.Examples from the listAvisHoliday Taxis

Supplier types

Compare supplier types and when to use them

A quick way to decide between bedbanks, wholesalers, DMC suppliers, GDS providers and aggregators before you request credentials.

OptionBest forTrade-offsHow PHPTRAVELS helps
BedbanksBest forFast hotel coverage at scale with net ratesTrade-offsDuplicates across sources and cancellation rules that differ per contractHow PHPTRAVELS helpsRouting, hotel code mapping, dedupe and markup controls per supplier
WholesalersBest forCurated trade inventory and price checksTrade-offsMarket-limited access and account requirementsHow PHPTRAVELS helpsMulti-supplier setup with fallback rules by market
DMC suppliersBest forDestination services, groups and inbound operationsTrade-offsDestination-specific coverage and contract-heavy onboardingHow PHPTRAVELS helpsService packaging and operational workflow for vouchers and amendments
GDS providersBest forAir distribution, complex fares and ancillariesTrade-offsSetup, certification and compliance requirements vary by regionHow PHPTRAVELS helpsUnified booking flow with PNR storage and back-office readiness
AggregatorsBest forLarge catalogues through one contractTrade-offsLess control over sources and higher reconciliation effortHow PHPTRAVELS helpsNormalisation and policy enforcement across every feed

Integration readiness

Qualify a supplier before you request credentials

A successful supplier integration is more than rates and availability. Tick what the supplier has confirmed in writing; a group that scores below three usually needs another conversation before you go live.

0/16checks confirmed

Scores are kept in this browser tab only and reset when you reload.

Commercial terms0/4

Technical quality0/4

Operations readiness0/4

Security and compliance0/4

Integration flow

From shortlist to live sales in five steps

An operational flow that reduces failed bookings, duplicate content and margin leakage. The XML window shows where each step leaves its mark on a real availability call.

  1. 01

    Qualify

    Confirm coverage, commercial model, cancellation rules and support expectations with the scorecard above.

  2. 02

    Credentials

    Obtain sandbox keys, IP allowlist rules and a test hotel list so every team validates against the same data.

  3. 03

    Map

    Normalise hotel codes, currencies, taxes and board types so search results match what the voucher will say.

  4. 04

    Dedupe

    Name a primary supplier per region and apply routing rules so results stay clean and fast.

  5. 05

    Go live

    Run booking and cancellation tests, train operations, then enable production traffic supplier by supplier.

Availability call

<?xml version="1.0" encoding="UTF-8"?><AvailabilityRQ supplier="hotelbeds">  <Credentials user="PT_AGENCY_01" key="••••••••" />  <Stay checkIn="2026-11-12" checkOut="2026-11-15" />  <Occupancy rooms="1" adults="2" children="0" />  <Destination code="DXB" masterId="DST-7731" />  <Currency>USD</Currency>  <Markup rule="b2c-default" /></AvailabilityRQ>
<AvailabilityRS supplier="hotelbeds" elapsed="412ms">  <Hotel code="118742" masterId="HTL-35611">    <Room board="BB" currency="USD" net="184.00" sell="206.08" />    <Cancellation deadline="2026-11-09" fee="184.00" />  </Hotel>  <Hotel code="Y-55120" masterId="HTL-35611" supplier="yalago"         role="fallback" visible="false" /></AvailabilityRS>

Sample elements and values; every supplier uses its own schema and the platform maps them to one internal shape.

  1. 1Each supplier gets its own credentials and IP allowlist; keys are stored per supplier, never shared.
  2. 2Destination and hotel codes are mapped to one master identifier so two feeds can describe the same property.
  3. 3Net rate, currency and board type are normalised before markup so the sell price is consistent.
  4. 4Cancellation deadlines and fees are captured on the search result, not discovered at booking time.
  5. 5A second feed for the same master id is kept as fallback and hidden from the customer by the routing rule.

Sample routing rules

RegionPrimary supplierFallbackGCC and global leisureYalagoHotelbedsEurope and MediterraneanYouTravelSunhotelsUAE and MENATravco DubaiDOTWAsia PacificDidaTravelHotelbedsGlobalHotelbedsRoomsXML

Illustrative pairs drawn from the list above. Your own rules follow your contracts, margins and the markets you sell most.

Already connected

Suppliers with a ready integration in PHPTRAVELS

The directory above is the market. This is the list of suppliers that already have a connector in the platform, read live from the integrations catalogue, so a supplier added by the team appears here without a release.

Flights11

  • Seeru
  • Amadeus
  • Duffel
  • Google Flights
  • Kayak
  • Kiwi
  • Mystifly
  • PKfare
  • Sabre
  • TBO Holidays
  • Travelport

Hotels10

  • Agoda
  • Amadeus
  • Booking.com
  • Hotelbeds
  • Hotelston
  • RateHawk
  • Stuba
  • TBO Holidays
  • Travelport
  • Wanderbeds

Tours and activities3

  • Tiqets
  • Tours BMS
  • Viator

Cars and transfers4

  • KiwiTaxi
  • CarTrawler
  • Discover Cars
  • Mozio

Rail1

  • HKINT

Ferries1

  • Kikoto Ferries

eSIM1

  • Airalo

A supplier from the list that is not here can still be connected: see Custom API integration for how a new feed is scoped, and All integrations for the full catalogue.

Connect your shortlist on a platform built for multi-supplier sales

Source code included under a commercial licence and self-hosted on your servers. Plans are one-time, from the Startup licence on the Pricing page, and every plan carries the routing, mapping and markup controls described here.

Open the live demoTalk to an integration specialist

Keep reading

Supplier questions

Travel XML API suppliers list FAQ

What agencies ask before they shortlist suppliers and request credentials.

Talk to sales

A travel XML API supplier distributes inventory through integration endpoints that support search, pricing, booking and post-booking actions such as cancellations and amendments. Hotel bedbanks, wholesalers, DMCs, GDS providers, attraction platforms, car rental companies and cruise lines all distribute this way, some with XML schemas and some with JSON.

Use bedbanks for broad hotel coverage, wholesalers for trade inventory and price checks, and DMC suppliers for destination services and group operations. Many travel businesses combine two to four suppliers and apply routing rules by market, as the stack builder on this page shows.

Yes. Each supplier issues its own account, keys and commercial terms, and several also require an IP allowlist. After approval you add the credentials in the admin panel, map currencies and markets, then complete test bookings before you switch the supplier to production.

For a supplier that already has a connector in PHPTRAVELS, the work is credentials, mapping and test bookings, which is typically a matter of weeks after the supplier issues keys. A new feed takes longer because the schema has to be scoped and mapped first, and multi-supplier setups add routing and dedupe rules.

Map every supplier hotel code to one master identifier, name a primary supplier per market and apply routing rules so the same property is returned once. Keep the other feeds as fallback for coverage gaps and price checks rather than showing them side by side.

The connected section on this page is read live from the integrations catalogue and lists every supplier with a ready connector by category. A supplier from the directory that is not there yet can be added as a custom API integration, scoped from its documentation.

Keep exploring

More from the platform