Skip to content

Environments

The staging and production environments, and the base URL of each Transferz API.

Updated · 1 min read

Transferz runs two separate environments. You build and test against staging, then switch to production when your integration is certified.

Staging and production

StagingProduction
PurposeBuild and test. Journeys are not driven.Real bookings and real drivers
Accounts and API keysStaging account, keys from this portalIssued after certification
Webhook endpointYour test endpointYour production endpoint
Used by this portalYes, for everythingNever

The two environments share nothing. Accounts, API keys, webhook settings, IDs and test data on staging do not exist in production, and the other way round. Keep the base URL, the API key and the webhook signing key in configuration, so you can switch environments without code changes.

status.transferz.com (opens in a new tab) shows the status of production. Staging has no status page; it is available on a best-effort basis.

Base URLs

Append the endpoint path from the API reference to the base URL of its API.

APIStagingProduction
Partners APIhttps://warpdrive.staging.transferz.com/partnershttps://warpdrive.transferz.com/partners
Transfer Companies APIhttps://warpdrive.staging.transferz.com/transfercompanieshttps://warpdrive.transferz.com/transfercompanies

For example, the staging URL to request quotes is https://warpdrive.staging.transferz.com/partners/quotes.

All APIs accept and return JSON over HTTPS. Read Conventions for dates, pagination and request IDs.

Moving to production

When your integration is certified you switch the base URLs, the API key and the webhook endpoint to production. Going live has the full checklist.

Was this helpful?

Back to your build path →