Kiwi API
Kiwi.com's Tequila B2B platform is a documented REST API with instant self-serve keys for flight search. Booking and live-pricing endpoints require a commercial agreement and negotiated production keys. Auth is a static apikey header, and first-party SDKs are unmaintained.
Frequently asked questions
Kiwi scores D+ on the API Report Card. Kiwi.com's Tequila B2B platform is a documented REST API with instant self-serve keys for flight search. Booking and live-pricing endpoints require a commercial agreement and negotiated production keys. Auth is a static apikey header, and first-party SDKs are unmaintained.
Without a usable official API, teams fall back on manual exports, file drops, or one-off vendor integrations. The other option is an unofficial API layer like Supergood that automates the authenticated web app directly.
Kiwi.com s.r.o. is a Brno, Czech Republic-headquartered online travel agency and flight booking platform founded in 2012 by Oliver Dlouhy and Jozef Kahan (originally launched as Skypicker and rebranded to Kiwi.com in 2016).
Vertical: Travel & Expense (more specifically: online travel agency / flight booking / virtual interlining / B2B travel API infrastructure). Consumer flight search and booking on web (kiwi.com plus localized country sites) and mobile (iOS, Android). 'Anywhere' inspirational search (search a date range without a fixed destination).
Mid as a global consumer OTA; mid-low as a B2B flight API. Kiwi.com is consistently ranked among the top-10 global flight OTAs by traffic and bookings, with a particularly strong footprint across CEE, Western Europe, LATAM and SE Asia.
Flight inventory metadata: routes, fares, fare classes, baggage rules, layover details, carrier codes (hundreds of low-cost and legacy carriers). Virtual-interlining itinerary graph: algorithmic combinations of non-interlined segments across separate tickets.
Founded 2012 (14 years old as of 2026) as Skypicker, rebranded to Kiwi.com in 2016 and majority-acquired by General Atlantic in March 2019.
Grades measure one thing: can a customer's engineering team get their own data out programmatically? We check six things (whether a real API exists, how access is gated, data coverage, auth quality, docs and developer experience, and stability) and roll them into a letter grade. Grades get re-verified, and they only move on evidence.