There are some common mistakes made when sending driver events via the API.
This article will explain how to avoid them.
- Driver not assigned: Before a driver event can be sent, you must first assign a driver. Follow the steps in the documentation to do this.
- Events sent in the wrong order: Driver events must be sent sequentially in the following order:
| EVENT | DESCRIPTION |
|---|---|
| DRIVER_DEPARTED_TO_PICKUP | Driver has started the job and is on their way to the pickup location. |
| DRIVER_ARRIVED_AT_PICKUP | Driver has arrived at the pickup location and is ready to meet the customer. |
| DRIVER_DEPARTED_TO_DROPOFF | Driver has collected the customer and is on their way to the dropoff location. |
| DRIVER_ARRIVED_AT_DROPOFF | Driver has completed the ride and has dropped off the customer. |
- Event time is after current time: You cannot send an event in the future. Remember to use UTC format when sending events to avoid time zone issues.
- Event time is before driver assignation: You cannot send an event before the driver has been assigned. Remember to use UTC format when sending events to avoid time zone issues.
-
The provided driver ID does not match the assigned ID: If you're not using the Booking.com driver app, then there is no need to send a driver_id. Simply omit this from the request.
-
Unable to find booking with bookingReference provided: The booking reference or customer reference provided do not match any bookings assigned to you. Check they are the correct way around in the request.
Still need help with driver events? Contact us.