Overview

Complete a flight reservation by confirming a prebook and processing payment. This is the final step in the booking flow.

When to Use

• Final booking confirmation - Convert a prebook into a confirmed booking
• Payment completion - Confirm with Stripe (TRANSACTION_ID) or bill an enabled credit line (CREDIT)
• After service selection - Book after optionally attaching seats or baggage via the services endpoint

What You Get

• Confirmed booking with a unique booking ID
• Payment confirmation with transaction details
• Full itinerary including all segments and passenger assignments
• Provider confirmation reference number

Key Features

• Idempotent: Returns the existing booking (HTTP 200 + data[0].message) if one already exists for the given prebookId in any status except FAILED. FAILED rows are retried in place. Concurrent duplicate requests while a book is in progress return HTTP 409 (45035).
• Payments: Stripe uses transactionId from prebook or attach-services after SDK confirmation; credit line uses CREDIT with server-side eligibility checks
• Provider confirmation: Finalizes the reservation on the provider side

Quick Start

Required fields: prebookId (from POST /flights/prebooks), payment with method and, for Stripe, transactionId

Tip: If you used POST /flights/prebooks/{prebookId}/services to attach ancillary services, use the new transactionId from that response, not the original prebook transactionId.