Mystifly API integration
Mystifly API integration: global airline content for your OTA
Mystifly is a Singapore-headquartered airfare consolidator, with offices in India, that aggregates content from hundreds of airlines, GDS, LCC and NDC sources included, into a single B2B API. For an OTA or agency that needs anywhere-to-anywhere international fares without running its own GDS contract, we integrate that API into your booking website, portal or metasearch product as an independent development partner.
Request a quote for Mystifly API integration
What Mystifly is
Mystifly is a global B2B airfare consolidator: it holds ticketing capability and airline content across markets, and distributes both to travel businesses through an API and an agent platform. Many agencies know it by the product names MyFareBox, its booking portal, and OnePoint, its long-standing API; the company currently markets its stack as a Smart Selling Platform that normalises GDS, low-cost carrier and NDC content into one interface. Whatever the label on the box, the commercial substance is the same: one agreement, one integration, and international fares that can originate far outside your home market.
That origin flexibility is the headline. A typical Indian consolidator prices strongest for journeys touching India; a global consolidator is built for a customer in one country booking a flight between two others, which is precisely the traffic pattern of an international OTA. The engineering pattern behind any such connection is described on our flight API integration page; below is what is specific to Mystifly.
Who a Mystifly integration suits
- OTAs selling international routes that need broad airline coverage without the deposits, segment commitments and certification overhead of their own GDS contract; see how that compares on our GDS integration page
- Indian agencies with outbound and diaspora traffic, where itineraries often start in the US, UK or Gulf rather than in India
- Metasearch and aggregator products that want a bookable fare source beside redirect partners; a natural fit with a meta flight website
- Travel tech platforms and corporate tools that resell flights inside a larger product and need one API rather than many airline deals
It is usually the wrong first choice for a purely domestic Indian booking site, where a local consolidator such as TBO or TripJack tends to fit the fare mix better. Plenty of portals run both: local content from an Indian consolidator, global content from Mystifly, one search box in front.
What access requires
You contract with Mystifly directly: their team qualifies your business, agrees commercial terms and issues API credentials, normally test first and production after your booking flow passes their checks. We do not resell Mystifly access and cannot open an account for you; what we do is prepare the integration questions, build against the sandbox while onboarding runs, and manage certification so the supplier-side process does not stall the launch. [TO CONFIRM: Mystifly's current onboarding requirements and which API version they issue to new customers]
Flows we integrate
Multi-origin search
One-way, return and multi-city searches with cabin, fare-brand and baggage detail, normalised so NDC, LCC and GDS-sourced results render identically in your UI.
Fare confirmation before payment
Re-pricing at selection time so the customer pays the fare that actually exists, the single biggest protector of margin in volatile international pricing.
Booking and ticketing
Passenger and document capture built for international itineraries, ticket issuance through Mystifly, and PNR plus ticket data stored on your side.
Voids, refunds and reissues
Post-booking servicing raised through the API where supported and routed to a service queue where it is not, with status visible to your team throughout.
Pricing and currency rules
Markups by region, carrier or point of sale, plus multi-currency display, so one integration can serve storefronts in several countries.
Caching and monitoring
Search caching tuned to fare volatility, full request logging, and alerting on error rates, because an international fare source is only as good as its uptime story.
These flows plug into whatever front end you run: a custom OTA build on our flight booking engine, an existing website, or a B2B portal where sub-agents book global fares against wallets you control.
Settlement, in general terms
Consolidator economics apply: you buy at Mystifly's net fare under whatever payment arrangement your agreement sets, typically a prepaid balance or a credit facility, and you sell at your marked-up retail price through your own payment gateway. Because Mystifly is the ticketing entity, you avoid the BSP participation and airline-by-airline settlement that direct issuance would demand. Specific deposit levels, credit terms, currencies of settlement and refund timelines are commercial matters between you and Mystifly, and we design your pricing and reconciliation logic around whatever those terms turn out to be. [TO CONFIRM: your agreed settlement terms before reconciliation reports are specified]
Process and timeline factors
Scope and account review
Your markets, route mix, product type and the state of your Mystifly onboarding. Written scope and fixed quote follow.
Sandbox build
Search, checkout, ticketing and servicing flows implemented against test credentials, with normalisation and caching in place.
Certification and controlled launch
Supplier checks passed, production keys live, monitored real bookings before full traffic.
Operate and extend
Monitoring and API-change support, and later phases such as a second content source or new points of sale.
Three things move the schedule most: how quickly your Mystifly agreement and credentials land, how much post-booking servicing you want automated in phase one, and whether multi-currency storefronts launch on day one or later. Each appears as an explicit line in the scope, with supplier dependencies separated from build time. As a rule of thumb, adding Mystifly search and ticketing to an existing booking engine is a smaller project than standing up a new international OTA around it, and automating refunds and reissues properly adds more effort than most teams expect, so we scope servicing depth deliberately rather than by default.
Trademark and independence note
Mystifly, MyFareBox and related product names are trademarks of their respective owner. Globitude Travels & Tech is an independent software integrator. We are not affiliated with, endorsed by or partnered with Mystifly, and we do not resell its content or represent its commercial terms. Platform details above are drawn from public information at the time of writing; confirm current products, API versions and terms with Mystifly directly.
Frequently asked questions
What is the difference between Mystifly and a GDS?
A GDS gives you raw distribution infrastructure and requires your own ticketing arrangements, typically IATA accreditation or a host agency. Mystifly is a consolidator that sits above those layers: it aggregates airline content from multiple sources and issues the tickets itself, so you integrate one API and settle one account. The trade-off is commercial terms versus control; our GDS integration page covers when going direct makes sense.
Is Mystifly relevant for an Indian travel agency?
Yes, mainly for international and multi-origin business: outbound holidays, diaspora traffic booking US-UK-Gulf itineraries, and OTAs serving customers outside India. For domestic Indian routes, local consolidators usually price better, and many of our builds use both side by side.
What are MyFareBox and OnePoint?
Product names Mystifly has used for its agent booking portal and its API respectively; the company now presents its offering as a Smart Selling Platform. If you hold older documentation, the concepts map across, but confirm with Mystifly which API version new customers receive before the project is scoped.
Do you provide Mystifly accounts or special fares?
No. Your commercial agreement, net fares and settlement terms come from Mystifly directly, and we have no influence over them. We are paid for building and supporting the integration, which keeps our advice about suppliers neutral.
Can Mystifly power a metasearch site rather than an OTA?
Yes. A metasearch product can use it as a bookable source, showing Mystifly-derived fares beside redirect partners and completing purchases on your own checkout. That hybrid model is common in the meta flight website builds we do, though your agreement with Mystifly must cover the usage pattern.
Related pages
Add global airline content to your booking product
Describe your markets, your route mix and where your Mystifly conversation stands. A written scope and fixed quote follow within two business days.