These operations cover trip-level metadata changes and miscellaneous PNR updates that don't fall into any specific category.
| Step | Operation | Event trigger | Context |
|---|---|---|---|
| 1 | TRIP_UPDATED | When trip-level information changes (e.g., trip name or description) without any car booking changes. | The trip metadata has been updated, but the car booking itself hasn't changed. Example: An admin renames the trip from "LA Business Trip" to "Q1 Client Meeting LA". The TRIP_UPDATED event is triggered. No car booking data is modified. |
| 2 | BOOKING_OTHER_UPDATE | When a change is made to the car booking that doesn't fall into any of the specific categories. | This is a catch-all for all miscellaneous PNR changes. This event is also sent when the PNR version is incremented due to an update. You may receive the BOOKING_OTHER_UPDATE event at any point during the car booking lifecycle containing information on the interactions between Spotnana and the supplier systems. Example: A remark has been added by the system during a backend interaction between Spotnana and the supplier. The BOOKING_OTHER_UPDATE event is triggered with the updated details. |