Skip to content
Journey: Not started

Transfer company walk-through · Step 3 of 7

Assign a driver

Sample data. Nothing is sent to Transferz.

Why this step exists

The traveller wants to know who picks them up. Assign the driver with a name and phone number as soon as you have planned the ride.

Transferz passes the driver on to the partner and the traveller, so they can contact each other.

The request

PUT/journeys/{id}/assign-driverAssign to driver in the reference

The previous step has not been run yet, so this uses the sample journey. Run step 2 to use your own.

curl --request PUT \  --url 'https://warpdrive.staging.transferz.com/transfercompanies/journeys/488213/assign-driver' \  --header 'Accept: application/json' \  --header 'Content-Type: application/json' \  --header 'X-Request-ID: req-ams-0002' \  --header 'X-API-Key: YOUR_STAGING_API_KEY' \  --data '{  "name": "Jordan Driver",  "phoneNumber": "+447700900456",  "notifyBySms": false,  "reassign": false}'
Sample data · nothing is sent

Common pitfall

A journey that already has another driver is refused with JOURNEY_ALREADY_ASSIGNED_TO_OTHER_DRIVER. Send reassign: true when you deliberately swap drivers.

Was this helpful?