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 hotel booking changes. | The trip metadata has been updated, but the hotel booking itself hasn't changed. Example: An admin renames the trip from "NYC Business Trip" to "Q1 Client Meeting NYC". The TRIP_UPDATED event is triggered. No hotel booking data is modified. |
| 2 | BOOKING_ OTHER_UPDATE | When a change is made to the hotel booking that doesn't fall into any of the specific categories. | This is a catch-all for miscellaneous PNR changes that don't affect dates, rates, confirmation numbers, or booking status. This event is also sent when the PNR version is incremented due to any updates. You may receive the BOOKING_OTHER_UPDATE event at any point during the hotel 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, GDS, and the supplier (e.g., a COMMISSION APPLIES remark added to the PNR). The BOOKING_OTHER_UPDATE event is triggered with the updated details. |