Skip to content
Air Travel API

Air Travel API

One REST API sells every airline we carry: search, book, ticket, refund and reissue, paid from your FlightOTA deposit.

Airlines

Overview

One REST API sells every airline we carry: search, book, ticket, refund and reissue, paid from your FlightOTA deposit. A booking takes five calls: search, confirm the price, read what to send, book, issue. Most fares are held first and issued later from your deposit. Fares marked instant_ticket: true are paid and ticketed in the booking call itself.

Search

Shops every airline source at once and answers in 5–30 seconds. Offers stay bookable for 15 minutes.

Confirm the price

The airline confirms the price now, so you can show a confirmed total before collecting passenger details.

Hold and issue

Most fares are held first and issued later from your deposit, before hold_expires_at.

After-sales

Void, refund and reissue a ticketed booking. Where the airline does not answer by itself, our desk handles it and quotes by hand.

Air Travel API
Production Gateway

Air Travel API

One REST API sells every airline we carry: search, book, ticket, refund and reissue, paid from your FlightOTA deposit.

Core Capabilities

  • One-way, round trip and multi-city search
  • Standard and branded fares
  • Price confirmation
  • Fare rules

Sandbox notes

Sandbox bookings go to airline test systems: tickets are test tickets and the deposit is test money. Test systems are slower and sometimes refuse what live accepts; a refusal there is a real code your integration must handle. Sandbox holds you do not issue are released automatically.

Interactive API Console & Simulator

Every call in the guide, with its code and the answer the guide shows. These replay the guide's examples; the real API is called from your server, never from a browser.

Offers, extras and airlines

One REST API sells every airline we carry.

Booking flow

A booking takes five calls: search, confirm the price, read what to send, book, issue.

  1. 01Required

    Search

    POST /flights/search

    Offers for one-way, round trip or multi-city.

  2. 02Optional

    Confirm the price

    POST /flights/offers/{offer_id}/price

    The airline's price now.

  3. 03Recommended

    Read what to send

    GET /flights/offers/{offer_id}/extras

    Who to send, in what order; seats, bags, meals.

  4. 04Required

    Book

    POST /flights/bookings

    A held booking (or a ticketed one for instant fares).

  5. 05Required

    Issue

    POST /flights/bookings/{booking_ref}/issue

    Tickets, paid from your deposit, before hold_expires_at.

5–30 s
Search answers in
15 min
Offers stay bookable
1–6
Slices in one search
23:59
Void window ends, Asia/Dhaka, day of issue

Endpoints

Base URL: https://api.flightota.com/api/v1 (production) · https://sandbox.flightota.com/api/v1 (sandbox). Expand an endpoint for parameters, code samples and example responses.

Getting started

Search

Offer details

Book

Ticket, read and cancel

Extras after booking

After-sales

Deposit

Plans & limits

Paid from your deposit, in your billing currency.

  • In the agent portal, open API access, buy the API plan and issue a sandbox key.
  • Rate limit is per key and set by your plan. Over it, you get 429 rate_limited; wait a minute.
  • Tickets, instant fares, accepted reissue quotes and paid extras are taken from your deposit; refunds and voids are paid back into it.
  • Currency is your account's billing currency. Every offer, booking and refund is in it.

Getting started

From a sandbox key to your first call. Live keys are switched on after certification.

Integration Architecture
Developer Fast-Path

Five calls from search to ticket

A booking takes five calls: search, confirm the price, read what to send, book, issue. Most fares are held first and issued later from your deposit.

  1. STEP 01

    Get a key

    In the agent portal, open API access, buy the API plan and issue a sandbox key. The secret is shown once; store it server-side only.

  2. STEP 02

    Whitelist your server

    A key only works from the public IP addresses you add under API access (up to 5 on a live key, 20 on a sandbox key). Never call the API from a browser or mobile app.

  3. STEP 03

    Send two headers on every request

    X-Api-Key and X-Api-Secret. No login call, no token.

  4. STEP 04

    Call ping first

    It tells you which agency and key you are, and the IP we saw, which is the address to whitelist if you get a 403.

Global Travel Gateway
Instant Sandbox Provisioning

Start building with the Air Travel API

Create an account, generate a test key and make your first request in minutes. No credit card required.