Flight API integration
TBO flights API integration from search to e-ticket
Connect your TBO account to the PHPTRAVELS flights module and sell TBO air fares on your website and agent portal. Every fare is rechecked before payment, every call carries a trace ID, and your team gets the logs, retry rules and booking tools that keep daily flight sales stable.
- Live TBO air fares
- Price recheck before payment
- Trace ID on every call
- B2C checkout and B2B portal
What you sell
TBO flights API integration inside your own booking engine
TBO is a B2B travel distributor whose air API returns flight fares that travel companies can resell. The PHPTRAVELS flights module calls it with your own TBO credentials, shows the fares in your search results and runs the whole booking: fare rules, price recheck, passenger details, payment, booking and ticket.
Fares do not all behave the same. Depending on the fare, some (often low-cost carriers) are booked and ticketed in one step, while others can be held as a booking and ticketed later. The module keeps that difference visible to your team so no fare is charged without the right next step.
- LCC06:10 – 08:253h 45m · Non-stop₹18,450Select
- FSC09:40 – 11:503h 40m · Non-stop₹21,980Select
- FSC21:15 – 23:353h 50m · Non-stop₹26,300Select
Sample fares. Each result keeps its supplier tag, so support always knows the source.
Call chain
Six calls between a search and a ticket
Pick a step to see what comes back from TBO, what PHPTRAVELS does with it and what usually goes wrong there.
Search
- What comes back
- Fares for the route, dates, cabin and passenger mix, each with a result token for the next calls.
- What PHPTRAVELS does
- Normalises results, applies your markup, caches the search and adds filters for airline, stops, baggage and departure time.
- What can go wrong
- Stale cached fares shown for too long. The cache is short and every later step rechecks.
Fare rules
- What comes back
- Change and cancellation conditions, baggage allowance and fare notes for the selected fare.
- What PHPTRAVELS does
- Shows the rules on the fare card and again before payment, in plain language where the supplier gives structured data.
- What can go wrong
- Customers buying a fare they did not understand, then asking for refunds the fare does not allow.
Price recheck
- What comes back
- The current price and availability of the fare the customer selected.
- What PHPTRAVELS does
- Compares it with the shown price. Same price continues; a higher price asks the customer to confirm; a gone fare returns them to results.
- What can go wrong
- Charging the old price for a fare that changed, which leads to disputes and manual refunds.
Extras
- What comes back
- Seats, meals and extra baggage where the airline and fare offer them.
- What PHPTRAVELS does
- Lists the options with their prices and adds them to the booking total before payment.
- What can go wrong
- Extras sold that the fare cannot carry. Only returned options are offered.
Book
- What comes back
- A booking reference, or a failure reason when the seat or price is no longer there.
- What PHPTRAVELS does
- Stores the booking with its trace ID, passenger data and payment record, and starts the booking timeline.
- What can go wrong
- A timeout after payment. The module queries the booking status before it ever sends a second booking.
Ticket
- What comes back
- E-ticket numbers for each passenger once the airline issues them.
- What PHPTRAVELS does
- Saves the ticket numbers, emails the itinerary and opens the booking for changes, cancellations and refunds.
- What can go wrong
- Held bookings left unticketed until they expire. Held bookings carry a deadline your team can see.
Price recheck
The fare is checked again before anyone pays
Most failed flight bookings start with a price that changed between search and payment. Try the three outcomes the checkout handles.
Checkout rules
- 01Every fare is rechecked with TBO before payment is taken.
- 02Payment is captured once per trace, never again on a retry.
- 03Fare rules and baggage are shown again on the payment step.
- 04When a fare is gone, the search and passenger details are kept.
Payment flows:Payment gatewaysAgent wallets
- Price at search
- ₹18,450
- Price at recheck
- ₹18,450
- Difference
- ₹0
Payment goes ahead at the price the customer saw.
- Price at search
- ₹18,450
- Price at recheck
- ₹19,120
- Difference
- ₹+670
The customer sees the new price and confirms it before payment. Nothing is charged until they do.
- Price at search
- ₹18,450
- Price at recheck
- Not available
- Difference
- —
The customer returns to fresh results with the same search and passenger details already filled in.
Example figures for one adult.
Operations
One trace ID follows the booking through every call
When a booking needs attention, support opens its trace and reads what happened in order, instead of asking a developer to search server logs.
trace TBO-FL-7Q2K9 --route DEL-DXB --pax ADT1
- 10:02:11INFOsearchresults cached for this search
- 10:03:40INFOrulesfare rules and baggage attached to the selected fare
- 10:05:02WARNrecheckprice changed, customer asked to confirm the new fare
- 10:05:31OKrecheckcustomer accepted the new fare
- 10:06:12INFOpaypayment captured once for this trace
- 10:06:19WARNbooksupplier timeout, status query sent instead of a second booking
- 10:06:27OKstatusbooking confirmed by status query, reference stored
- 10:06:40OKtickete-ticket numbers saved, itinerary emailed
A sample trace: the price changed, the customer accepted it, the booking call timed out and a status query confirmed it without booking twice.
Request logs and trace IDs
Each search, recheck, booking and ticket call is logged under one reference so issues are isolated quickly.
Test route library
A fixed set of routes, dates, cabins and passenger mixes you run after every change.
Timeout and retry policy
Recovers from short network failures without the risk of a double booking.
Alerts on failure spikes
Your team is notified when error rates rise, before sales are affected.
Go-live plan
Five steps to selling TBO fares
Teams lose weeks when they find missing operational needs late. This plan puts them first.
- 01
Access and credentials
Open your TBO account, request flight API access and receive test credentials.
- 02
Connect and validate
Add the credentials in the admin, set timeouts and run the test route library.
- 03
Search and price control
Set markups, currencies and filters, and confirm that rechecked prices match checkout.
- 04
Book and confirm
Test passenger details, payment, booking, ticketing and itinerary emails end to end.
- 05
Operate and scale
Switch to live credentials, set alerts and support steps, then open traffic.
Test route library
| Route | Trip | Passengers | Cabin | What it proves |
|---|---|---|---|---|
| DEL → BOM | OW | 1 ADT | Y | A baseline domestic fare and instant ticketing |
| BOM → DXB | RT | 2 ADT · 1 CHD | Y | Child pricing and outbound-return pairing |
| DEL → LHR | RT | 1 ADT · 1 INF | Y | Infant pricing and passport fields |
| BLR → SIN | OW | 1 ADT | C | Business cabin fares and their rules |
| HYD → JED | OW | 2 ADT | Y | Baggage rules on a long sector |
Use the routes you actually sell; these are examples.
Delivery support when you want it
- Kickoff and scopeRoutes, markets, pricing rules and workflow needs.
- Implementation and QASearch, recheck and booking success testing.
- Go-live supportA monitoring playbook and handover to your support team.
Options
Ways to sell TBO flights, compared
Each approach can work. The difference is how much you build and run yourself.
| Option | Time to launch | Ongoing workload | Usually fits |
|---|---|---|---|
| Direct build on the TBO API | Time to launchMedium to long: you build the UI, pricing, recheck, logs and support tools | Ongoing workloadHigh | Usually fitsLarge teams with in-house developers and operations |
| A GDS connection | Time to launchLong: deeper onboarding and implementation | Ongoing workloadHigh | Usually fitsComplex airline content needs |
| Another aggregator API | Time to launchMedium: a quick start, but post-booking work stays with you | Ongoing workloadMedium | Usually fitsA quick first version |
| PHPTRAVELS with TBOReady-made | Time to launchShorter: the booking flow and management tools already exist | Ongoing workloadLow to medium | Usually fitsOTAs, agencies, tour operators and DMCs |
PHPTRAVELS is a one-time licence with source code under a commercial licence, installed on your own server. You keep your TBO contract and credentials.
Run TBO beside other flight suppliers
One search can merge several flight sources, each with its own markup, so you are never tied to a single supplier.
Also read:AmadeusNDC flights booking systemB2B travel portalAll integrations
Seeru
Amadeus
Duffel
Google Flights
Kayak
Kiwi
Mystifly
PKfare
Sabre
Travelport
FAQ
Questions about TBO flights
What teams usually ask before they connect their TBO account.
Talk to salesConfirm your TBO account has flight API access and get test credentials. Then add them to the flights module, run a small library of real routes and dates through search, recheck, booking and cancellation, and only then polish the customer journey.
Price changes between search and payment, fare rule limits the customer did not see, and timeouts during confirmation. The module rechecks every fare before payment, logs every step under one trace ID and queries the booking status after a timeout instead of booking again.
Yes. One booking engine serves both: customers get a public checkout, and agents get their own pricing, markups and reports in the agent portal.
No. Many teams keep their CRM or accounting tools and connect them to the booking engine through APIs and webhooks, so flight sales are added without changing how the office works.
TBO hotels use a separate connector in the stays module. You can switch on flights, hotels or both with the same TBO account details where your contract allows it.
Yes. Hotels, tours, cars and transfers can be added later while you keep one customer account, one checkout and one reporting layer.
Keep exploring
More from the platform
- Flights APIGDS, NDC and consolidator flight APIs on one platform
- TBO hotel API integrationTBO Holidays hotel rates in your booking engine
- FlightsGDS and NDC ticketing
- Flight booking softwareBuyer's checklist for agencies and OTAs selling flights
- Travel APIsGDS, hotel, tour, car and payment APIs
- B2B travel portalAgent tiers, markup layers, credit limits and settlement