Rapid Flights API pilot documentation
Early access preview
This documentation is part of an early access preview initiative for selected partners only. Pilot programs will launch by Q4 2025, with general availability in 2026.
If you are interested in becoming a pilot or beta partner, please reach out to your account manager.
The Rapid /flights API bundle
Rapid Flights API is made up of a selection of endpoints that together enable a search-to-book flow.

Get to know the Rapid Flights endpoints
Because this product is still in the early access phase, please bear in mind that the schema details and functionality are still in active development and may change before the full release of this product to partners.
Action | Method | Rest URI | Result |
---|---|---|---|
Search for available flights | POST | /flight-offers | Returns available offers. |
Request more details on flight offers | GET | /flight-offers/{offer_id} | Returns the details of a flight, including price breakdown and policies. |
Request a seat map for the chosen flight | GET | /flight-offers/{offer_id}/seats | Returns the seat map of a flight if it is available. |
Provide details of the chosen payment method for the booking | POST | /payments | Returns a payment_token , which goes in the body of the create booking request. |
Complete booking | POST | /itineraries/flight | Returns an itinerary ID and links to retrieve reservation details or complete payment session. |
Request details of an existing booking by itinerary ID | GET | /itineraries/{itinerary_id}/flight | Returns itinerary details by the itinerary_id parameter. |
Cancel a booking | DELETE | /itineraries/{itinerary_id}/flight | Cancels an existing booking. |
Use case
Here's how you can use the Rapid Flights API to create an end-to-end booking experience for your customers.
Step 1 - Search available flight offers
First, use the /flight-offers endpoint to allow travelers to see what flights are available.
Check out the key parameters below:
Key parameter | Description | Example |
---|---|---|
departure_airport | The airport from which the flight departs. | LAS |
arrival_airport | The airport at which the flight arrives. | LAX |
departure_date_time | The time and date at which the flight departs. | 2025-01-09T17:45:00-08:00 |
Step 2 - Provide more detail on the available flight options
Before surfacing flight options to your customer, get some more granular information using the /flight-offers/{offer_id} endpoint.
Here's the kind of details travelers need to know before they book:
Object | Use it to... |
---|---|
amenities | Display available in-flight entertainment options, such as WiFi or films. |
baggage_allowance | Provide details on how much luggage is included with the flight. |
change_policy | Indicate whether post-booking changes are allowed and, if so, whether they will incur an additional fee. |
meal_options | What food is served during the flight and whether it is included or is an additional charge. |
Step 3 - Help your customer choose their preferred seat
Use the /flight-offers/{offer_id}/seats endpoint to display a seat map (where available) so travelers can pick their preferred part of the plane.
Example:
cabin_class: economy
exit_row_list:
- '17'
- '18'
rows:
- row_number: 16
seats:
- aisle: false
column: A
seat_number: 16A
availability: not_available
preferred: false
seat_codes:
- window
seat_token: Q11REWlbQV5VARNfBQBxQ14JXAVYTT1XEwtbXEcJUQpTAkBSR0sNFVUIZgVdFENZSxFqBwtRBlx9eDoSVgNGU0ZCQkFTbFFcRRJbF0BrAllcVAh5dTdDVlwVUURBTRRdbwBXR1JcAVMKAUlRBRUCWG1WDEACdg1XFlByBgRLA1wcBXEDABNwDFJbDRFBDA0BDFkOB1oNVA5Q
Step 4 - Payment
You can now use the /payments endpoint to allow the customer to register a payment method for the booking.
The response will contain a payment_token
, which goes in the body of the create booking request.
Step 5 - Create the booking
Use the /itineraries/flight endpoint to complete the booking.
Step 6 - Retrieve booking details
You can use the /itineraries/{itinerary_id}/flight endpoint to retrieve booking details using the itinerary ID. The response will include cancellation links, where applicable.