Supplier and service API hub
Travel APIs connected to one booking platform
Every travel API guide on this site in one place: GDS and airline content, hotel bedbanks and extranets, tours, cars and transfers, payment gateways and back-office tools. Filter the directory by category, compare the three ways to source inventory and follow the path an integration takes from sandbox keys to live sales.
- Integration guides by category
- Search, price, book, ticket flow
- APIs vs booking engine vs GDS
- Self-hosted with source code
In short
What travel APIs are and where they fit
Three terms come up on every page of this hub. Here is what each one means before you pick a supplier.
If you are new to the subject start with What is API integration, then read the technical walkthrough in Travel API integration. The full list of ready connectors lives on All integrations, and the booking modules that consume them are described under Platform overview.
Travel API
A programmatic endpoint that returns searchable travel data such as availability, fares, rules and content for flights, hotels, cars or tours, usually as JSON or XML.
Travel API integration
Wiring a supplier, GDS or aggregator endpoint into a booking engine: authentication, field mapping, idempotent booking calls and error and retry policies.
Self-hosted connectors
PHPTRAVELS ships its connector code with the licence, so your team can read, extend and host the adapters that talk to each supplier.
The call sequence every supplier shares
- 01Search
- 02Price and revalidate
- 03Book
- 04Ticket or confirm
Supplier names and response shapes differ, but each connector in the directory below maps onto this same four-call sequence.
The directory
Travel APIs by category
Pick a category to narrow the list. Each entry opens a dedicated guide to that supplier or service, what it returns and how it is set up on the platform.
GDS, airline and flight APIs
Global distribution systems, NDC, low-cost carrier aggregators, consolidators and flight data services for the flights module.
- Flights APIGDS, NDC and consolidator flight APIs on one platform
- Amadeus API integrationChoose your Amadeus access and sell flights in your own portal
- Sabre API integrationSabre APIs for shop, price, book and ticket in your portal
- Travelport API integrationTripServices flights, branded fares, PNRs and servicing
- Galileo reservation systemGalileo holds, ticketing and after-sales in one admin
- Apollo GDS softwareApollo fares, PNRs and ticketing via Travelport
- NDC flights booking systemSell NDC airline offers, ancillaries and servicing
- Amadeus connector setupKeys, environments and setup for the Amadeus module
- Duffel API integrationDuffel flight offers and orders in your booking site
- Kiwi API integrationKiwi.com Tequila flight search and booking
- TBO flights APITBO air fares, recheck and ticketing in your engine
- PKFARE API integrationPKFARE flight search, booking and PNR in your portal
- Riya travel booking platformB2B agents, corporate travel and retail in one
- IndiGo airline ticketsSell and service IndiGo fares through flight APIs
- Google Flights APIWhy there is no public API and what to use instead
- Kayak affiliate programReferral model, limits and owned alternatives
- Flight status APILive flight status and tracking inside your platform
- Amadeus central reservationsOne reservation core for Amadeus and your own stock
- Amadeus travel agent softwareSearch, PNR, ticketing and after-sales in one portal
- Sabre agent softwareThe daily Sabre desk: queue, servicing, roles, invoices
- Galileo softwareGalileo booking, ticketing and servicing workflows
- Abacus GDSWhat became of Abacus and how to sell its content via Sabre
- AERTiCKET API integrationConsolidator net fares from AERTiCKET in your flight engine
- WegoWego metasearch profile and how to connect it
- DohopDohop virtual interlining profile and how to connect
- Cleartrip API integrationCleartrip supplier profile and how to connect it
- TravelstartTravelstart profile and a custom connector plan
- Arzoo APIWhat happened to Arzoo and the live supplier routes for India
Hotel APIs, bedbanks and extranets
Wholesale bedbanks, OTA affiliate programmes, extranets and channel managers that fill the hotel search with rooms and rates.
- Hotels APIBedbank, OTA, GDS and direct hotel APIs explained
- Stays APIHotels, apartments and vacation rentals in one accommodation API
- Hotelbeds API integrationContent and Booking APIs, rate checks and hotel mapping
- RateHawk API integrationRateHawk hotels in your booking engine, ready connector
- Bedsonline integrationBedsonline hotels and agent rates in your engine
- TBO hotel API integrationTBO Holidays hotel rates in your booking engine
- Hotelston API integrationHotelston hotel rates in your booking engine
- Go Global Travel integrationGo Global hotels, transfers and cars in your engine
- Bonotel travel agentLuxury U.S. hotels for your agents and portal
- Mark travel booking engineHotel search, Saudi transfers and agents in one
- Expedia API integrationExpedia Rapid API hotels in your booking engine
- Expedia TAAP API integrationTAAP hotels, commissions and changes in your portal
- Expedia ExtranetPartner portal for rates, inventory and bookings
- Booking.com ExtranetRates, availability, reservations and payouts
- Agoda API integrationAgoda hotels and homes in your booking engine
- Booking.com and Priceline APIsBooking.com, Priceline and Expedia hotel API access
- Hotel booking system APIMany hotel suppliers through one booking API
- Channel manager integrationSync hotel rates, availability and bookings
- TBO Holidays supplier profileWhat TBO sells and how to connect it to PHPTRAVELS
- Hotelbeds supplier profileWho Hotelbeds is and how to connect it to PHPTRAVELS
- GTA (now Hotelbeds)What happened to GTA and how to reconnect its inventory
- Booking.com supplierPartner access, what you can sell and how to connect
- Priceline hotel API providerPriceline Partner Network and how to connect it
- Grupo TranshotelSupplier profile, its 2014 closure and live hotel API options
Tours, attractions, cars and transfers
Activity marketplaces, car rental brokers and transfer suppliers that add ancillaries next to flights and stays.
- Tours APITours, activities and attraction tickets through one API
- Cars APICar rental and transfer APIs in one booking engine
- Transport APITransfers, rail, bus and ferry APIs for door-to-door trips
- Cruises APISailings, cabins and deposits from a cruise API or your own contracts
- Ferries APIFerry timetables, availability and tickets through an API
- Viator API integrationViator tours and activities in your booking site
- Airalo API integrationSell Airalo eSIMs on your travel website, ready connector
- Viator travel agentPortal, commission and a connected tour workflow
- Tiqets API integrationTiqets attraction tickets in your booking engine
- CarTrawler API integrationCarTrawler car rentals booked inside your platform
- CarTrawler supplier profileWho CarTrawler is and how it plugs into your cars module
- Sixt car rentalTwo ways to sell Sixt cars on a PHPTRAVELS site
- Alamo Rent A Car APISupplier profile and how to connect Alamo cars
Payments, CMS, accounting and integration tools
Payment gateways, bank and custom APIs, accounting exports and content management connectors that sit around the booking flow.
- Payment gateway APIHow card payments, 3-D Secure, captures and refunds work over an API
- Razorpay integrationConnect Razorpay to a travel booking site as a custom gateway
- Paddle API integrationMerchant of record vs payment gateway, and when Paddle fits
- Travel API integrationConnect XML and JSON travel suppliers in PHP
- Custom API integrationConnect any supplier or partner API to PHPTRAVELS
- Payment gateway integrationCheckout, 3D Secure, refunds and webhooks
- Stripe paymentsCard and wallet checkout with refunds and payouts
- PayPal paymentsPayPal checkout for flights, hotels and tours
- Bank transfer paymentsBank transfer checkout with manual confirmation
- Travel accounting integrationBookings posted to QuickBooks, Xero and Tally
- Travel CMS integrationConnect WordPress or a headless CMS to booking
Three ways to source inventory
Travel APIs vs booking engine vs GDS API
Teams often weigh a direct API, a packaged booking engine and a raw GDS contract as if they were the same purchase. They solve different problems and are usually combined.
| Criteria | Travel APIs | Booking engine | GDS API |
|---|---|---|---|
| Purpose | Travel APIsData and operations through endpoints | Booking engineFront end, business rules and checkout | GDS APIAir content and ancillaries through legacy and NDC channels |
| Content scope | Travel APIsHotels, flights, cars, activities, bedbanks | Booking engineSearch to checkout for whatever is connected | GDS APIMainly airlines and their ancillaries |
| Integration effort | Travel APIsMedium: field mapping, idempotency, retries | Booking engineMedium to high when built from scratch; low on PHPTRAVELS | GDS APIHigh: PCC setup, queues, certification and audits |
| Commercials | Travel APIsPer call, markup or seat based, set by the supplier | Booking engineOne-time licence on PHPTRAVELS, plus gateway fees | GDS APIGDS contracts, incentives and segment targets |
| Best for | Travel APIsOTAs and DMCs mixing several suppliers | Booking engineSelling directly with your own brand and rules | GDS APIAir-heavy agencies and travel management companies |
| Time to market | Travel APIsFast once credentials are issued | Booking engineInstall, connect suppliers, brand and launch | GDS APILongest, because approval and certification come first |
PHPTRAVELS is the booking engine column: the supplier APIs and any GDS contract plug into it, so you buy the software once and add feeds as your contracts arrive. Pricing is on Pricing; the hosting side is covered under Requirements.
From keys to live sales
How an API integration goes live
The rail below is the order of work for any supplier in the directory, with the request and response that the platform exchanges once the connector is switched on.
- 01
Credentials
Sign the supplier agreement and receive sandbox keys, endpoints and the documentation set.
- 02
Sandbox connection
Enter the keys in the admin panel, run the first search and confirm the connector can read the response.
- 03
Content mapping
Match supplier codes to the platform master data: airports, hotel ids, room boards, vehicle classes.
- 04
Markups and rules
Set markups, taxes, fees and currency rules per agency, per B2B agent or per customer group.
- 05
Test bookings
Complete the supplier's certification scenarios: book, modify, cancel and reconcile against their test console.
- 06
Production keys
Swap to live credentials, enable the supplier for the public site and the B2B portal, then monitor the first bookings.
One revalidation call, as the platform sends it
{"supplier": "hotelbeds",1"env": "production",1"rateKey": "HB-20261112-118742-DBL-BB","occupancy": { "rooms": 1, "adults": 2 },"currency": "USD","markupRule": "b2c-default"2}
{"status": "available","net": 184.00,2"sell": 206.08,2"currency": "USD","cancellation": { "deadline": "2026-11-09", "fee": 184.00 },"hold": "PT-HLD-7731",3"expiresIn": 9003}
- 1
Supplier keys are stored per environment, never in the request body you ship to customers.
- 2
Net and sell prices travel together; the markup rule name tells the back office why they differ.
- 3
A hold reference lets the booking call stay idempotent if the customer retries payment.
- See the integration walkthrough
Pick by business model
Which travel APIs each kind of business connects first
The directory is long because travel businesses differ. These are the usual starting combinations we see at onboarding.
- 01
Online travel agency
A GDS or NDC feed for flights, one or two bedbanks for hotels, a car broker and a card gateway. Breadth first, then direct contracts.
- 02
Destination management company
Own inventory loaded in the admin, a bedbank for gaps, a tours marketplace and transfers. Flights are often added later through a consolidator.
- 03
Corporate travel management
GDS content with negotiated fares, a hotel programme through an extranet or bedbank, approval rules and accounting export.
- 04
Consolidator or B2B wholesaler
Multiple air sources with markups per sub-agent, an agent wallet, bank transfer and gateway payments, and an accounting feed.
Each model is described on its own page: Online travel agencies, DMCs and Corporate travel; the sub-agent credit side of a wholesaler is covered under Agent wallets. The white-label layer that distributes any of these feeds to partners is described under White-label B2B portal.
Questions
Travel APIs, answered
Short answers to what buyers ask before choosing suppliers.
Talk to salesTravel APIs are endpoints that expose live inventory, prices, rules and operations such as search, revalidate, book and cancel from suppliers, GDS providers and aggregators. A booking platform calls them and turns the responses into a search result, a basket and a confirmed booking.
Authentication with the supplier's keys, mapping its codes to your master data, calling search, price and book in order, handling errors and retries without duplicate bookings, and feeding the result to payments, vouchers and accounting. On PHPTRAVELS the connectors already implement this; your work is credentials, mapping and rules.
Yes. The platform is self-hosted and the source code is included under a commercial licence, so your developers can read every adapter, add a supplier that is not in the directory yet or change how an existing one maps content.
Usually a mix rather than one feed: a low-cost carrier aggregator for breadth, NDC or GDS content for full-service airlines and ticketing, and a consolidator where you lack your own airline contracts. The flights group of the directory lists guides for each option.
Several per module. The platform queries each enabled supplier, merges the results by master id, removes duplicates and applies your markup rule before showing a price, so adding a second bedbank or a second air source is a configuration change, not a rebuild.
The APIs themselves are priced by their suppliers, typically per call, per booking or through a markup agreement; some are free with an affiliate programme. The PHPTRAVELS software that connects them is a one-time licence as listed on the pricing page.