Skip to content
Booking: Not started

Partner walk-through · Step 1 of 7

Connectsend an API key

Sample data. Nothing is sent to Transferz.

Why this step exists

Alex lands at Amsterdam Schiphol on flight TZ1234 from London and needs a ride to a hotel on the Herengracht. You sell Alex the transfer.

Every call to the Partners API carries your API key in the X-API-Key header. There is no separate login call: the key alone identifies you.

A harmless first call proves that the key works. Here you look up Alex's flight, which you will also use later to time the pickup.

The request

curl --request GET \  --url 'https://warpdrive.staging.transferz.com/partners/flights/search?arrivalAirportIataCode=AMS&departureAirportIataCode=LHR&arrivalDate=2026-12-01' \  --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

A missing, wrong or expired key gets 401 with an empty body, so there is no error code to log. Check the header name (X-API-Key) and call the API from your server: keys never belong in browser or mobile code.

Was this helpful?