New booking lifecycle webhooks

October 29, 2025

We have introduced new booking lifecycle webhooks to gain more transparency into their execution via the tours.

Published when a tour that the booking's stops are dispatched to is started. Beware that in rare cases, the driver_location may be unavailable and therefore null.

Webhook booking.driver_location_updated

Published when the location of the tour's driver, that the booking's stops are dispatched to, is updated.

Together with the new booking lifecycle events, we’ve added new booking’s stop lifecycle event webhooks.

Webhook booking.stop_arrived

Published when the driver arrives at the stop. It's driven by the state of the dispatched stop.

Webhook booking.stop_completed

Published when the driver completes the stop. It's driven by the state of the dispatched stop.

Webhook booking.stop_failed

Published when the driver fails the stop. It's driven by the state of the dispatched stop.

Additionally, we’ve enriched the existing booking.etas_recalculated webhook with the customer ID property, as well as the ETA info regarding the next 10 unfinished stops.

Webhook booking.etas_recalculated

Published when the ETAs for the booking's stops have been recalculated.

The publication of these webhooks is based off on the lifecycle of the underlying tour(s) and their stops used to complete the booking.