Broker integrations
Distribution is part of operations — not an inbox beside it.
Broker connectivity matters because a booking changes real inventory. The useful question is not simply which channels connect, but how each reservation moves into availability, pricing and desk work.
01 · Channel operation
Receive demand
Bring broker reservations into a defined operational flow instead of treating each channel as a separate process.
02 · Channel operation
Protect availability
Keep sellable capacity aligned with confirmed bookings, direct demand and vehicles that are unavailable.
03 · Channel operation
Control exceptions
Make amendments, missing details and allocation decisions visible to the people who need to act.
Integration methods
SOAP
Contract-based messaging with a fixed schema. Established broker and distribution systems still use it, so operators often meet it in practice.
REST API
Lightweight request-and-response calls, usually JSON. Common in modern channel tools for availability, rates and reservation updates.
Booking received
Dates, location, class and renter details
Availability checked
Capacity viewed against every committed rental
Reservation controlled
Rates, extras and source stay attached
Desk action prepared
Allocation and handover enter the daily plan
Agent portal & iframe embedding
Let partners sell for you without leaving their own page.
Distribution does not stop at brokers. Agencies want somewhere to book, and partner sites want a booking form of their own. Both can be served from one operation.
Agencies book against your live terms.
An agent portal gives travel agencies and partner desks their own sign-in, so a reservation is built against current availability and the rates that agency is entitled to, rather than requested by email and confirmed an hour later.
01 · Live availability
Agencies book from what can actually be sold right now, not a list copied last month.
02 · Contracted rates
Each agency sees the pricing attached to its own account.
03 · Clear attribution
The reservation carries the agency that created it, so volume stays traceable.
04 · Fewer handoffs
Requests, amendments and confirmations stop travelling through email threads.
Typical users
Travel agencies, concierge and corporate desks, and tour operators that need their own booking terms.
Your booking flow, inside somebody else's page.
An iframe embed places the search and reservation form inside a partner website, a destination page or your own microsite. The visitor searches, chooses and reserves without seeing a hand-off.
Embed · your availability
Pick-up
Airport T2
Drop-off
Same
Class
Estate
Typical placements
Partner websites, destination and transfer pages, tour operator microsites, and your own campaign landing pages.
Partner page or agent sign-in
The booking starts where the customer or agency already is.
Your availability answers
Current stock and terms respond to the search.
Created at source
Dates, vehicle class and the originating site stay attached.
One operation receives it
The reservation enters the same desk workflow as every other booking.
Whether an agent portal or an embeddable booking frame is included, and how either is configured or charged, is confirmed on the official Carhire Manager Web website.