These operations cover changes to an active car rental booking. Modifications such as pickup or drop-off date and time, location, vehicle type, rate, and rebooking to a different supplier are covered in these operations.
Webhook used: PNR_V3
| Step | Operation | Event trigger | Context |
|---|---|---|---|
| 1 | BOOKING_UPDATED | When the car booking is modified and the same PNR is updated. | A change has been made to the car reservation that is not a cancellation or rebooking. This event type covers all car modifications, including pickup or drop-off date and time changes, pickup or drop-off location changes, vehicle (car type) changes, number of cars changed, loyalty number updates, and total booking amount changes. If a supplier decides to cancel and rebook for a modification then the BOOKING_UPDATED event will not be sent. Instead, you'll receive a BOOKING_CANCELED_BY_TRAVELER followed by a BOOKING_CREATED event. Use the carPnr > rebookReference object in the BOOKING_CREATED event payload to see the cancelled PNR. Example 1: A traveler extends their rental by one day (drop-off moves from March 18 to March 19). The BOOKING_UPDATED event is triggered on the same PNR with the updated dates and new total ($220). Example 2: A traveler changes the pickup location from the airport to a downtown branch. The supplier cancels and rebooks the reservation with new information. A BOOKING_CANCELED_BY_TRAVELER event is triggered for the original PNR, followed by a BOOKING_CREATED event for the new PNR with the updated location. Example 3 (Loyalty added): A traveler adds their Hertz Gold Plus Rewards membership number to the booking. The BOOKING_UPDATED event is triggered. |
2 |
| When the car booking is rebooked to a different supplier or vehicle. | The car reservation has been rebooked. This indicates the vendor confirmation number has changed.
Rebooking can occur when a better rate becomes available for an equivalent vehicle and an agent or traveler manually rebooks to a different supplier. The |