Wise API

All the technical details of our APIs can be found here.

We recommend starting from the Integration Guides to work through specific examples of how to integrate with the Wise API.

Explore the comprehensive technical reference documentation for integrating with the Wise Platform API, with examples of all calls as they relate to the important flows for transfer creation, multi currency accounts, and much more.

Below are the standard API endpoints used for our Send Money Flow:

Quote

The quote resource defines the basic information required for a Wise transfer - the currencies to send between, the amount to send and the profile who is sending the money.

Recipient

The recipient resource defines the information needed to create a transfer to the intended beneficiary - type of recipient, bank account information, contact details.

Transfer

The transfer resource defines a payment order to a selected recipient account based on a selected quote.

Fund

In order for transfers to complete, they must be funded after creation. Multiple methods of funding transfers exist depending on your integration method.

The Wise Platform API is continuously evolving as we offer new features and coverage to our API customers. Here we explain how our API versioning is maintained so you know what to expect.

It's important to us that third-party integrations are not adversely affected by changes and we endeavor to uphold these standards as part of making convenience and transparency part of our company's mission. We are regularly reviewing our policies to make sure we're delivering the best possible API developer experience.

These policies apply to both our REST API and our webhooks (push-based event API).

Sandbox https://api.sandbox.transferwise.tech

Production https://api.transferwise.com

A breaking change refers to any change that requires a client to update their application in order to continue working with the API as originally intended. If an API field or resource is removed or renamed, then a breaking change has taken place. In this case we will increment the version of the affected API endpoints to prevent breaking existing customer integrations.

Under our current policy, API endpoints are not all versioned together, if API endpoint compatibility has changed in the new version as a result of a breaking change we will provide clear instructions in our documentation on which API calls must be used together.