Booking.com Flights API

Booking.com's Demand API documentation says it includes accommodations, car rentals, and flights for Affiliate Partners. The getting-started path is for Managed Affiliate Partners with Partner Centre access, token credentials, and an affiliate ID. That is not the same as a normal public self-serve flights API for arbitrary developers.

For developers who only need flight prices and booking links, Ignav is the direct path: create an account, verify email, and make authenticated REST calls without waiting for affiliate approval.

What people want from Booking.com flights

The common product idea is to add flights beside hotels: a destination guide with "fly there from $X", a trip planner that compares arrival options, a travel content site, or a search page that sends users out to book. Those workflows need flight search and reliable booking handoff more than they need order management.

How Ignav handles that workflow

Search fares with POST /api/fares/one-way or POST /api/fares/round-trip. Each itinerary includes an ignav_id. Send that ID to POST /api/fares/booking-links and Ignav returns airline and OTA booking URLs. Use GET /api/airports when you need to turn user input into airport codes first.

• 1,000 free requests included.
• $2.00 per 1,000 successful requests after the free tier.
• Failed requests are not billed.
• No monthly minimums.
• No per-account rate limits for authenticated API use.

What Ignav does not cover

Ignav does not provide Booking.com affiliate access, accommodation inventory, car rentals, affiliate reporting, or Booking.com order management. It also does not issue tickets, sell flights, manage bookings, or replace ticketing/order-management APIs.