Statuses
Booking life Cycle

Booking statuses
| Status | description |
|---|---|
| Pending | The order is in creation. |
| Reserved | Pre-book order has been created, will stay in this state until the driver assignment Note: Routing status can be skipped. |
| Routing | On-demand order has been created and locating a driver |
| Confirmed | A driver/courier on the way to the origin location |
| Waiting | The driver/courier has arrived at the origin location and waiting for the passenger/parcel. |
| Driving | The driver/courier has picked up the passenger/ parcel and on their way to the next stop. |
| Completed | The order was completed |
| Cancelled | The order has been cancelled, the order can be canceled by: Booker Rider API request Driver after some waiting time( the time to cancel can vary by services or suppliers |
| Rejected | The order has been rejected On-demand: No driver could perform the order Pre-book: No fleet reserved the order (order can be rejected a few minutes after the booking or after reservation) |
| CareReq | The order is been handled by customer care, the condition can be unique for each product/ customer |
| ActiveOrder | Some suppliers can't share driver location and order statuses, they are called non-integrated/ untrackable suppliers, if a ride is performed by such type of supplier, the cycle will be: 1. reserved 2. active order (instead of confirmed/ waiting/ driving ) 3. completed/ canceled/ rejected |
Stop statuses - stops[0].progress_status
In this context a stop point means either origin location, middle stop or destination
| Status | Description |
|---|---|
| Pending | Stop point was not reached yet |
| Confirmed | Driver/courier has confirmed passenger/parcel was picked up for the delivery to the current stop point. |
| Waiting | The driver/courier has confirmed that he/she has picked up the passenger/parcel for delivery to the current stopping point |
| Completed | Driver/courier delivered the passenger/parcel to the current stop point |
| Cancelled | The stop was cancelled for one of the following reasons: - driver/courier didn't pick up passenger/parcel that was/were should be delivered to the current stop point - order was cancelled by Booker/Rider/API/Driver |
Passenger / Parcel Action status - stops[0].actions[0].status
Refers to the action performed by the driver/courier at the pick-up or drop-off point.
It may vary depending on the type of stop point action type.
| Action type | Action status | Description |
|---|---|---|
| pick_up | Passenger/parcel supposed to be picked up on certain Stop Point | |
| pending_pickup | Driver/courier has not picked up passenger/parcel yet, but supposed to do | |
| picked_up | Driver/courier picked up passenger/parcel (marked in Driver app) | |
| not_picked_up | Driver/courier didn't pick up passenger/parcel (marked in Driver app) | |
| drop_off | Passenger/parcel supposed to de dropped off on certain Stop Point | |
| pending_drop_off | Driver/courier has not dropped off passenger/parcel yet, but supposed to do | |
| dropped_off | Driver/courier marked in Driver app as passenger/parcel was dropped off | |
| not_dropped_off | Driver/courier marked in Driver app as passenger/parcel was not dropped off (not applicable for delvery orders) | |
| stop_by | Transit stop point, no pick_up/drop_off. Valid for taxi rides only | |
| pending_transit_stop | Driver/courier has not arrived to transit stop point yet, but supposed to do | |
| skipped_transit_stop | Driver/courier has skipped transit stop point (e.g. stop point was deleted by Gett customer support agent) | |
| completed_transit_stop | Driver/courier has arrived and completed transit stop point |
Updated about 1 year ago
