Skip to content

Direct API

Supply your engineers can ship against

REST and JSON endpoints for search, price, book, cancel and retrieve. Sandbox credentials on day one, real fares in staging, production in weeks.

REST JSON over HTTPS
Day 1 Sandbox credentials
3 wks Median time to production
99.9% Target search availability

Integration

Designed by people who have integrated travel APIs

Predictable shapes, honest error codes, idempotent booking calls and documentation written against the actual responses.

One contract, all supply

A single request shape covers every connected supplier. You do not write a branch per wholesaler.

Idempotent booking

Booking calls take an idempotency key, so a timeout retry cannot create a duplicate PNR.

Async search

Poll or subscribe to a webhook for slower suppliers instead of blocking your request thread.

Webhooks for change

Schedule changes, cancellations and refund settlement pushed to your endpoint, with signed payloads and replay.

Rate limits you can plan for

Documented quotas per environment, with headers on every response so you can back off gracefully.

Scoped credentials

Separate keys per environment and per product, revocable independently, with request signing available.

Endpoints

The whole booking lifecycle

Search through to settlement, including the unglamorous parts most APIs leave you to work out from support tickets.

  • POST /v1/search — flights and hotels, async or blocking
  • POST /v1/price — revalidate before you take payment
  • POST /v1/book — idempotent, returns PNR and documents
  • POST /v1/cancel — penalty preview before you commit
  • GET /v1/bookings/{id} — current state and history
  • Webhooks — change, cancellation and refund events

Request

// One shape, every supplier
POST /v1/search
{
  "product": "flight",
  "origin":  "LHR",
  "destination": "JFK",
  "departure": "2026-09-12",
  "passengers": { "adults": 2 },
  "cabin": "economy"
}

// 200 — partial results are explicit
{
  "offers": [ /* … */ ],
  "suppliers_queried": 50,
  "suppliers_responded": 48,
  "expires_at": "2026-09-01T10:14:22Z"
}

Onboarding

From credentials to production

01

Sandbox

Keys and documentation the same day. Deterministic fixtures so tests stay stable.

02

Staging

Live fares, real availability, no ticketing. Build and break things safely.

03

Certification

A short review of your booking, cancellation and error handling with our solutions engineer.

04

Production

Live keys, agreed rate limits and a named engineering contact.

The direct API was live in our platform inside three weeks. Previous integrations took us the better part of a year.
Priya Raman · CTO, Northbound OTA, Bengaluru

API FAQs

Questions from engineering teams

The API is plain REST over HTTPS with JSON bodies, so any HTTP client works. We publish an OpenAPI 3 description you can generate a client from, plus reference examples in PHP, Python, Node and Go.

Connected to the suppliers your clients already trust

  • Amadeus
  • Travelport
  • Sabre
  • Expedia
  • WebBeds
  • Hotelbeds
  • TBO
  • Restel
  • Mystifly
  • Duffel

Free to join

Start booking at net rates today

Create an account in minutes. No upfront cost, no contract, no credit card — you only pay when your client confirms.

  • No sign-up fee
  • No contracts
  • 24/7 booking