Overview

Creates a pending post-booking extra-charge batch for an existing flight booking and returns an opaque chargesId. For Stripe-paid bookings, also creates a PaymentIntent (transactionId + secretKey) when usePaymentSdk is true.

Access

Requires Flights API access. Post-booking extra charges are not enabled by default — contact the LiteAPI support team to request access.

When to Use

• Attach fees after confirmation (seat change, baggage, admin adjustment)
• Obtain a Stripe client secret so the customer can confirm payment before POST .../extra-charges/charges

What You Get

• chargesId — Opaque token required by /extra-charges/charges (do not re-send charge lines)
• paymentTypes — Locked to the booking's original payment (TRANSACTION_ID or CREDIT)
• transactionId / secretKey — Present for Stripe bookings when usePaymentSdk is true
• Existing extras totals plus pending batch totals

Constraints

• Booking status must be CONFIRMED or PENDING_CONFIRMATION
• All lines in one request must share the same currency
• Payment method on /charges must match the original booking payment