Trip Stops

Taxi & Private Hire › Products › Trip › Trip Stops

Generally available

A stop is one waypoint on a trip — a pickup, dropoff or intermediate point. Each carries its address and coordinates, an expected arrival time, a type (pickup / dropoff / waypoint) and its own lifecycle (scheduled → en route → arrived → finished, or no-show / cancelled) that drives the driver app.

Example request

POST /client/{clientId}/tripsegmentstop/{tripSegmentStopId}/arrived ▷ Try it

See the API reference for the full request and response schema.

Endpoints

Method	Path
POST	/client/{clientId}/tripsegmentstop/{tripSegmentStopId}/arrived · primary	▷ Try it
POST	/client/{clientId}/tripsegmentstop/{tripSegmentStopId}/call-customer	▷ Try it
POST	/client/{clientId}/tripsegmentstop/{tripSegmentStopId}/cancel	▷ Try it
POST	/client/{clientId}/tripsegmentstop/{tripSegmentStopId}/finished	▷ Try it
POST	/client/{clientId}/tripsegmentstop/{tripSegmentStopId}/noshow	▷ Try it

Full request/response schemas and an interactive explorer will live in the API reference (coming soon).

Use cases

Operator flows that exercise this feature.

Log a customer contact

action risk: low

Record an attempt to contact the customer at a stop (counts toward the no-show call guard).

1. POST /client/{clientId}/tripsegmentstop/{tripSegmentStopId}/call-customer

Mark a no-show

action risk: low

Record a passenger no-show at a stop, once the no-show guards are met.

1. POST /client/{clientId}/tripsegmentstop/{tripSegmentStopId}/noshow

Related

• Trips
• Trip Segments