API reference
Every endpoint and webhook event has its own page, with examples in five languages and a Try it console against staging. Every call carries your API key in the X-API-Key header, see the Authentication guide. This page has what those pages do not: the specification files, a Postman collection and the MCP server.
Sections
- Partners API
Partners
- Transfer Companies API
Transfer companies
- EVENTWebhook events
10 events
One page per event, listed in the sidebar. Start with Driver assigned.
OpenAPI specifications
One OpenAPI file per API with the published endpoints, curated examples and the staging server as base URL.
- Partners APIv1.0.0partners.openapi.json
https://warpdrive.staging.transferz.com/partners
- Transfer Companies APIv0.9.0transfer-companies.openapi.json
https://warpdrive.staging.transferz.com/transfercompanies
Postman collection
One collection per API, a folder per section and a request per endpoint, with an example body where the endpoint takes one.
- Partners APIpartners.postman_collection.json
- Transfer Companies APItransfer-companies.postman_collection.json
- In Postman choose Import and drop the collection file.
- Import the Transferz staging environment and select it.
- Paste your API key into the
apiKeyvariable. Requests send it in theX-API-Keyheader.
MCP server
Give your coding agent this documentation: it can search the guides and the reference and read endpoint and webhook pages. The documentation tools need no credentials.
https://developers.test.transferz.com/mcpclaude mcp add --transport http --scope user transferz-docs https://developers.test.transferz.com/mcpAll clients, the tools and agent access