Understanding our driver endpoints¶
What does it do?¶
Our driver endpoints allow you to manage drivers when you're using the Booking.com Taxi Driver App and assign drivers to bookings, when new drivers are created the API will also take care of sending the driver app activation link to your drivers.
Note
If you're not using the Booking.com Taxi Driver App, you don't need to create drivers with the Public API.
Why use it?¶
By creating drivers, it enables you to send driver events to keep customers informed at the time of pickup by letting them know that the driver is on the way or that they've arrived at the pickup location. You can also update driver details and remove drivers as necessary.
How does it work?¶
Our driver management endpoints are part of the Taxi Public API, you'll need to authenticate with the API to get started.
Warning
It's important your Client ID & Client Secret keys remain private and are not shared.
High-level Flow¶
- Once on-boarded a
clientID
andclientSecret
will be provided to you. The authentication endpoint can be called to exchange the keys with an access token which is then used to authenticate each subsequent request. - If you're using the Booking.com Taxi Driver App, you can use the token to create drivers by calling
/v1/drivers
. - You can then assign created drivers to
ACCEPTED
bookings via the/v2/bookings/:bookingReference/assignDriver
endpoint, you can assign a driver as many times as necessary (e.g. if you need to re-assign another driver). - Once a driver has been assigned the booking status will transition to DRIVER_ASSIGNED and you can send driver events.
See our endpoint references for more information.