List transfers
Cursor pagination, oldest-to-newest window given by from/to. Scoped the way GET /accounts is: transfers touching the ACTING node's own partitions. To read a movement between two of your sub-clients, act as one of them.
Cursor pagination, oldest-to-newest window given by from/to. Scoped the way GET /accounts is: transfers touching the ACTING node's own partitions. To read a movement between two of your sub-clients, act as one of them.
Authorization
bearer In: header
Query Parameters
Return only transfers touching this account, on either side.
Include transfers executed at or after this instant (ISO 8601).
date-timeInclude transfers executed at or before this instant (ISO 8601).
date-timeThe nextCursor from the previous page. Omit it for the first page. Treat it as opaque.
Rows per page, 1-100. Defaults to 25.
value <= 10025Header Parameters
Act on behalf of one of your sub-clients. The value is that sub-client id, and the request then reads and writes that sub-client's own accounts and registry rows rather than yours. Omit it to act as yourself. A route that does not accept the header refuses it with 400 ON_BEHALF_OF_NOT_ALLOWED_HERE rather than ignoring it — that includes every vault route (deposits, withdrawals, conversions, sub-accounts, positions), the webhook registry, and POST /sub-clients, since a sub-client never has sub-clients of its own. An id that is not one of your sub-clients answers 404 ON_BEHALF_OF_NOT_FOUND; a closed one answers 409 ON_BEHALF_OF_SUB_CLIENT_CLOSED; and a key restricted to a subset of your sub-clients answers 403 ON_BEHALF_OF_NOT_ALLOWED_FOR_KEY for any node outside it.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/partner/v1/transfers?accountId=7e2a0c53-4d81-49b6-8f37-1a5c9e0b2d74&from=2026-09-01T00%3A00%3A00.000Z&to=2026-09-30T23%3A59%3A59.000Z&cursor=f39b0c74-51ae-4d82-9b06-3c7e2a5d1f80&limit=25"{ "data": { "items": [ { "amount": "250.00", "currency": "USD", "disclosure": { "items": [ "ENVIRONMENT_IS_TESTNET: The environment is a testnet (Arbitrum Sepolia). No mainnet deployment exists.", "YIELD_IS_SIMULATED: The vault rate is set administratively and the interest it produces is minted as fresh underlying, not earned. It does not represent a return generated by deployed capital.", "FIAT_RAILS_ARE_MOCKED: No real fiat movement occurs. Balances are ledger entries against a sandbox provider.", "CONVERSION_RATES_ARE_MARKET_QUOTED_OR_REFUSED: A conversion is priced only by an external venue that quotes independently of TCB. When no such venue can price the pair, the conversion is refused rather than priced from an internal table. Read rate.pricingModel on every conversion: MARKET is a venue quote; any other value is not a market rate and must not be presented as one.", "CONTRACTS_ARE_UNAUDITED: No audit has been performed. Mainnet is gated on a two-firm audit that has not been commissioned.", "CUSTODY_IS_TCB_SUBACCOUNT: Everything held for the client — its vault shares, and the tcbUSD it holds between the steps of the tokenised deposit chain — is held in TCB custody, in the one TCB wallet assigned to the client. The client holds no keys and moves those tokens only through this API; each sub-account's shares and tcbUSD are book entries against what that wallet holds.", "INTEGRATION_AGREEMENT_ONLY: Fees as published on the rate card; no yield share, no return commitment." ], "summary": "This is a pilot integration on a testnet. Nothing in this system earns anything: the yield is simulated and the fiat rails are mocked.", "version": "2026-10-27" }, "executedAt": "2026-09-02T10:15:30.000Z", "from": { "accountId": "1b9d4f07-6c23-4a8e-b510-9f2c7d3e5a68", "ownerId": "3a7e5c91-0d24-4b6f-8e13-5c9a2f7b1d04", "ownerType": "CLIENT" }, "ownership": "SAME_OWNER", "reference": "Invoice 2026-0412", "replayed": false, "status": "COMPLETED", "to": { "accountId": "1b9d4f07-6c23-4a8e-b510-9f2c7d3e5a68", "ownerId": "3a7e5c91-0d24-4b6f-8e13-5c9a2f7b1d04", "ownerType": "CLIENT" }, "transferId": "0c93a6e1-58fb-4d27-9a04-7e1b3c5d8f26" } ], "nextCursor": "0c93a6e1-58fb-4d27-9a04-7e1b3c5d8f26" }, "success": true, "timestamp": "2026-09-02T10:15:30.000Z"}Return an account's IBAN POST
Every account receives on an IBAN from the moment it is opened, so this returns the account with its IBAN, issuing one only if the account somehow has none. Calling it again returns the same IBAN. The holder name is always the owner's verified legal name, never the account label.
Transfer within one tree POST
Both accounts must resolve under the caller's root client (own accounts or accounts of the caller's sub-clients). Same currency, instant, terminal on the response — no screening, no TCB limits, no approval. x-on-behalf-of narrows what may be named as fromAccountId to that sub-client's accounts; toAccountId may still be any account in the same tree. Idempotency key is MANDATORY.