How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

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 48 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 8 schemas. It is described by OpenAPI 3.2.0.

Requests are made against 2 base URLs: https://api.wise.com, https://api.wise-sandbox.com.

15 operations 14 paths 8 schemas 9 GET5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
Base URL
https://api.wise.com/v2
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Basic
Resource Areas
1

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.

Transfer 15

A transfer is a payment order to a recipient account based on a quote.

POST
/v1/transfers
Create a transfer
transferCreate 1 param body → 200429
GET
/v1/transfers
List transfers
transferList 9 params → 200429
GET
/v1/transfers/{transferId}
Get a transfer by ID
transferGet 2 params → 200404429
PUT
/v1/transfers/{transferId}/cancel
Cancel a transfer
transferCancel 2 params → 200404409429
POST
/v1/transfer-requirements
Validate transfer requirements
transferRequirementsValidate 1 param body → 200429
POST
/v2/profiles/{profileId}/third-party-transfers
Create a third party transfer
transferThirdPartyCreate 2 params body → 200429
GET
/v1/profiles/{profileId}/third-party-transfers/{transferId}deprecated
Get a third party transfer by ID (V1)
transferThirdPartyGetV1 3 params → 200404429
GET
/v2/profiles/{profileId}/third-party-transfers/{transferId}
Get a third party transfer by ID
transferThirdPartyGet 3 params → 200404429
POST
/v3/profiles/{profileId}/transfers/{transferId}/payments
Fund a transfer
transferFund 3 params body → 200404429
GET
/v1/transfers/{transferId}/payments
List completed payments
transferPaymentsList 2 params → 200404429
GET
/v2/transfers/{transferId}/invoices/bankingpartner
Get payout information
transferPayoutInfoGet 2 params → 200404429
GET
/v1/transfers/{transferId}/receipt.pdf
Get a transfer receipt
transferReceiptGet 2 params → 200404429
GET
/v1/transfers/{transferId}/us-combined-receipt.pdf
Get a US combined disclosure receipt
transferUsCombinedReceiptGet 2 params → 200404429
GET
/v1/transfers/{transferId}/documents/noc
Get a non objection certificate (INR)
transferNocGet 2 params → 200404429
POST
/v1/profiles/{profileId}/partner-licence-transfersdeprecated
Create a partner licence transfer
transferPartnerLicenceCreate 2 params body → 200429

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are transfer (20 properties), originator-transfer (20 properties), payment (7 properties), v2.0.0-2 (5 properties). Each schema is shown below with its type and property counts.

v4.0.0
object
5 properties
payment
object
7 properties
v2.0.0
object
5 properties
originator-transfer
object
20 properties
transfer
object
20 properties
transfer-requirement
object
2 properties
v4.0.0-2
object
5 properties
v2.0.0-2
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

wise-transfer-api-openapi.yml Raw ↑

Other APIs Wise publishes across the network.

Wise Activity API
Wise Address API
Wise Balance API
Wise Balance Statement API
Wise Bank Account Details API
Wise Batch Group API
Wise Bulk Settlement API
Wise Card API
Wise Card Kiosk Collection API
Wise Card Order API
Wise Card Sensitive Details API
Wise Card Transaction API
Where this information came from

This is an independent, third-party profile of Wise Transfer API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.