Live demo

Flight API integration

Kiwi API integration for travel agencies

Bring Kiwi.com flight content into your PHPTRAVELS booking site through the Tequila API. Kiwi.com returns the itineraries and takes the booking; PHPTRAVELS runs the search, checkout, markup and agency admin around them.

  • Kiwi module in the flights category
  • One-way, return and multi-city
  • Markup on every Kiwi.com fare
  • Setup guide on docs.phptravels.com

How it works

Kiwi.com flights inside your own booking platform

A Kiwi API integration links two things: the booking website your customers use and the Kiwi.com Tequila account that supplies its flight results. PHPTRAVELS ships a Kiwi module in the flights category. You enter your AffilID and API key in the admin, the module checks them against Tequila, and searches start returning Kiwi.com itineraries with your markup applied. Tequila access is granted by Kiwi.com, so confirm your account before planning a launch.

  1. Request Tequila API access from Kiwi.com and receive your AffilID and API key
  2. Open Modules in the PHPTRAVELS admin and enter both credentials in the Kiwi settings
  3. Save to run the credential check, a live airport lookup against the Tequila API
  4. Set your markup and review fares for adults, children and infants
  5. Run a small number of real bookings before opening Kiwi.com fares to all customers
Try the flights demoSee pricing
Environment
Production only
AffilID
youragency_affil
Endpoint
Tequila API v2 · api.tequila.kiwi.com
API key
••••••••••••••••
Markup
6% on Kiwi.com fares

Booking flow

From a Kiwi.com search to a confirmed booking

The path one Kiwi.com fare takes through your site, including what happens after the customer pays.

  1. Search

    The customer's journey, passengers and cabin go to Kiwi.com and itineraries come back.

  2. Price

    Your markup is applied and fares show in the customer's chosen currency.

  3. Checkout

    Name, surname, title, nationality, email and phone are collected for each traveller.

  4. Book

    The booking token and passenger list are sent to Kiwi.com to create the booking.

  5. After booking

    Cancellations and refunds are requested through Kiwi.com support, not through the API.

Responsibilities

Who does what in a Kiwi API integration

A working Kiwi.com connection needs a booking platform, an approved Tequila account and an agency process for after-sales.

  • PHPTRAVELS: your booking platform

    The website, Kiwi module settings, markup, checkout and booking administration. Your package sets the wider B2C and B2B tools.

  • Kiwi.com: your flight content

    Itineraries, prices and booking through the Tequila API. Access, routes and post-booking rules are set by Kiwi.com and the airlines.

  • Your agency: the commercial workflow

    Selling prices, customer payments and support, including who contacts Kiwi.com when a traveller asks to cancel or change.

Flight suppliers you can connect:

  • Seeru
  • Amadeus
  • Duffel
  • Google Flights
  • Kayak
  • Kiwi
  • Mystifly
  • PKfare
  • Sabre
  • TBO Holidays
  • Travelport
See every integration

Back office

Run Kiwi.com flight sales from your admin

Credentials, pricing and after-sales rules for Kiwi.com bookings, in the same dashboard as the rest of your travel business.

  • Module settings

    AffilID and API key saved under Modules, with an instant check that tells you if the key is missing, invalid or rate limited.

  • Markup and supplier cost

    Each booking keeps the marked-up selling price next to the Kiwi.com price, so margin is visible per reservation.

  • Currency

    Searches request prices in the customer's currency, and the same currency is stored with the booking data.

  • Cancellation requests

    Kiwi.com does not cancel through the API, so the admin flags these bookings for your team to raise with Kiwi.com support.

  • B2C and B2B channels

    Decide whether Kiwi.com fares serve your public site, your agents or both, then validate pricing for each.

  • Extra workflows

    Extra bags, seat selection or other steps beyond the module can be scoped as integration customization.

Compare

Building on the Kiwi.com API yourself vs PHPTRAVELS

Kiwi.com gives you the flight API; you still need a booking product around it. This is typically what a custom build involves next to PHPTRAVELS.

AreaCustom build on TequilaPHPTRAVELS
Customer websiteCustom build on TequilaSearch, results and checkout designed and coded from scratchPHPTRAVELSBranded flight search, results and checkout already in place
Kiwi.com connectionCustom build on TequilaSearch, multi-city and booking calls written and tested in-housePHPTRAVELSExisting Kiwi module with credential check and markup
Admin and marginCustom build on TequilaBooking admin and pricing rules still to buildPHPTRAVELSBookings, supplier cost and selling price in one dashboard
Agent channelCustom build on TequilaA B2B portal is a separate projectPHPTRAVELSB2B and B2C tools in the platform, depending on your package
Other suppliersCustom build on TequilaEach new airline source or product is another buildPHPTRAVELSOther flight, hotel, tour and car modules in the same installation

Use cases

Who connects Kiwi.com to PHPTRAVELS

  • New online travel agencies

    Launch a flight booking site with Kiwi.com itineraries as a first content source, then add more suppliers.

  • Budget and leisure agencies

    Sell short-haul and leisure routes with clear bag limits on every fare, alongside your own packages.

  • B2B agent networks

    Offer Kiwi.com fares to partner agents with their own access and pricing rules, agreed for your package.

Why PHPTRAVELS

Your Kiwi.com account, your platform, your code

  • Source code included

    Self-hosted under a commercial licence, so your developers can extend the Kiwi.com flow.

  • Your Tequila credentials

    You hold the AffilID and API key, stored in your own installation.

  • Documented setup

    A Kiwi module guide on docs.phptravels.com in the flights section.

  • B2C and B2B

    One installation for your public website and your agent portal, in 24 languages.

FAQ

Kiwi API integration questions

What agencies ask when evaluating the Kiwi module, Tequila access and after-sales.

Talk to sales

It connects the Kiwi.com Tequila API to your PHPTRAVELS booking platform through the Kiwi module in the flights category. Kiwi.com supplies itineraries and takes bookings; PHPTRAVELS provides the customer website, markup and agency administration.

Tequila access is granted by Kiwi.com. Once approved, you receive an AffilID and an API key, which you enter in the Kiwi module settings. Check eligibility and commercial terms directly with Kiwi.com.

The module works against the Kiwi.com production API only and rejects placeholder keys. Validate with a small number of real bookings, or limit Kiwi.com fares to staff accounts, before opening them to customers.

Yes. One-way and return trips use a single search, and multi-city requests search each leg separately with Kiwi.com and combine the results.

No. Kiwi.com does not offer cancellation or refunds through the API used by the module. Your team requests them through Kiwi.com support, and eligibility follows Kiwi.com and airline rules.

Do not assume full parity. Extra bags, seat selection and other services need checking against your PHPTRAVELS version and your Kiwi.com account, and can be added as customization.

Keep exploring

More from the platform