Skip to Content
Symmio Trading-SDK — the SDK surface for builders on Arbitrum
CorePoolsDetail tables

Pool detail tables

A pool’s detail view is five tables, and they do not come from one place. Three different backends fill them, and knowing which is which is what keeps a discrepancy between two tables from reading as a bug.

TableReadBackend
PositionsgetListingMarketDetail + toPoolPositionsListing backend
Open quotesgetPoolQuotesAnalytics subgraph
Limit orderssearchTpSlOrdersTP/SL handler
Trade historygetPoolTradeHistoryAnalytics subgraph
Deposits and withdrawalsgetPoolTransactionsListing backend

These reads are pool-wide, not account-scoped

This is the single most important thing about them. getPoolQuotes, getPoolTradeHistory, getPoolTransactions and the limit-order search all return every trader’s rows on the market — there is no partyA filter anywhere in them.

That is deliberate: a pool page shows the pool’s book, not the visitor’s. It has three consequences worth designing around.

  • No wallet is required. None of these reads needs a connected account, so the tables render for an anonymous visitor.
  • The account column matters. partyA / walletAddress differs row to row, so showing it is not decoration — without it the rows are ambiguous.
  • They are not the account-scoped reads. getQuoteHistory and getSubAccountQuotes answer “what does this account hold”; these answer “what is on this market”. Reaching for the wrong one gives an empty table or someone else’s data.

The subgraph reads scope by the pool’s symbolId and by source — the SYMMIO diamond the quotes were opened against, which is simply the chain’s symmioAddress. There is no separate address to configure.

An unlisted pool has no book

A pool that has not reached LISTED has no symbolId, and without one there is no solver market to query. getPoolQuotes and getPoolTradeHistory short-circuit to an empty result rather than issuing a request, and their query factories stay enabled: false.

getPoolTransactions is the exception: deposits and withdrawals exist from the moment a listing is applied for, so that table has rows well before the pool is tradable. It keys on the pool’s token address rather than a symbolId — pass tokenAddress to scope it to this pool, since with no filter it spans every pool.

Limit orders are not protocol LIMIT orders

The limit-orders table is filled by searchTpSlOrders with conditionalOrderType: TpSlSearchOrderType.SEND_QUOTE. A send_quote conditional order opens a quote when a trigger price is hit — a different mechanism from a protocol LIMIT order.

The distinction is load-bearing: the lowcap solver declares limitOrder: false, yet this table can still have rows. Do not gate it on the limitOrder capability.

Reads

Helpers

Pending orders and realized history values

getPoolQuotes returns pending-order orderPrice and orderNotional directly on each quote. Requested price takes precedence over opened price; explicitly supplied zero is retained. Missing inputs stay null.

getPoolTradeHistory returns closeQuantity, closePrice, tradeValue, openFee, closeFee, platformFee and realizedPnl directly on each event row. Monetary values are 18-decimal bigints or null when unavailable. Each row receives only its proportional opening-fee share, and liquidation rows have no closing fee. Normal, force, emergency and ADL closes retain their closing fees. Raw quote fee fields are rates; row fee fields are amounts.

import { getPoolQuotes, getPoolTradeHistory, type Config } from "@symmio/trading-core"; export async function detailTables(config: Config, symbolId: number) { const [{ quotes }, { rows }] = await Promise.all([ getPoolQuotes(config, { symbolId }), getPoolTradeHistory(config, { symbolId }), ]); return { pendingNotionals: quotes.map((quote) => quote.orderNotional), history: rows }; }

Wallet-filtered transaction views may require listing authentication at the application boundary even though the underlying pool transaction transport is public. Reuse the listing session, cancel old observers and discard completions after wallet/token/deployment switches.

There are no standalone detail selectors to compose after these reads. Withdrawal previews belong to the position projection. Chart range selection, running sums and deposit minimum/balance-delta estimates remain consumer-owned.

Further reading

Last updated on