TBO Integration: What It Covers Today
TBO flights and TBO hotels are two different APIs here, at two different stages. This page says plainly which is which.
TBO uses different technology for each product. The hotel API is SOAP with credentials on every call, and the flight API is REST with a token. We built them as separate connections so that a change to one cannot affect the other. An agency can run TBO flights without TBO hotels.
TBO here is partly built and partly in testing, so please read the status table below before you plan a launch around it.
Key features
Flights in the normal search
When switched on, TBO offers join your flight results beside Duffel and go through the same detail page and checkout.
Payment, then ticket
The fare is rechecked, the customer pays through your gateway, and the server then books the fare with TBO and sends the ticket email.
Wallet and cancellation tools
Admins can read the TBO wallet balance, see cancellation charges and cancel a booking from the back office.
Hotels built up to prebook
Search, room lists, cancellation policy and prebook work with your credentials. Booking and cancelling are limited to admin use for testing.
Off until you ask
TBO is switched off by default on every site, and the hotel module has its own separate switch.
Why it is on request
TBO issues API access separately from its B2B portal, so a working portal login usually fails against the API. Access also depends on which modules TBO opens for your account, and static hotel content comes from a separate data feed. We can only confirm a flow end to end with your credentials, so we test first and switch TBO on after that test passes.
If you depend on TBO for your launch, tell us on your application. We will tell you where your account stands before you pay for a plan that lists it.
What hotels still need
The missing pieces are the customer checkout and stored hotel content. The hotel connection already enforces what TBO asks of a seller: rooms have to come from the room list, and it refuses to continue when TBO returns no cancellation policy. It also keeps to TBO's stated limits of 4 rooms per booking, with 4 adults and 2 children per room.
Until the checkout is connected, sell hotels through a supplier that is already in the public search. RateHawk, Hotelbeds and WebBeds are the usual choices.
What this integration does not do
TBO hotels do not appear in your public search today, and customers cannot book them. The TBO visa service is not offered. TBO flights are the only flight route that depends on TBO, so running Duffel or PKFARE needs no TBO account at all.
TBO flights and hotels side by side
| TBO flights | TBO hotels | |
|---|---|---|
| Status | On request, after testing your credentials | On request, not in public search |
| Customer can search | Yes, once switched on | No |
| Customer can book | Yes, once switched on | No |
| Admin tools | Wallet, cancellation charges, cancel | Book, booking detail, cancel |
| Credentials | Your TBO API username, password and agency ID | Your TBO hotel API username and password |
Frequently Asked Questions
Can I use my TBO portal login?
Usually not. TBO treats API access as separate from the portal, so ask its API support team to issue credentials and enable the modules you need.
Can my customers book TBO hotels today?
No. Hotel booking is limited to admin use while the public checkout is built. If this decides your choice, ask us before you sign up.
Is TBO part of a monthly plan?
TBO flights are listed on the On Demand plan. Everything else about TBO is agreed per site, after we have tested your credentials.
Is Travora Hub affiliated with TBO?
No. Travora Hub is independent, and your TBO account and contract stay between you and TBO.
Guides to read next
Explore more: Flight Booking Software · Duffel Integration · PKFARE Integration · Hotel Booking Engine · All Integrations