Environments and base URLs
The staging and production environments, and the base URL of each Transferz API.
Transferz runs two separate environments. You build and test against staging, then switch to production when Transferz gives you production credentials.
Staging and production
| Staging | Production | |
|---|---|---|
| Purpose | Build and test. Journeys are not driven. | Real bookings and real drivers |
| Accounts and API keys | Staging account, keys from this portal | Issued by Transferz |
| Webhook endpoint | Your test endpoint | Your production endpoint |
| Used by this portal | Yes, for everything | Never |
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.
Base URLs
Append the endpoint path from the API reference to the base URL of its API.
| API | Staging | Production |
|---|---|---|
| Partners API | https://warpdrive.staging.transferz.com/partners | https://warpdrive.transferz.com/partners |
| Transfer Companies API | https://warpdrive.staging.transferz.com/transfercompanies | https://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 you go live you switch the base URLs, the API key and the webhook endpoint to production. Going live has the full checklist.