Wise transfer API
A transfer is a payment order to a [recipient account](/api-reference/recipient) based on a [quote](/api-reference/quote).Once created, a transfer usually needs to be funded within fourteen days. Otherwise, it will be automatically cancelled.There are 2 types of transfer resources: standard transfer resource and originator transfer resource. Please see below for differences between the two.Standard Transfer {% #standard-transfer .title-3 .m-t-5 %}The standard transfer object is returned by the [create transfer](/api-reference/transfer/transfercreate), [get transfer](/api-reference/transfer/transferget), [list transfers](/api-reference/transfer/transferlist), and [cancel transfer](/api-reference/transfer/transfercancel) endpoints.Originator Transfer {% #originator-transfer .title-3 .m-t-5 %}The originator transfer object is returned by the [create third party transfer](/api-reference/transfer/transferthirdpartycreate) and [get third party transfer](/api-reference/transfer/transferthirdpartyget) endpoints. It includes an additional `originator` data block with details about the payment originator.
Wise transfer API is one of 47 APIs that Wise publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
Tagged areas include transfer. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an AsyncAPI specification.
This API exposes 15 operations across 14 paths, and defines 4 schemas. It is described by OpenAPI 3.1.0.
Requests are made against 2 base URLs: https://api.wise.com, https://api.wise-sandbox.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
Wise transfer API declares
4 security schemes
for authenticating requests.
It accepts HTTP bearer tokens (JWT) (UserToken).
It accepts HTTP bearer tokens (JWT) (PersonalToken).
It accepts HTTP bearer tokens (JWT) (ClientCredentialsToken).
It accepts HTTP basic authentication (BasicAuth).
UserToken— User Access Token for making API calls on behalf of a Wise user. Can be obtained via two OAuth 2.0 flows: - registrationcode grant: For partners creating users…PersonalToken— Personal API Token for individual personal or small business users. Generated from Wise.com Settings Connect and manage apps API tokens. Has limited API access…ClientCredentialsToken— Application-level token for partner operations that don't require a specific user context, such as bulk settlement and card spend controls. Obtained via POST /…BasicAuth— Basic Authentication using your Client ID and Client Secret as the username and password. Client credentials are provided by Wise when your partnership begins.…
Paths & Operations 15
Across 14 paths, the API surfaces 15 operations — 9 GET, 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.
A transfer is a payment order to a [recipient account](/api-reference/recipient) based on a [quote](/api-reference/quote). Once created, a transfer usually needs to be funded with…
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are originator-transfer (20 properties), transfer (20 properties), payment (7 properties), transfer-requirement (2 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Wise 12
Other APIs Wise publishes across the network.