# Seat changes

These operations cover the changes that can be made to seat assignments on the booking.

**Webhook used:** [PNR_V3](/openapi/webhookeventapi/webhooks/paths/pnr_v3/post)

| Step | Operation  | Event trigger | Context |
|  --- | --- | --- | --- |
| 1 | `FLIGHT_SEAT_ CONFIRMED` | When a requested seat assignment is confirmed by the airline. | A seat that was in a pending or requested state has now been confirmed by the airline.
**Example:** A traveler requested seat 14A (window).
The airline confirms the assignment and the operation is triggered with the confirmed seat details. |
| 2 | `FLIGHT_SEAT_ CHANGED` | When a confirmed seat is reassigned to a different seat by the airline. | The traveler's confirmed seat number has changed.
The most common cause is an aircraft equipment swap where the airline changes the plane type and the seat map is completely different.
If the traveler paid for a premium seat selection (e.g., extra legroom), the fee is not automatically refunded.
The traveler or the agent should contact the airline to request a refund for the seat.
**Example:** A traveler paid $45 for seat 14A (extra-legroom window).
The airline swaps the aircraft and reassigns them to seat 22C (middle seat, standard legroom).
The `FLIGHT_SEAT_CHANGED`event is triggered with the updated seat info.
The $45 seat fee is not automatically refunded, so the traveler should request a refund through the TMC or airline. |
| 3 | `FLIGHT_SEAT_ CANCELLED` | When a confirmed seat assignment is completely removed by the airline. | The traveler's seat assignment has been removed entirely.
The flight booking and ticket exist but no specific seat is assigned for the traveler.
This could be due to an aircraft equipment swap, or a schedule change requiring re-accommodation on a different flight.
The system does not automatically rebook a new seat.
The traveler must manually select a new seat from the seat map, or the airline will assign one at check-in.
Paid seat fees are not automatically refunded and the refund depends on the airline's policy.
**Example:** A traveler had seat 8F confirmed on a London to Dubai flight.
The airline changes the aircraft from an A380 to a 777 and seat 8F no longer exists.
The event `FLIGHT_SEAT_CANCELLED` is triggered. The traveler can now select a new seat from the available seat map, or wait until check-in for an airline-assigned seat.
If they paid for the original seat, they should contact support to request a refund. |


## Seat change flow diagram


```mermaid
flowchart TD
    subgraph seats["Seat changes"]
        A(["Ticketed booking"]) --> B{"Seat change <br>initiated?"}

        B -->|"Seat<br>confirmed"| C["<b>FLIGHT_SEAT_<br>CONFIRMED</b><br>―――――――――――<br>Requested seat confirmed<br>by the airline."]

        B -->|"Seat<br>changed"| D["<b>FLIGHT_SEAT_<br>CHANGED</b><br>―――――――――――<br>Seat reassigned<br>(e.g., equipment swap).<br>Paid seat fee NOT<br>auto-refunded."]

        B -->|"Seat<br>cancelled"| E["<b>FLIGHT_SEAT_<br>CANCELLED</b><br>―――――――――――<br>Seat removed<br>(e.g., equipment swap).<br>Traveler must select<br>a new seat."]
    end

    style A fill:#f0f0f0,stroke:#999
    style C fill:#2196F3,color:#fff
    style D fill:#FF9800,color:#fff
    style E fill:#F44336,color:#fff
```