Flight Exchange

Exchanges a booked flight for a different itinerary.

get_booking with booking_ref (and last_name for guests) returns items[] with servicing eligibility and refusal reasons for item selection. The same booking_ref + booked_item_id identifies the selected item on every action, including commit and status. booked_item_id is the stable booked item, even after an exchange. last_name is required for guests and optional for authenticated owners. A 409 with items[] means customer selection is needed; a retry identifies that choice with booked_item_id.

Guest verification uses the Jinko booking reference and traveler last name; no login is required.

The workflow is shop → price → commit → status:
1. action="shop" with booking_ref + booked_item_id (plus last_name for guests) and segments_to_exchange browses exchange alternatives. segments_to_exchange names each leg to change by the airports get_booking lists for it (the leg's first departure and final arrival airport, not a connection airport) with its new departure_date; legs not named stay as booked. To change only the return, name only the return leg. A refusal names the booked legs.
2. action="price" with the same identity and offer_id obtains exact pricing: the current ticket, the new ticket's value, the airline change fee if any, and the amount due or refunded.
3. action="commit" with the same identity, offer_id and the quote_id from price carries out the exchange the customer agreed to after seeing that price: its ticket values, change fee, amount due or refunded and the new fare's terms. An exchange can involve an additional payment or a pending refund. When the customer pays a difference, the commit returns a payment page: the exchange is carried out only after that payment is authorized, so send the customer to the page; action="status" returns the same page while it waits. A price refused because the exchange can't be refunded automatically returns no quote_id: if the traveler confirms, commit the same offer_id without one, which sends the request to Jinko support.
4. action="status" with the same identity reports exchange progress.

When the answer carries customer_amounts (the price prints "Current ticket" and "New ticket"), its figures obey: current ticket + amount due − amount refunded = new ticket + change fee + residual value (an absent figure counts as 0).
Answers without customer_amounts carry older supplier figures that need not add up; the identity does not apply to those answers.
The "You pay" / "You get back" line (on older answers, "Total Due" / "Total Refund") gives the amount due or refunded directly, without reconstruction from the ticket values and change fee. A quoted refund is pending, rather than money already returned.
In the structured result, customer_amounts holds the traveler's figures when present; the top-level fare_difference, original_fare, new_fare and penalty_amount keep an older supplier meaning and are not the traveler's figures.

The airline reference is the locator usable on the airline's site or at check-in. If absent from this result, get_booking or the original confirmation can supply it. The same booking_ref + booked_item_id identifies the booked item after an exchange.

An exchange re-fares the ticket, so the traveler ends up on a different product. A price output that opens with "FARE CHANGE" states the one change the amount due or refunded does not show: a cheaper exchange can still move the traveler off a refundable fare. The "New fare" block gives the new fare's refund policy, change policy, checked baggage and carry-on. "Not stated by the fare" means the provider stated no rule: it is unknown, which is neither "non-refundable" nor "included", and the replaced ticket's rules are not carried over to it.