Live demo

Flight API integration

Duffel API integration for travel agencies

Bring Duffel flight content into your PHPTRAVELS booking platform. Duffel supplies the offers and orders available to your account; PHPTRAVELS runs the website, checkout, markup and agency admin around them.

  • Existing Duffel flight module
  • NDC, GDS and low-cost content
  • Agency markup settings
  • Test mode before going live

How it works

Your booking platform, connected to Duffel flights

A Duffel API integration separates two decisions: the booking platform your customers use, and the supplier account that powers its flight results. PHPTRAVELS ships a Duffel module in the flights category with API credential and markup settings, documented in a setup guide on docs.phptravels.com that covers API access and a first search. Start with that connection, then agree the booking and servicing actions your team needs for launch.

  1. Create your Duffel account and confirm your markets and content access
  2. Prepare a Duffel test access token for your trial configuration
  3. Open Modules in the PHPTRAVELS admin, then the Duffel settings, and enter the credentials
  4. Set your markup and validate search, passenger details, payment and order confirmation
  5. Complete Duffel's activation requirements and switch to live credentials
Try the flights demoSee pricing
Environment
Test mode
Endpoint
Duffel API · api.duffel.com
Access token
duffel_test_••••••••
Markup
8% on Duffel fares

Booking flow

From Duffel search to a confirmed order

Use this flow to evaluate your configured connection, including the hand-off from customer checkout to supplier confirmation.

  1. Search

    Send the journey and passengers to Duffel and receive flight offers.

  2. Review

    Retrieve the chosen offer again so the price and availability are current.

  3. Book

    Collect passenger details and payment, then create the order with Duffel.

  4. Confirm

    Check the order and airline reference, then confirm to the customer.

  5. Service

    Changes and cancellations follow airline rules and your agreed scope.

Responsibilities

What each part of the Duffel integration does

A working connection needs a platform, an approved supplier account and an agency operating process. Define all three before choosing a launch date.

  • PHPTRAVELS: your booking platform

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

  • Duffel: your flight connection

    Airline offers and order services through its API. Airlines, content and post-booking actions depend on Duffel, the airline and your account.

  • Your agency: the commercial workflow

    Supplier onboarding, selling prices, customer payments and support, including who handles pending bookings and traveller requests.

Flight suppliers you can connect:

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

Back office

Run Duffel flight sales from your admin

Settings, pricing and operating rules for Duffel bookings, in the same dashboard as the rest of your travel business.

  • Module settings

    Duffel API credentials entered under Modules, with test and live configurations kept separate.

  • Markup and selling price

    Save your agency markup and review the final price against supplier charges, currency and payment costs.

  • B2C and B2B channels

    Decide which channels Duffel serves first, then validate agent access, pricing and checkout.

  • Unresolved orders

    A clear process for staff to spot an unconfirmed supplier order, so a payment is never treated as a ticketed flight.

  • Separate cost lines

    Licence, hosting, payment processing, custom work and Duffel charges planned as separate budget items.

  • Extra workflows

    Seats, paid baggage or servicing beyond the module can be scoped as integration customization.

Compare

Building on the Duffel API yourself vs PHPTRAVELS

Duffel 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 DuffelPHPTRAVELS
Customer websiteCustom build on DuffelSearch, results and checkout designed and coded from scratchPHPTRAVELSBranded flight search, results and checkout already in place
Duffel connectionCustom build on DuffelOffers and orders calls written and tested by your developersPHPTRAVELSExisting Duffel module with credential and markup settings
Admin and markupCustom build on DuffelBooking admin and pricing rules still to buildPHPTRAVELSBooking administration and module markup in one dashboard
Agent channelCustom build on DuffelA B2B portal is a separate projectPHPTRAVELSB2B and B2C tools in the platform, depending on your package
Other productsCustom build on DuffelEach new supplier or product is another buildPHPTRAVELSHotels, tours, cars and other supplier modules in the same installation

Use cases

Who connects Duffel to PHPTRAVELS

  • New online travel agencies

    Launch a branded flight booking site with Duffel content from day one, then add more products.

  • Agencies without IATA accreditation

    Eligible businesses can use Duffel Managed Content under Duffel's accreditation and ticketing authority, subject to Duffel's approval.

  • B2B agent networks

    Offer Duffel flights to partner agents with their own access and pricing rules, agreed for your package.

Why PHPTRAVELS

Your Duffel account, your platform, your code

  • Source code included

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

  • Your Duffel credentials

    You hold the Duffel account and access tokens, stored in your own installation.

  • Documented setup

    A Duffel setup guide on docs.phptravels.com covering API access and a first search.

  • B2C and B2B

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

FAQ

Duffel API integration questions

What agencies ask when evaluating the module, supplier access and launch requirements.

Talk to sales

It connects the Duffel flight supplier module with your PHPTRAVELS booking platform. Your Duffel account provides access to eligible flight content, while PHPTRAVELS provides the customer-facing website and agency administration.

Yes. PHPTRAVELS lists a Duffel module in the flights category and publishes a setup guide covering API access and a first search. Confirm compatibility with your installed version and the booking operations you need before launch.

Create a Duffel account, obtain the API credentials, then enter them in the Duffel module settings in your PHPTRAVELS admin. Configure the markup and validate the integration in test mode before moving to production.

Duffel offers Managed Content using its own accreditation and ticketing authority, subject to account activation and available content. Confirm eligibility with Duffel. Connecting PHPTRAVELS does not make your business IATA-accredited.

Do not assume full feature parity. Seats, paid baggage, changes, cancellations and other servicing actions need to be checked against your PHPTRAVELS module version, airline support and the agreed integration scope.

No. Duffel test mode uses sandbox content and test credentials. It is useful for validating behaviour, but test results are not production availability or a commercial fare quote.

Keep exploring

More from the platform