Kiwi Tequila API Flights Documentation

Kiwi Tequila API flights documentation is what you open when you want Kiwi.com’s search in your app. The gotcha is in the table of contents: search is one family of calls. Booking is another. Most copy-paste tutorials only show the GET.

This page is the split, not a substitute for Kiwi’s partner portal. Ktemia’s own contract stays on the flight search API post. We are not Tequila. Routes here are not live. No invented Kiwi fares.

Key Takeaways

• Kiwi’s Margarita docs: /search for itineraries, /booking to finish. Last updated 2 April 2019.
• Affiliate search examples use fly_from, fly_to, date_from, date_to, and an apikey header.
• Deep links and booking tokens are Kiwi’s book path. They are not a Ktemia PNR, because we do not ticket.

What is the Tequila API?

Kiwi’s public What is Tequila API? page (Margarita monorepo, last updated 2 April 2019) describes Tequila as the platform to build a travel business app with kiwi.com content. You register. You get an API key.

To search, they list /locations and /search (plus Multicity and NOMAD). To finish booking, they say you need the /booking API: check the price is still valid, check the itinerary is still available, save the booking, confirm payment.

That paragraph is the documentation people skip. A search response is not a ticket. A booking token is not a search.

The query kiwi tequila api flights documentation is often a hunt for one curl that “does flights.” Tequila’s own outline is two products under one brand: a Search API and a Booking API. If your README says “Tequila” and only ships /v2/search, you documented half the stack and promised the other half.

Travelpayouts’ Kiwi.com affiliate program API describes the affiliate search host as tequila-api.kiwi.com and a basic GET /v2/search with fly_from, fly_to, dateFrom / dateTo in the example URL (their parameter table uses date_from / date_to as dd/mm/yyyy). Affiliate flows may return a deep_link so the traveller finishes on kiwi.com.

Treat those URLs as historical public descriptions. Hostnames in old posts disagree (tequila-api.kiwi.com vs api.tequila.kiwi.com). Date field names disagree. Get the current base URL, header, and date format from your Tequila solution. We will not pretend we opened your partner dashboard.

What does a Tequila flights search actually send?

Public affiliate docs need origin, destination, and a departure date range. fly_from and fly_to accept airport codes, city IDs, countries, and other Kiwi location IDs. If you omit fly_to, they warn you can get aggregated results you did not mean.

That is still search. It is not Ktemia’s envelope.

Ktemia’s contract is one POST, JSON, origin, destination, depart as 2026-10-12. Worked query: LIS → LHR. If a field is missing, we ask. We do not invent PRG because a Kiwi tutorial used it.

Do not copy Tequila’s GET query string onto POST /v1/flights. Do not copy our ISO date onto a dd/mm/yyyy range without checking Kiwi’s current spec. Mixed date formats are how you search the wrong day and burn quota.

We are not pasting a live Tequila JSON list. Invented prices would look like a key we do not have.

Search vs booking in the same Tequila docs

Call	What it is for	What you must not conclude
Locations	Resolve city / airport IDs	Not a fare
Search / Multicity / NOMAD	Itineraries you can show	Not a paid ticket
Booking	Revalidate, pay, save the order	Not “just another search param”
Affiliate deep_link	Hand the traveller to kiwi.com	You did not issue the ticket

Affiliate and full API integrations both start with search. Only one of them stays on your domain through payment. Kiwi’s Margarita page is explicit: booking is a separate API. If your product is compare-only, stop at search and say so. If your product is an OTA, you need Kiwi’s booking agreement, not a Ktemia POST.

Ktemia terms treat a search as comparison, not a reservation. We do not sell the flight. Hotel search and flights search with AI are compare verticals. Tequila’s booking call is Kiwi’s merchant path. Do not rename our copilot a Tequila booking bot.

How is Tequila different from Skyscanner, Amadeus, and Google Flights?

Skyscanner Live Prices is create-and-poll after Partnerships. Tequila is Kiwi’s key, historically a GET search. Different host, different session model, different commercial gate.

Amadeus self-service shut 17 July 2026. Remaining Amadeus is enterprise / GDS. Tequila is not a GDS login.

There is no official public Google Flights API. QPX Express died 10 April 2018. Tequila is not a Google scrape.

A GDS searches and books through an intermediary that does not hold inventory (Amadeus glossary). Tequila is Kiwi’s platform. The GDS vocabulary is unpacked on GDS vs booking engine vs a search API.

What must you not guess?

Origin, destination, dates. On Tequila, that is fly_from, fly_to, and the date fields Kiwi currently requires. On Ktemia, that is origin, destination, depart.

If the user says “soon,” ask. Do not fill 01/08/2026 because a blog used it. On Free, you get 50 API requests a month. A wrong city is a spent call. Never put apikey or a Ktemia dashboard key in frontend JavaScript.

Agents should load “search flights, ask if unclear,” not “open Tequila and hope.” That wiring is flights MCP. Same three Ktemia fields. Different pipe.

Read the search chapter, then stop if you do not ticket.

Kiwi Tequila API flights documentation is a search chapter and a booking chapter. Copy the first only if your product is compare. Copy both only if you have Kiwi’s booking deal.

Ktemia is compare: product, pricing caps, flight search API for the POST. Where Tequila sits against Amadeus, Skyscanner, Booking and Expedia is laid out in best travel API. The case for comparing at all sits in our price spread study — one seller to the next, a $970 median difference on the same seat. Routes are not live. When they are, this page will not grow a fake Tequila response. It will point at a dated Ktemia example, still without a PNR.