List your sub-accounts
Registry rows only, oldest first, so your default sub-account leads the list. Positions are on GET /partner/v1/positions, which needs a currency to be meaningful.
Registry rows only, oldest first, so your default sub-account leads the list. Positions are on GET /partner/v1/positions, which needs a currency to be meaningful.
Authorization
bearer In: header
Response Body
application/json
application/json
application/json
application/json
curl -X GET "https://example.com/api/partner/v1/sub-accounts"{ "data": [ { "createdAt": "2026-08-14T08:42:11.000Z", "externalRef": "acme-fund-002", "isDefault": false, "label": "Growth Fund II", "subAccountId": "5d3b8e10-2f47-4c9a-b6e8-0a71d4c2f395" } ], "success": true, "timestamp": "2026-09-02T10:15:30.000Z"}Your tcbUSD, decomposed by sub-account GET
The tcbUSD booked to each sub-account — held, reserved by steps in flight, and available — with the totals and the balance of the TCB wallet assigned to you. Your vault shares are on GET /positions.
Register a sub-account POST
Creates a named partition of your omnibus position. A sub-account is a partition of YOUR book: it confers no wallet, no key and no allowlist entry, and every share still sits in the one sub-account wallet TCB custodies for you. Use the returned subAccountId on deposits and withdrawals to attribute them; omit it and they land in your default sub-account.