Skip to content

You decide who connects, and how hard they can hit you

For bedbanks, wholesalers, DMCs, hotel platforms and channel managers. TravelRevo lets you take on buyers without another integration project each time, with your approval on each one, and your traffic limits enforced.

Access request

Waiting on tests

Corvane Travel

Buyer type
Online travel agency
Markets
Gulf states, Western Europe
Your agreement
Reference CT-2041 on record
Sandbox tests
Must pass on current versions

Traffic cap, search

12 per second

  • Access request Accepted
  • Booking tests Waiting
  • Your go-live approval After tests pass
Illustrative. Companies and data are fictional.

Approve each buyer connection yourself.

3
approvals before go-live, and yours is one
1
traffic cap you set per buyer connection
0
external load tests without your written authorisation

Buyers do this work before they reach your engineers

Who they are
A buyer's organisation is reviewed by a person.
Buyer typeOnline travel agency
That you agreed
Your business admin approves the connection, with a reference to your agreement on record.
Your agreementReference CT-2041 on record
That they work
They pass an agreed test plan in your sandbox or on an agreed test property before reaching production.
Sandbox testsMust pass on current versions

Illustrative. Companies and data are fictional.

See what each buyer costs your API

Every request is attributed to a buyer connection. A buyer searching far more than it books is visible as that buyer, with its peak against the cap you set, and its most common errors.

Your caps are hard limits. A ramp stays under them, and rate-limit responses from your system are a reason to stop ramping. When something errors, your team and the buyer read the same redacted trace.

Corvane Travel, sample hour
OperationYour capPeak usedError rateMost common error
Search12 per second9 per second0.4%Unmapped hotel ID
Quote4 per second2 per second1.1%Rate expired
Book1 per secondUnder 1NoneNone
Cancel1 per secondUnder 1NoneNone
Illustrative. Companies and figures are fictional, and aren't a measure of anything real.

Who decides what

Commercial and technical boundaries are set by you. TravelRevo holds them in place.

Which buyers get access
Who decidesYou, per buyer
What TravelRevo doesHolds the connection closed until you approve it
Commercial terms and rates
Who decidesYou and the buyer
What TravelRevo doesRecords a reference to your agreement, and leaves the terms to you
Credit and settlement
Who decidesYou and the buyer, directly
What TravelRevo doesStays out of the money. TravelRevo isn't the merchant of record
Traffic caps and windows
Who decidesYou
What TravelRevo doesApplies them to each buyer connection
Test policy
Who decidesYour integration engineer
What TravelRevo doesRuns only the approved plan, in your authorised sandbox or on an agreed test property
External load tests
Who decidesYou, in writing
What TravelRevo doesKeeps them off unless authorised, with a cap, a time window and a kill switch
Your native codes and terms
Who decidesYou
What TravelRevo doesKeeps them on every quote and booking, unaltered

Questions you may have

Do you support push as well as pull?

Yes, including channel managers. Connecting through your API and pushing rates and availability both follow the same approvals, mapping review and tests. Tell us how you distribute today.

Can a buyer reach my production system without my approval?

No. Live needs your approval, the buyer's approval, operator approval, a commercial reference on record, current passing tests, an approved mapping snapshot and a traffic policy. Remove any one and the connection doesn't go live.

Who can see my rates and inventory?

Only the buyers you've connected with, within the scope of that connection. Other sellers and unconnected buyers don't see your inventory, pricing or mappings.

What stops a buyer from hammering our API?

Your caps, which apply per buyer connection. A ramp stays inside them, and rate-limit responses from your system are a reason to stop ramping. External load tests are off by default and need your written authorisation.

Do we have to build a new API?

TravelRevo works with existing hotel adapters, so the first question is whether your system already has one. Tell us what you run. If there's no adapter, we'll say so.

How are our API credentials handled?

They're stored in a dedicated secrets vault and referred to by versioned reference. Once saved, they aren't displayed again, and they're kept out of logs, emails and AI prompts.

Do you use our hotel data to help other buyers or sellers?

Your codes and content are only used under the terms agreed for your connections. How mapping reference data can be used and shared is something we agree with you explicitly.

Do you take a margin on bookings?

TravelRevo isn't a merchant of record or a reseller, so we don't resell your rates. Connecting is free for every buyer and seller. Ask us about live trading, and we'll tell you what applies.

What do you need from us to connect?

A named integration contact with some engineering time, and an authorised sandbox, test environment or agreed test property.

Tell us which buyers you want this for

Tell us what you run today and which connections take up your team's time. A person will reply, and it won't commit you to anything.