Suppliers
Travel API integration
Start on Rezofy's consolidated content and switch to your own credentials whenever your contracts come through. Most agencies run both and let the rule engine decide which source to show for a given route or agent tier.
Adding suppliers
3–7
working days to add a new API.
Signed a new consolidator? Got direct rates from a bedbank? Send us the credentials and documentation, and the connection is selling inside a week — search, book, cancel and refund, mapped into the same screens your team already uses.
You send credentials
Test credentials, API documentation and a contact at the supplier. That is the whole handover.
We map the calls
Search, availability, price check, book, ticket, cancel and refund mapped to the platform's own model.
Certification
Test bookings against the supplier's environment, error handling, edge cases and any certification they require.
Live
You run UAT, we switch to production credentials, and the supplier appears in your markup rules.
The window assumes the supplier provides working test credentials and documentation on day zero. Suppliers with mandatory certification cycles or slow sandbox provisioning can take longer — we tell you which on the call, before you commit.
Pre-integrated
The connections are already built.#
GDS
Amadeus, Travelport and Sabre for full-service carriers and international content.
LCC & NDC
Direct low-cost carrier connections and NDC offers with ancillaries and branded fares.
Consolidator fares
Your private and net fares loaded as a supplier, priced by your own rules.
Hotels
Global bedbanks, direct contracts and your own static inventory, with content mapping.
Cars & transfers
Airport transfers, self-drive and chauffeur inventory with meet-and-greet options.
Buses & rail
Domestic bus operators and rail booking for multi-modal itineraries.
Activities & packages
Sightseeing, attraction tickets and dynamic packaging that bundles air with land.
Payments
Cards, UPI, net banking, EMI, wallets and international gateways with auto-reconciliation.
Insurance & visa
Travel insurance and visa assistance sold as add-ons at checkout.
Messaging
WhatsApp Business API, SMS, transactional email and push, on templates you control.
Your systems
CRM, Tally and other accounting, ERP and mid-office through open APIs and webhooks.
Your next supplier
Not on the list? Send credentials and it is live in 3–7 working days.
Once it is live
A connection is not finished when it works once.#
We keep it running
- Supplier version changes tracked and applied before they break your bookings
- Response-time and error-rate monitoring per supplier
- Automatic failover to an alternative source when one goes down
- Look-to-book ratio watched, so you do not breach supplier limits
- Credential rotation handled without downtime
You stay in control
- Turn a supplier on or off per channel, market or agent tier
- Set which source wins when two return the same flight
- Apply different markups per supplier on the same route
- Cap or throttle a supplier that charges per search
- See margin per supplier before you renew a contract
Questions about this#
How quickly can you connect a supplier I have just signed?
Three to seven working days from the moment you hand over test credentials and documentation. That covers search, booking, cancellation and refund, plus certification if the supplier requires it. Suppliers with long sandbox provisioning or mandatory certification cycles take longer, and we tell you which those are before you commit.
What exactly do you need from me on day zero?
Test credentials, the API documentation, and the name of someone at the supplier who can answer a question. That is the whole handover. If the supplier requires a certification call, we attend it.
Do I need my own GDS contract to start?
No. Start on Rezofy's consolidated content and switch to your own credentials whenever your contracts come through. Many agencies run both at once and let the rule engine decide which source to show for a given route or agent tier.
Is there a limit on how many suppliers I can connect?
No technical limit. The practical limit is your own supplier strategy — every extra source adds search latency and, on some suppliers, a cost per search. The platform reports look-to-book and margin per supplier so you can prune the ones not earning their place.
What happens if a supplier's API goes down mid-booking?
Searches fail over to your remaining sources automatically, so the customer still sees results. A booking already in progress is held and flagged in the booking desk queue with the supplier's error, rather than silently failing.
Keep reading
Related#
Start selling next week.
Take the trial on your own routes and fares, on whichever model suits you. Nothing to install, nothing to sign.