Getting started as a partner
Make your first call to the Transferz staging API from your own system. You need the onboarding email from Transferz. About 10 minutes.
0 of 3 steps done
Transferz set up two staging accounts for you and emailed the details. Your person account is for you. Your integration account (
…@integrations.staging.transferz.com) is the one your system uses. API keys and request recording belong to the account that creates them, so do every step on this page signed in with the integration account.The first time you sign in, Transferz asks you to choose a new password. Nobody can receive email at the integration address, so "Forgot password" doesn't work for it. If you lose the password, ask Transferz in a support ticket.
Sign in to start
Use the integration account from your onboarding email.
Access is set up by Transferz. No email yet? Contact your Transferz contact.
Your system sends an API key in the
X-API-Keyheader of every call. The key belongs to the account that creates it: here, your integration account. Store it in your secret store, never in source code or browser code. A key expires three months after it was last used.Available after you sign in with your integration account (step 1).
Search for KLM flights from London Heathrow to Amsterdam Schiphol, a week from today. Send the request from your terminal or your own code, not from this portal: the point is to prove that your system can reach Transferz staging with your key.
GET /flights/searchReferenceSign in to fill in your staging key. Sign incurl --request GET \ --url 'https://warpdrive.staging.transferz.com/partners/flights/search?airlineIataCode=KL&departureAirportIataCode=LHR&arrivalAirportIataCode=AMS&arrivalDate=2026-11-25' \ --header 'Accept: application/json' \ --header 'X-API-Key: YOUR_STAGING_API_KEY'Show example response
Sample data
Response 200[ { "flightDesignators": [ { "airlineCode": "KL", "flightNumber": "1234", "primary": true, "airlineName": "KLM" } ], "scheduledDepartureTimeLocal": "2026-11-25T11:15:00", "departureAirportIataCode": "LHR", "scheduledArrivalTimeLocal": "2026-11-25T13:40:00", "arrivalAirportIataCode": "AMS", "departureAirportCountryCode": "GB", "arrivalAirportCountryCode": "NL" }]A
200response with a list of KL flights from LHR to AMS on that date. Each flight has its flight number (flightDesignators), scheduled times and airports. An empty list is also a successful call: it means no flights were found on that date.This page sees your call through request recording: a copy of each call made with this account's API keys (method, path, status, duration, and the request and response bodies). Transferz switched it on for your integration account when it set the account up, and you'll use it to debug while you build. If it's off, this step offers to turn it on. Calls made in the first few seconds after recording starts or a key is created are not recorded, so wait a few seconds before you make a call. Every recorded call is in Workspace › Request log.
Not listening
Sign in with your integration account first (step 1).
On your phone? Send the request from your computer. This page keeps listening while it's open.
Got an error in your terminal?
A call without a valid key of this account can't be linked to you, so this page may not see it. These are the usual causes.
Status Likely cause Fix 401 The X-API-Key header is missing, or the key is wrong, deleted or expired. Copy the key again, or create a new one in step 2. The header name is X-API-Key. 403 The key's account can't use this API or this company. Check that the key comes from your integration account and that you call the Partners API (…/partners), not the Transfer Companies API. 400 A required parameter is missing or invalid. Send departureAirportIataCode and arrivalAirportIataCode as 3-letter codes, and arrivalDate as YYYY-MM-DD. The message in the response's errors list says what is wrong. 404 Wrong base URL or path. Use https://warpdrive.staging.transferz.com/partners/flights/search. A common slip is leaving out /partners. 429 Too many requests in a short time. Wait a minute and send it once more. 5xx Staging had a problem. Send it again in a minute. If it keeps failing, check the staging status. API status
What to build next
Follow these in order. Each guide ends with a link to the next.
- How a booking worksThe lifecycle of a partner booking, from quote to completed journey.
- Request quotesRequest quotes for a transfer, including return trips and flight lookup.
- Create a bookingTurn a quote into a booking with traveller details and your own reference.
- Pay for a bookingPay for a booking by invoice, payment link or Stripe Connect.
- WebhooksReceive events from Transferz, verify their signature, acknowledge them, and handle retries, order and duplicates.
- Follow a journeyFollow a journey's status, driver and vehicle by webhook or polling, and get its voucher.
- Cancel a journey or a bookingCancel one journey or a whole booking, with or without cancellation charges.
- Going liveWhat to check before launch, the go-live checklist, and whom to contact before and after launch.
Also available: Optional modules · Suggest a pickup time · Change a journey
Stuck?
- Ask AI answers from these docs. Open it with ⌘I or the Ask AI button in the header.
- For anything about your accounts or staging, ask Transferz in a support ticket.
- To see the whole flow without an account, try the walk-through on sample data.