Overview

Initiate a flight booking session by reserving the offer with the provider, creating a payment intent when you use the Stripe SDK, and discovering available ancillary services — all in a single request.

When to Use

• Start the booking flow once a user has confirmed their flight selection
• Collect passenger details and initiate payment processing
• Discover add-ons like seat selection and extra baggage before final confirmation

What You Get

• Prebook ID required to complete the booking at /flights/bookings
• Payment intent (transactionId, secretKey) when usePaymentSdk is true — for Stripe SDK integration
• Credit line snapshot (creditLine in the response) when you set includeCreditBalance: true and your account has an enabled credit line with payment bypass
• Available services (servicesAttachable) including seats and baggage options
• Booking confirmation from the provider with reservation details

Key Features

• End-to-end prebook flow: Verifies offer → payment setup (Stripe payment intent or credit line) → books with provider → fetches services
• Payment options: usePaymentSdk: true uses the Stripe SDK. usePaymentSdk: false is allowed when your user has payment bypass (sandbox or whitelabel) and either an enabled credit line or a whitelabel/CMI checkout (no Stripe intent; complete payment via WL and call /flights/bookings with payment.method: THIRD_PARTY and payment.token)
• Ancillary services: Returns attachable services (seats, baggage) that can be added before final booking
• Same shape as /book: Uses offerId instead of prebookId

Quick Start

Required fields: offerId (from search/verify), contact (name, email, phone), passengers (with birthday, document, and name details).

Payment: Send usePaymentSdk: true for Stripe (typical). Send usePaymentSdk: false when paying on credit line or via whitelabel/CMI (requires payment bypass); otherwise you receive a validation error.

Tip: Use the servicesAttachable in the response to offer seat selection or extra baggage before calling /flights/bookings.