Skip to content
Booking: Not started

Partner walk-through · Step 5 of 7

Follow the ridestatus, driver and position events

Sample data. Nothing is sent to Transferz.

Why this step exists

On the day, Transferz tells your endpoint what happens: a driver is assigned, the vehicle is known, and the driver's position updates as they drive to Schiphol.

Each event arrives as a signed POST. Check the signature before you trust it, answer 2xx quickly, and fetch the full journey when you need more detail.

The event arrives

Your endpoint · https://example.com/webhooks/transferz

Sample events

No events yet. Run the step and 3 events arrive here, as your endpoint would receive them.

Sample data · nothing is sent

Then fetch the details

Fetch the journey with driver and vehicle

GET/journeys/{journeyId}Get journey by id in the reference

Step 3 has not been run yet, so this uses the sample journey. Run step 3 to use your own.

curl --request GET \  --url 'https://warpdrive.staging.transferz.com/partners/journeys/488213' \  --header 'Accept: application/json' \  --header 'X-Request-ID: req-ams-0001' \  --header 'X-API-Key: YOUR_STAGING_API_KEY'
Sample data · nothing is sent

Common pitfall

Verify the signature over the raw request body, before any JSON parsing. Re-serialising the parsed JSON changes spaces and order, and the check fails for every event.

Was this helpful?