# Other updates

These operations cover trip-level metadata changes and miscellaneous PNR updates that don't fall into any specific category.

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

| Operation  | Event trigger | Context |
|  --- | --- | --- |
| `TRIP_UPDATED` | When trip-level information changes (e.g., trip name or description). | The trip container has been updated, but the flight details themselves haven't changed.
**Example:** An event coordinator renames the trip from "NYC Business Trip" to "Q1 Client Meeting NYC".
The `TRIP_UPDATED` event is triggered reflecting the metadata change. No flight or ticket data is changed. |
| `BOOKING_OTHER_ UPDATE` | When a change is made to the booking that doesn't fall into any of the specific categories. | This is a catch-all event for miscellaneous PNR changes such as loyalty number additions, special service requests (e.g., wheelchair assistance),
contact information updates, or other miscellaneous PNR modifications.
Everytime an update is made to a PNR, it's `version` number is appended to `n+1`. This version change generates
a `BOOKING_OTHER_UPDATE` event and the payload contains the information about the changes that happened.
You may receive this event at any step in the [air booking lifecycle](/webhooks/booking-lifecycle/air-booking-lifecycle/air-booking-lifecycle-intro).
Even [seat changes](/webhooks/booking-lifecycle/air-booking-lifecycle/seat-changes-lifecycle) could trigger this event as there are changes made to the PNR.
**Example:** A traveler's frequent flyer loyalty number is added to the booking,
or a special service request like wheelchair assistance is submitted.
The `BOOKING_OTHER_UPDATE` event is sent with the updated PNR details. |