Transfer company walk-through · Step 1 of 7
Connectwebhook endpoint, signature key and API key
Sample data. Nothing is sent to Transferz.
Why this step exists
A traveller lands at Amsterdam Schiphol on flight TZ1234 and has booked a ride to a hotel on the Herengracht. Transferz gives the journey to your company, Canal City Transfers.
Transferz pushes journeys to you, so it needs an HTTPS endpoint to send them to. You set that URL in the workspace and get a signature key to check that events really come from Transferz.
For your own calls to the Transfer Companies API you send an API key in the X-API-Key header. A first harmless call, listing tomorrow's journeys, proves the key works.
The request
List journeys on 1 December
curl --request GET \ --url 'https://warpdrive.staging.transferz.com/transfercompanies/journeys?pickupDateAfter=2026-12-01T00%3A00%3A00&pickupDateBefore=2026-12-02T00%3A00%3A00&includedStatuses=CONFIRMED&includedStatuses=PLANNED&page=0&size=20&sort=pickup%3Basc' \ --header 'Accept: application/json' \ --header 'X-Request-ID: req-ams-0002' \ --header 'X-API-Key: YOUR_STAGING_API_KEY'⌘↵ Sample data · nothing is sent
Common pitfall
Treat the signature key like a password: keep it in your secret store, not in source code. The key is used as UTF-8 text; do not decode it from hex or Base64.