Support for external IDs on bookings

September 24, 2025

We have introduced support for passing external IDs on the booking creation that will be stored in our system and becomes visible in API responses and booking-related webhook notifications.

This feature allows easier integration of external systems for booking management with MotionTools, by allowing you to correlate a booking ID on the other system with booking data stored and published via MotionTools, as the booking procedes through it’s lifecycle.

post /api/hailing/bookings

Create a Booking

This property will be returned only on bookings fetched via standard and compact views. You can also filter by the external_id on the bookings list.

get /api/hailing/bookings

All Bookings

get /api/hailing/bookings/{id}

Show Booking

The property is also included in the CSV export of the bookings.

post /api/hailing/bookings/export

Export Bookings as CSV

We have also extended all our booking-related webhooks to contain the external_id when present. This allows you to more easily reference the booking on your side against your own identifier without having to store our booking ID alongside it and match them.

Webhook booking.created

Published when a new booking has been created

Webhook booking.etas_recalculated

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

Webhook booking.modified

Published when some part of booking is modified, e.g. when stops are changed.

Webhook booking.route_changed

Published when the route of a booking has changed, i.e. by adding or removing stops, changing their locations, changing their order and so on.

Webhook booking.transition

Indicates a change of status of a booking.

Support for external IDs on bookings

Help center articles