Arrival Guards
Taxi & Private Hire › Products › Trip › Arrival Guards
Generally available
Pre-flight checks that block a driver from marking a stop as arrived / finished when real-world conditions are not met — proximity to the stop, sensible elapsed time, etc. Run on `/tripsegmentstop/{id}/arrived` and `/tripsegmentstop/{id}/finished` for DRIVER auth only. USER and SYSTEM auth bypass entirely. Operators see guard verdicts in the dispatch audit log; drivers see them as actionable error responses in the app.
Example request
POST /client/{clientId}/tripsegmentstop/{tripSegmentStopId}/arrived
See the API reference for the full request and response schema.
Endpoints
| Method | Path | |
|---|---|---|
POST | /client/{clientId}/tripsegmentstop/{tripSegmentStopId}/arrived · primary | |
POST | /client/{clientId}/tripsegmentstop/{tripSegmentStopId}/call-customer | |
POST | /client/{clientId}/tripsegmentstop/{tripSegmentStopId}/cancel | |
POST | /client/{clientId}/tripsegmentstop/{tripSegmentStopId}/finished | |
POST | /client/{clientId}/tripsegmentstop/{tripSegmentStopId}/noshow |
Full request/response schemas and an interactive explorer will live in the API reference (coming soon).
Use cases
Operator flows that exercise this feature.
action risk: low
Record an attempt to contact the customer at a stop (counts toward the no-show call guard).
POST/client/{clientId}/tripsegmentstop/{tripSegmentStopId}/call-customer
action risk: low
Record a passenger no-show at a stop, once the no-show guards are met.
POST/client/{clientId}/tripsegmentstop/{tripSegmentStopId}/noshow
Settings
How operators configure this feature.
Some jobs drop several passengers or parcels at the same address — a block of flats, an office, an event door. Without this, the driver has to tap "arrived" on each one separately, which is fiddly and slows them down. Turn it on and the moment they arrive at one stop, every other stop at the same place (within a distance you set) is marked arrived automatically. It only ever groups stops that are genuinely together, so nothing far away gets swept up by mistake. Leave it off and drivers confirm each stop by hand.
On / off · default false
An arrival or no-show only means something if the driver was actually there. This requires a driver to be genuinely at the stop — and to have a working location — before they can mark arrival or record a no-show, so the timeline you bill and report from holds up.
| Setting | Range | Default |
|---|---|---|
| Require location for these actions When On, a driver with no location can't mark arrival or a no-show. | 0–1 | 0 |
| Arrival distance (m) How close to the stop counts as arrived. | 50–1000 | 200 |
| No-show distance (m) How close the driver must be to record a no-show. | 50–1000 | 200 |
| Max location age for arrival (s) A driver's location must be newer than this to mark arrival or a no-show. | 15–300 | 60 |
A driver marking "arrived" well before they could realistically be there is often the start of a wrongful no-show. This sets how early counts as too early, flagging premature arrivals so they can be checked before they cost you a customer.
| Setting | Range | Default |
|---|---|---|
| Early arrival allowed (min) How many minutes early a driver can arrive before it is flagged. | 5–60 | 15 |
Asking drivers to tap "arrived" is one more thing to forget, and forgotten taps skew your timings. This automatically marks the driver arrived once they're within a set distance of the stop — saving a step and keeping arrival times honest.
| Setting | Range | Default |
|---|---|---|
| Auto-arrive distance (m) Co-located stops within this distance are marked arrived together when the driver arrives at one. | 25–500 | 100 |
When a driver gets close to a pickup, we quietly note the moment — no tap required, and it never changes the trip. It's just a clean, honest record of when they actually arrived, separate from the "arrived" button a driver might press early or late. Over time those moments teach the system how long the approach to a pickup really takes in each area, so the promises you make to customers about timing get more accurate. Set how close the driver has to get before we count it as "there".
| Setting | Range | Default |
|---|---|---|
| Pickup proximity distance (m) How close the driver must get to the pickup to record their arrival for timing analytics. Passive — does not mark the stop arrived. | 25–500 | 100 |