Skip to content
Journey: Not started

Transfer company walk-through · Step 5 of 7

Share journey trackingDriver App or your own system

Sample data. Nothing is sent to Transferz.

Why this step exists

During the ride, the traveller and the partner follow the driver live. Either your driver uses the Transferz Driver App, which reports everything by itself, or your own system reports status and positions through the API.

With your own system you report that the driver is on the way, send positions while they drive, say when they arrived and when the traveller is on board.

How does the driver share the ride?

Your dispatch system calls the API for each status and position.

Driver leaves for Schiphol

PUT/journeys/{id}/status/driver-underwayUpdate status to 'driver underway' in the reference

Step 2 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/status/driver-underway' \  --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 '{  "latitude": 52.3462,  "longitude": 4.9171,  "recordedAt": "2026-12-01T12:40:00"}'
Sample data · nothing is sent

Send a position

PUT/journeys/{id}/driver-positionUpdate driver position in the reference

Step 2 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/driver-position' \  --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 '{  "latitude": 52.3091,  "longitude": 4.7624,  "recordedAt": "2026-12-01T13:12:05"}'
Sample data · nothing is sent

Driver is at the meeting point

PUT/journeys/{id}/status/driver-arrivedUpdate status to 'driver arrived' in the reference

Step 2 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/status/driver-arrived' \  --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 '{  "latitude": 52.3091,  "longitude": 4.7624,  "recordedAt": "2026-12-01T13:12:05"}'
Sample data · nothing is sent

Traveller is on board

PUT/journeys/{id}/status/in-progressUpdate status to 'in progress' in the reference

Step 2 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/status/in-progress' \  --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 '{  "latitude": 52.3101,  "longitude": 4.7655,  "recordedAt": "2026-12-01T13:55:00"}'
Sample data · nothing is sent

Common pitfall

Status changes too far before pickup are refused (JOURNEY_STATUS_CHANGE_NOT_ALLOWED_IF_PICKUP_TIME_TOO_FAR_IN_FUTURE). Send positions every 30 to 60 seconds while driving, with recordedAt in local time.

Was this helpful?