Returns the detailed Trading Asset View: each returned currency is broken down across accessible DMA accounts or RapidX Portfolios, and then into the relevant wallet or venue detail.

Use this endpoint when a user needs to reconcile or display where a Trading currency is held. It is the allocation counterpart to Get Trading Asset Summary, which returns only one aggregate row per currency.

Rate limit: 10 requests per minute per API key.

API key access

This is a read-only LTP Open API endpoint. READ permission is sufficient; TRADE, TRANSFER and WITHDRAW are not required.

An unsupported API key level is rejected before asset data is read, normally with 2003. The required primeType selects the account family within the caller's permitted scope; it never expands that scope.

The literal word currency in the endpoint path is part of the route name, not a path parameter. Use the currency query parameter when filtering a currency symbol.

Query parameters

Response structure

data has page, pageSize, totalSize and list. Pagination applies to the outer currency list only. Amounts are decimal strings; identifiers are opaque strings. The hierarchy is:

currency (data.list[])
  └── account or Portfolio (list[])
        └── wallet or venue detail (details[])

Top-level response fields

Currency level

Each data.list[] item is the aggregate of one currency across the selected primeType.

Account or Portfolio level

Each nested list[] entry allocates the top-level currency to one account/Portfolio.

Wallet or venue detail

Each details[] item contains only the fields below. Account identity, name and note are provided by the parent account/Portfolio row.

equity appears only at the currency level. The detail rows do not repeat id, primeType, venue, accountName or accountNote.

Currency metadata

Important interpretation rules

• The account-level and detail-level rows are drill-downs of the top-level currency. Never add all three hierarchy levels together.
• For DMA, the account layer identifies an exchange and the final layer identifies a wallet. For RapidX, the Portfolio layer has no single venue and the final layer identifies the exchange.
• A successful result can contain a currency row with details = [] when dust filtering removes the detail rows. This is not a missing-data error.
• Use this endpoint for currency allocation. Use the Trading Account List or Trading Account Assets endpoint for an individual account total.

Available versus transferable amounts

available is the quantity usable for operations within the current account, such as placing spot orders. It does not necessarily equal the quantity that can be transferred out or withdrawn. The quantities may be equal in Funding, spot or unified accounts. For example, a unified account without open positions, open orders or other collateral requirements may have equal available and transferable quantities. Positions, open orders and collateral requirements can cause them to differ; the account mode alone does not determine whether they are equal. Aggregated available should not be assumed to equal the total transferable amount.

• DMA sub-accounts: query the exchange's native API for the transferable amount of the relevant asset and wallet, particularly for portfolio-margin and multi-currency margin accounts.
• RapidX Portfolios: use maxTransferable from Get Portfolio Asset Details, matching the asset and exchange. The API key selects the Portfolio: a Main User Level key queries the Main Portfolio; a dedicated Sub Portfolio key queries its own Portfolio. Sub-user Level keys cannot call that endpoint.

Get All Portfolio Assets also returns maxTransferable for a cross-Portfolio view and requires a Main User Level API key. These RapidX endpoints remain supported alongside Account Assets V2.

The transferable amount is determined at query time; the transfer request is checked again when processed.

Relevant errors