Channels · OTA & broker distribution
Put your fleet in front of travellers already booking on Trip.com, CarTrawler and the rest
Brokers and online travel agents send you customers who were never going to find your own site. Glovebox connects your fleet to them on a modern, keyed API built for exactly this: real-time availability and rates, the same foundation a broker's own integration team would expect to work against.
Settings → Integrations → Channels, in every workspace. Linking an OTA costs nothing and never collects a password, API key or other login secret.
Why it matters
More demand, without a new storefront to run
A broker or OTA puts your cars in front of someone who is already deciding where to book, on a platform they already trust. You do not have to win that traveller to your own site first; the booking arrives already decided, and your fleet, your rates and your availability stay exactly as current as they are in Glovebox.
The fastest way onto a channel is almost always the relationship you already have. An operator who already holds an approved supplier account with a broker gives that broker's own certification a head start, because the trust is already established on their side.
Already selling through an OTA?
Link us up to your existing account, and we build the connection
If you already hold an approved supplier account with a broker, that is most of the work done. Give us the broker and your supplier or partner ID, and our integration work starts from the relationship you have already built, rather than a certification conversation from a standing start.
Not yet approved with the one you want? We prepare a ready-to-send introduction addressed to your own contact there, with Glovebox copied in, so it reads as what it is: a referral from an operator already in motion. Either way, you get a reply from us with exactly what happens next.
Settings → Integrations → Channels. Takes a minute; we take it from there.
The engineering behind it
A modern, keyed API, built for distribution
Every channel connection runs on the same foundation: a versioned, keyed REST API serving your real-time availability and rates, straight from the fleet and pricing you already manage in Glovebox. There is no spreadsheet to upload and no separate system to keep in sync; a broker reads exactly what your own booking widget reads, at the moment they ask for it.
It is the same API a broker's own integration team can be pointed at directly, documented and ready for a developer to work against.
Developer documentation →{
"vehicle_group": "suv-midsize",
"available": true,
"rate": { "daily": 129.00, "currency": "NZD" }
}
Keyed per workspace. Read access to availability and rates, nothing else.
How we track every connection
You will always know exactly where a channel stands
Every broker on your Channels page carries one of three words: Live, In certification, or Available on request. We built it this way on purpose: a status here is a fact you can act on, not a sales line.
Live is the only one that claims a working connection, and it is the only one we have to prove: Glovebox will not let a channel be marked Live without a record of a real booking that went through it end to end. That is rigour working in your favour, not a disclaimer.
Trip.com, EconomyBookings, CarFlexi, Zuzuche, QEEQ, DiscoverCars, CarTrawler
Read live from Glovebox. It moves the moment a status does.
The standard we hold ourselves to
We will never tell you a channel is live until a real booking has gone through it, start to finish.
An operator has walked away from a platform before over an overstated integration claim. Glovebox would rather a status read "In certification" for longer than call something "Live" a day early. The build queue moves on what operators ask for, and the channels you request are the ones we work on first.
Questions
Channels, answered
Can I list my cars on Trip.com, CarTrawler or another broker today?
Every broker we build goes through the same process: we start the integration, work through that broker's own certification, and prove it with a real booking before we ever call it "Live" on your Channels page. Tell us which one you want and we add it to the build; tell us you are already an approved supplier with them and we go straight to the technical work.
What does "In certification" mean, and when will it finish?
It means the integration is built and we are working through that broker's own technical approval. We will not put a date on it, because finishing it is the broker's call, not ours. We would rather say that plainly than guess.
I already sell through a broker directly. Does that help?
Yes, and it is the fastest route by a wide margin. If a broker has already approved you as a supplier, with your own account and a supplier or partner ID, we build from the account you already hold instead of starting a certification conversation from nothing. Operators who come to us already connected to a broker are routinely our quickest live channels.
Will Glovebox ever ask for my broker password or API key?
No. There is nowhere in Glovebox to enter one, and linking an OTA never collects a password, API key or any other login secret. If anything ever appears to ask you for one, stop and contact us.
Does Glovebox contact the broker on my behalf?
If you are not yet approved with a broker, we prepare the introduction and you send it from your own address, with Glovebox copied in. It reads as what it is: a referral from an operator already in motion, not a cold pitch from a platform the broker has never heard of. We do not email brokers ourselves.
What does it cost?
Nothing to link an OTA or broker, and nothing to be on the list. There is no charge today for anything shown here.
I want to build my own connection instead. Is there an API?
Yes. The Channel API gives a developer keyed, real-time access to your availability and rates, the same data a broker integration runs on. It is a separate, developer-facing surface from this page; see the developer documentation if that is the route you want.