Changelog

Deprecated: use GET /v3/wallet/transaction, which pages with a cursor.

Returns the movements of the authenticated user's wallet, newest first, paged with offset and limit, together with the total number of transactions that match the filters.

All filters are optional and combine with AND. Each item has the shape of GET /v1/wallet/transaction/{id} without the details: the fees, the user's note and the amounts valued in another currency are only returned there.

Buys, sells and swaps appear only once they are completed, and a transfer between two different users appears as a withdrawal to the sender and as a deposit to the receiver.

Retrieves aggregated summaries of earn movements grouped by currency for a specific movement type (deposit, reward, withdrawal, discount-funds, or discount-rewards). Returns totals in the original currency and converted to the user's preferred currency. For reward type, use new endpoint /v1/earn/movements/reward/summary.

This endpoint is deprecated. Use GET /v2/account/employment-status instead, which returns translation keys instead of pre-translated text.

This endpoint is deprecated. Use GET /v2/account/funds-origin instead, which returns translation keys instead of pre-translated text.

This endpoint is deprecated. Use GET /v2/account/professions instead, which returns translation keys instead of pre-translated text.

This endpoint is deprecated. Use GET /v2/account/purposes instead, which returns translation keys instead of pre-translated text.

This endpoint is deprecated. Use GET /v3/account/address instead, which returns addresses with sensitive data masked except for the country code.

Deprecated — use GET /v1/verifier/verify/identity/verification/retry instead.

Retries the identity verification process for the authenticated user.

Deprecated — use POST /v3/verifier/identity-verification/init instead.

Initiates the identity verification process for the authenticated user. Returns a redirect URL or token for the identity provider flow.

Deprecated — use POST /v2/blockchain-manager/travel-rule-order/{orderId} instead.

Submits the travel-rule information of a crypto order of the authenticated user: who the counterparty is and what kind of wallet they use. For a deposit that is who sent the funds, and for a withdrawal who receives them. This version also accepts the counterparty's identity document, full postal address, place of birth and date of birth.

When walletOwnership is other, the counterparty must be identified with either document and address, or placeOfBirth and dateOfBirth.

Deprecated — use POST /v1/teller/iban/validate instead. Removal planned for 2027-04-05.

Deprecated — use the address-book confirmation flow instead (POST /v1/compliance/address-book/{addressBookId}/confirm).

Returns whether a crypto destination address linked to a wallet movement has been verified, along with the address details and verification timestamp.

Deprecated — use POST /v1/compliance/address-book/{addressBookId}/confirm instead.

Confirms a crypto destination address linked to a wallet movement, for subaccounts that cannot receive the email-based confirmation. TOTP is sent via the x-totp header; only gauth is supported.

Deprecated — use POST /v2/social-pay/order instead. Creates a new social payment order. The recipient is identified by email, phone, or alias depending on the type field. The amount is debited from the sender's pocket.

This endpoint requires two-factor authentication — the TOTP code is sent via the x-totp and x-totp-type headers. When TOTP is missing, this version maps the upstream HTTP 428 to HTTP 420 so existing clients keep the legacy contract. TOTP mismatch also returns HTTP 420.

Deprecated. Fetch rates from GET /v1/currency/rate or GET /v1/currency/prices and convert locally instead.

Converts one or more amounts into the to currency, each at its own point in time. value and time must have the same number of entries. from either has that same number of entries, or a single symbol that then applies to every amount.

The result is an array of numbers in request order. A position whose from symbol is unknown, or for which no rate exists at that time, comes back as 0 rather than as an error, so check for zeros before trusting a result.

No authentication is required.