Live demo

Flight API integration

PKFARE API integration for agencies and OTAs

Sell PKFARE flight content on your own booking site and agent portal. PKFARE supplies the fares and creates the order; PHPTRAVELS runs the search, checkout, markup, payment, PNR records and after-sales in one admin.

  • One-way, return and multi-city
  • Refund rules and bags on every fare
  • Order and PNR after payment
  • Setup guide on docs.phptravels.com

How it works

PKFARE flights inside your own booking engine

A PKFARE API integration connects the booking website your customers and agents use to the PKFARE account that supplies its flight results. PHPTRAVELS ships a PKFARE module in the flights category: you enter your partner ID and API key, every request is signed with them, and searches return PKFARE fares with your markup and currency applied. When payment is confirmed, the booking is sent to PKFARE and the order number and PNR are saved on the reservation. Access and commercial terms come from PKFARE, so confirm your account before you plan a launch.

  1. Agree access and scope with PKFARE and receive your partner ID and API key
  2. Open Modules in the PHPTRAVELS admin and enter both in the PKFARE settings
  3. Set markup and currency, then review adult, child and infant prices
  4. Run search, payment, PNR and cancellation tests with a few real bookings
  5. Open PKFARE fares to your B2C site, your agents or both
Try the flights demoSee pricing
Environment
Production
Partner ID
youragency_partner
Endpoint
api.pkfare.com · shopping and booking
API key
••••••••••••••••
Markup
B2C 7% · Agents 4%

Booking flow

From a PKFARE search to an order with a PNR

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

  1. Search

    The journey, passengers and cabin go to PKFARE and fares come back.

  2. Price

    Your markup and currency are applied per passenger type.

  3. Checkout

    Traveller names, passport details and contact information are collected.

  4. Pay

    The customer pays through your gateway or the agent pays from the wallet.

  5. Book

    After payment the booking goes to PKFARE, and the order number and PNR are saved.

  6. Cancel

    Cancellation is sent to PKFARE by order number from the admin, subject to PKFARE rules.

Responsibilities

Who does what in a PKFARE API integration

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

  • PHPTRAVELS: your booking platform

    Website, agent portal, PKFARE module settings, markup, checkout, payments and booking administration.

  • PKFARE: your flight content

    Fares, availability, fare rules, orders and PNRs. Access, routes and ticketing terms are set by PKFARE and the airlines.

  • Your agency: the commercial workflow

    Selling prices, customer payments and support, including changes and refunds that follow PKFARE and airline rules.

Flight suppliers you can connect:

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

Back office

Run PKFARE flight sales from your admin

Credentials, pricing and booking records for PKFARE, in the same dashboard as the rest of your travel business.

  • Module settings

    Partner ID and API key saved under Modules in your own installation, never shown to customers.

  • Markup and supplier cost

    Each booking keeps the selling price next to the PKFARE fare and tax, so margin is visible per reservation.

  • Order and PNR records

    Order number, PNR, passengers, payment status and the full PKFARE response stored with the booking.

  • No duplicate orders

    A booking that already has a confirmed PNR is not sent to PKFARE again if payment is retried.

  • B2B agent sales

    Agents book PKFARE fares with their own markup and wallet balance in the agent portal.

  • Manage booking

    Staff look up a booking by reference and see passengers, itinerary, payment and notes in one place, not in a separate portal.

Compare

Ways to sell PKFARE flights

The right approach depends on how much of the customer journey and back office you want to own. This is how the common options typically compare.

AreaSupplier portal or custom buildPHPTRAVELS
SearchSupplier portal or custom buildStaff check fares in the supplier portal and copy them into quotesPHPTRAVELSPKFARE fares in your own branded search and agent portal
PricingSupplier portal or custom buildMarkup added by hand or coded from scratchPHPTRAVELSMarkup and currency rules applied per passenger type
BookingSupplier portal or custom buildPassenger data re-typed into the supplier portalPHPTRAVELSOrder and PNR created automatically after payment
RecordsSupplier portal or custom buildSupplier record and internal notes kept apartPHPTRAVELSOne booking record for admin, customer and agent
Time to launchSupplier portal or custom buildA custom build means designing the site, admin and finance flow tooPHPTRAVELSExisting PKFARE module inside a full booking platform

Use cases

Who connects PKFARE to PHPTRAVELS

  • B2C flight booking sites

    Public flight search, online card payment, customer accounts and booking history in one branded site.

  • B2B agent distribution

    Sub-agent logins, private markups and wallet or credit payments for agencies and consolidators.

  • Air plus hotel and tours

    OTAs and tour operators combine PKFARE flights with hotels, tours and transfers in one itinerary.

Why PHPTRAVELS

Your PKFARE account, your platform, your code

  • Source code included

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

  • Your PKFARE credentials

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

  • Documented setup

    A PKFARE 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

PKFARE API integration questions

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

Talk to sales

It connects PKFARE flight content to your PHPTRAVELS booking platform through the PKFARE module in the flights category, so customers and agents search, see fare rules, pay and receive a PNR inside your own site.

Access is granted by PKFARE. Once approved, you receive a partner ID and an API key, which you enter in the PKFARE module settings. Check eligibility and commercial terms directly with PKFARE.

A supplier login is useful for quick lookups, but it does not give you a branded booking engine, your own checkout, agent markups, invoices or customer accounts. Many agencies keep the login for support and sell through the integration.

The order number and PNR are saved on the booking, so staff review passengers, itinerary, payment status and notes in your admin. Cancellation is sent to PKFARE by order number; what can be cancelled, changed or refunded follows PKFARE and airline rules.

Yes. One-way, return and multi-city searches are supported, with multi-city legs sent to PKFARE in a single request.

It depends on your plan and the products you enable. Plans start with Startup as a one-time licence; see the pricing page or ask sales for a quote. PKFARE's commercial terms are agreed with PKFARE.

Keep exploring

More from the platform