Appearance
Wise
International money transfers, multi-currency accounts, and exchange rates via the Wise (TransferWise) API.
| Detail | Value |
|---|---|
| Category | Finance |
| Base URL | https://api.transferwise.com/v1 |
| Authentication | Bearer Token |
| Endpoints | 4 |
| Connector key | wise |
Using Wise in a workflow
- Go to Connections and click New Connection.
- Pick Wise from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET /v1/profiles | List user profiles |
POST /v1/quotes | Create a transfer quote |
POST /v1/transfers | Create a transfer |
GET /v1/transfers/{transferId} | Get transfer details |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET /v1/profiles
List user profiles
| Detail | Value |
|---|---|
| Operation ID | fintech.listProfiles |
| Method | GET |
| Path | /v1/profiles |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Wise connection from the Connection dropdown.
- In the Operation dropdown, select
fintech.listProfiles. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Wise API reference.
POST /v1/quotes
Create a transfer quote
| Detail | Value |
|---|---|
| Operation ID | fintech.createQuote |
| Method | POST |
| Path | /v1/quotes |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
sourceCurrency | string |
targetCurrency | string |
sourceAmount | number |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Wise connection from the Connection dropdown.
- In the Operation dropdown, select
fintech.createQuote. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Wise API reference.
POST /v1/transfers
Create a transfer
| Detail | Value |
|---|---|
| Operation ID | fintech.createTransfer |
| Method | POST |
| Path | /v1/transfers |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
targetAccount | integer |
quoteUuid | string |
customerTransactionId | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Wise connection from the Connection dropdown.
- In the Operation dropdown, select
fintech.createTransfer. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Wise API reference.
GET /v1/transfers/{transferId}
Get transfer details
| Detail | Value |
|---|---|
| Operation ID | fintech.getTransfer |
| Method | GET |
| Path | /v1/transfers/{transferId} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
transferId | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Wise connection from the Connection dropdown.
- In the Operation dropdown, select
fintech.getTransfer. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Wise API reference.