OTAs · Metasearch · Agencies
Inventory that isn't already in your results
Flight results look the same across every channel because they come from the same GDS. Charter blocks don't. We connect 20+ tour operators into one API and adapt the integration to your format in weeks.
What's in the feed
None of this overlaps with your GDS suppliers. These are operator blocks sold seat-only, flagged as charter in every result, on routes and dates your existing content doesn't carry.
- 476 city pairs, 798 routes open for sale today
- 25,685 flights depart more than 90 days out. Core operators publish about six months ahead, some sources up to 15.
- Departure markets: Kazakhstan, Uzbekistan, Azerbaijan, Georgia, Armenia, Moldova, Romania
- Destinations: Turkiye, Egypt, UAE, Vietnam, Montenegro and other charter leisure markets
A charter block is priced to fill a specific aircraft on a specific rotation, not to fit a fare ladder. On the return leg that usually puts the seat well under the scheduled fare on the same city pair. It's the strongest reason a traveller picks a charter result over the one above it, and the reason these routes convert rather than just add rows to your page.
Top corridors by volume
| Corridor | Flights per week | Operators |
|---|---|---|
| RMO–AYTChisinau–Antalya | 38 | 5 |
| RMO–SSHChisinau–Sharm el-Sheikh | 35 | 4 |
| ALA–AYTAlmaty–Antalya | 11 | 7 |
| ALA–CXRAlmaty–Nha Trang | 8 | 7 |
| ALA–SSHAlmaty–Sharm el-Sheikh | 7 | 4 |
How to connect
Pull search API
You query us, we answer live. One endpoint for search, one for the route directory, one for order reconciliation. We run without rate limits on partner keys and hand you a test key before any contract is signed.
Hourly price feed
We push the full inventory to you: prices, availability, baggage, end-of-sale dates. Refreshed every hour, delivered over SFTP. Running in production for a European distribution partner today.
Your contract
A different schema, a different transport, push instead of pull, a webhook when availability changes. Send the spec and we build against it. Every integration we run today started as someone else's requirement.
How onboarding runs
- 1.
Call — We look at your traffic and agree which part of the inventory fits your channel.
- 2.
Test key — Issued within [N] working days, no contract required.
- 3.
Price check — You compare our quotes against your own accuracy threshold before going live.
- 4.
Live — Named technical contact and an agreed response time from day one.
The price doesn't move
Metasearch partners measure price accuracy on redirect themselves. We're built so that the number comes out clean, and we'd rather you verify it than take our word for it.
Every quote carries an identifier derived from its own final price, the passenger composition and the partner. The price cannot change under that identifier, because the identifier is computed from it. When the operator price, the exchange rate or the fare rules move, the result is a new identifier, and the quote you were already showing stays bookable at the price you showed.
A quote holds for 60 minutes from the moment we return it, and never reaches the traveller with less than 45 minutes left. It extends silently as expiry approaches. If the price does move, the traveller sees the previous and the new amount side by side and the payment button stays locked until they confirm.
Prices are returned in USD, EUR and GEL on every option. Rates refresh hourly, and a refresh never touches a quote already issued.
Operations
Payment
GTAvia LLC is the merchant of record. Card payment is taken as a pre-authorisation: funds are held and captured only once the operator confirms the seat. If the operator declines, the hold is reversed, and the traveller is never charged for a seat that doesn't exist.
Order confirmation
Charter blocks are confirmed by the operator, not instantly by the system. Median time from booking to confirmation is about an hour. Confirmation rate is 97% on channels where the seat is confirmed automatically and 75% on redirect traffic, where a larger share of bookings falls inside 24 hours of departure.
Disruption handling
Schedule changes and cancellations reach the traveller by email in English and Russian, with the operator's reason stated. We send it as soon as the operator notifies us. On a cancellation the hold is reversed automatically and any captured amount is refunded through the same gateway.
Refunds and changes
Charter fares are refundable under the operating tour operator's block conditions, which differ by programme. Changes go through support rather than self-service, because the seat has to be released and rebooked on the operator's side. Full and partial refunds are processed through our payment gateway.
Technical monitoring runs 24/7, with automated alerting on supplier gateway degradation, marker loss and payment anomalies.
We build to your spec
We already run seven kinds of tour operator platform to get inventory in, so fitting an unfamiliar system is routine work for us. Getting it out to you works the same way: you describe the shape you need, we build it and test it with you.
Most requests take one to four weeks, and several usually ship together rather than one after another. Some are a same-day config change.
Things partners have asked us for:
- Additional settlement currency — KZT, AZN, UZS, TRY, RON, MDL, PLN
- A custom feed schema, or a transport other than SFTP
- Push notification when availability changes, instead of pull
- A segmented feed: routes, operators or departure windows filtered to your criteria
- Channel-specific pricing rules
- An additional deeplink locale
- A dedicated escalation channel with an agreed response time
Not on the list? Ask. The answer is usually a delivery date.
Talk to us
- We reply from a person, not an autoresponder
- A short call to work out which part of the inventory fits you
- Reply within one working day