Acquire a token granting you access to perform sensitive operations on behalf of an identity.
- Get all transfer transactions
Weavr Multi Product BackOffice API (v3)
Weavr Multi Back Office API allows you, as an innovator, to perform various back office operations concerning identities and their instruments, without requiring the users to be logged in.
A token is to be obtained through the access_token method, and this will allow relevant operations to be performed on behalf of this same identity.
Managed Accounts are a type of financial instrument offered by Weavr. They hold funds for their owner, and can be upgraded to IBANs so as to receive and send funds to instruments outside of the Weavr Platform, via Wire Transfers. These accounts can also be used as sources and destinations in the transfer transaction.
With the access_token representing the identity and the consent of the identity, you will be able to operations on the identity's managed accounts, such as getting a managed account's details and retrieving its statement.
Managed Cards are a type of financial instrument offered by Weavr. Cards created in prepaid mode have their own balance, whereas those created in debit mode tap into the balance of their parent Managed Accounts. Apart from being used at merchants for puchases, prepaid mode cards can also be used as sources and destinations in the transfer transaction.
With the access_token representing the identity and the consent of the identity, you will be able to perform operations on the identity's Managed Cards, such as getting a Managed Card's details and managing its spend rules.
Request
Transfers funds between managed accounts and managed cards belonging to the same corporate or consumer identity.
The Transfer Profile (configured in the Multi Portal) specified determines the behaviour and restrictions of the transaction (for example, fees).
The profile Id which a specific identity, instrument or transaction type is linked to.
Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.
You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.
Profile Ids can be found in the Multi Portal, in the API Credentials page.
The tag field is a custom field that can be used to search and filter.
The managed account or managed card from where the funds will be transferred.
The description details that are included in the transaction as reference.
The managed account or managed card to where the funds will be transferred.
The amount, in same currency as the source and destination instruments, to be transferred to the destination (exclusive of any fee amount that may be specified in the profile).
The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.
- Mock serverhttps://api.weavr.io/_mock/products/multi-backoffice/openapi/transfers
- Weavr Sandbox Environmenthttps://sandbox.weavr.io/multi/backoffice/transfers
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
https://api.weavr.io/_mock/products/multi-backoffice/openapi/transfers \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-H 'api-key: YOUR_API_KEY_HERE' \
-H 'idempotency-ref: string' \
-d '{
"profileId": "string",
"tag": "string",
"source": {
"id": "string",
"type": "managed_cards"
},
"description": "string",
"destination": {
"id": "string",
"type": "managed_cards"
},
"destinationAmount": {
"currency": "str",
"amount": 0
},
"scheduledTimestamp": "string"
}'Success
The profile Id which a specific identity, instrument or transaction type is linked to.
Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.
You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.
Profile Ids can be found in the Multi Portal, in the API Credentials page.
The tag field is a custom field that can be used to search and filter.
The source managed account or card from where the funds were transferred.
The destination managed account or card to where the funds were transferred.
The amount, in same currency as source and destination, that was transferred from the source to the destination instrument.
The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.
The description details that are included in the transaction as reference.
Status of the transaction.
The time when the transaction was created, expressed in Epoch timestamp using millisecond precision.
The epoch timestamp at which the transaction is scheduled to be executed.
The epoch timestamp at which the transaction was executed, transitioning to a final state such as COMPLETED, REJECTED, or FAILED.
{ "id": "string", "profileId": "string", "tag": "string", "source": { "id": "string", "type": "managed_cards" }, "destination": { "id": "string", "type": "managed_cards" }, "destinationAmount": { "currency": "str", "amount": 0 }, "description": "string", "state": "INITIALISED", "creationTimestamp": 0, "scheduledTimestamp": "string", "executionTimestamp": "string", "cancellationReason": "string" }
The offset value for paging, indicating the initial item number to be returned from the data set satisfying the given criteria. Leave out to fetch the first page of results.
The limit of the results for paging, starting at the offset. Limit is always capped at 100.
Filter by the transfer profile. Leave out to fetch all transfer transactions.
Filter by the transfer transaction state. Leave out to fetch all states.
Filter for transfer transactions created after createdFrom timestamp. Timestamp is expressed in Epoch timestamp using millisecond precision. Leave out to fetch all transfers.
Filter for transfer transactions created before createdTo timestamp. Timestamp is expressed in Epoch timestamp using millisecond precision. Leave out to fetch all transfers.
- Mock serverhttps://api.weavr.io/_mock/products/multi-backoffice/openapi/transfers
- Weavr Sandbox Environmenthttps://sandbox.weavr.io/multi/backoffice/transfers
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://api.weavr.io/_mock/products/multi-backoffice/openapi/transfers?offset=0&limit=1&profileId=string&id=string&type=managed_cards&state=INITIALISED&createdFrom=0&createdTo=0&tag=string' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'api-key: YOUR_API_KEY_HERE'{ "transfer": [ { … } ], "count": 0, "responseCount": 0 }
- Mock serverhttps://api.weavr.io/_mock/products/multi-backoffice/openapi/transfers/{id}
- Weavr Sandbox Environmenthttps://sandbox.weavr.io/multi/backoffice/transfers/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://api.weavr.io/_mock/products/multi-backoffice/openapi/transfers/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'api-key: YOUR_API_KEY_HERE'Success
The profile Id which a specific identity, instrument or transaction type is linked to.
Profiles contain configuration and determine behavioral aspects of the newly created transaction, for example, fees that may apply.
You can have one or more profiles linked to your application, and these can be used to drive different behaviors according to your product's needs.
Profile Ids can be found in the Multi Portal, in the API Credentials page.
The tag field is a custom field that can be used to search and filter.
The source managed account or card from where the funds were transferred.
The destination managed account or card to where the funds were transferred.
The amount, in same currency as source and destination, that was transferred from the source to the destination instrument.
The currency expressed in ISO-4217 code. Example: GBP, EUR, USD.
The description details that are included in the transaction as reference.
Status of the transaction.
The time when the transaction was created, expressed in Epoch timestamp using millisecond precision.
The epoch timestamp at which the transaction is scheduled to be executed.
The epoch timestamp at which the transaction was executed, transitioning to a final state such as COMPLETED, REJECTED, or FAILED.
{ "id": "string", "profileId": "string", "tag": "string", "source": { "id": "string", "type": "managed_cards" }, "destination": { "id": "string", "type": "managed_cards" }, "destinationAmount": { "currency": "str", "amount": 0 }, "description": "string", "state": "INITIALISED", "creationTimestamp": 0, "scheduledTimestamp": "string", "executionTimestamp": "string", "cancellationReason": "string" }