Skip to content

Understanding our driver endpoints

What does it do?

The driver endpoints allow you to:

  • Assign drivers to accepted bookings (all partners with own driver app)
  • Manage drivers via CRUD operations (partners using the Booking.com Taxi Driver App only)

Note

If you're not using the Booking.com Taxi Driver App, you don't need to create drivers with the Public API. You only need the Assign Driver endpoint.

How does it work?

For partners with their own driver app:

  1. Authenticate — obtain an access token
  2. Accept a booking — transition booking to ACCEPTED status
  3. Assign a driver — call POST /v2/bookings/:bookingReference/assignDriver with driver and/or vehicle details
  4. Send driver events — once assigned, send driver events to keep customers updated

For partners using the Booking.com Taxi Driver App:

  1. Authenticate — obtain an access token
  2. Create drivers — call POST /v1/drivers with driver details. An SMS activation link will be sent to the driver.
  3. Assign a driver — call POST /v2/bookings/:bookingReference/assignDriver with the driverId returned from step 2
  4. Driver events are sent automatically by the Booking.com Driver App

Note

The driverId used in assign driver is the UUID returned when creating a driver — not a custom or legacy ID.

See our endpoint references for full details.

Further reading