Market data
The TRON API does not serve market data. Quotes, candles, depth, tape, 24h stats, FX rates, the symbol catalog and the live streams come straight from Nuntius, the market-data service. This API only decides who may connect: it mints the access token Nuntius checks.
| You need | Where it comes from |
|---|---|
| Quotes, candles, depth, tape, stats, FX | Nuntius |
| Live streams (book, tape, quotes, bars) | Nuntius WebSocket gateway |
| Symbol catalog and symbol metadata | Nuntius |
| Live account equity and unrealized P&L | This API: /ws/risk Account-State-Update. GET /api/v1/accounts/{id}/state moves only on fills, adjustments and liquidations, not with price. |
| Orders and fills | This API |
Getting access
Section titled “Getting access”POST /api/market-feed/session returns a short-lived token and the gateway to
use it on. It resolves the tenant like every other call (an origin registered on
your tenant, or X-Tenant-Slug) and reads the caller from the browser cookie
session or a bearer.
curl -s -X POST "https://api.troncharts.xyz/api/market-feed/session" \ -H "authorization: Bearer $TOKEN" \ -H "x-tenant-slug: $TC_TENANT_SLUG"The response carries:
| Field | Meaning |
|---|---|
token |
The credential to present to the Nuntius gateway. |
expiresAt |
When the token stops working. |
refreshAfter |
When to ask for a new one. Refresh before expiresAt, not after. |
gateway |
Where to connect: the WebSocket url and the candle intervals on offer (candleIntervals). |
venues |
The venues your tenant’s market-data policy enables. |
lanes |
Per-lane settings for the connection. |
policy |
The access policy the token was minted under. |
Nuntius validates the token against this API’s public keys, published at
/api/.well-known/market-data-jwks.json. You do not call that endpoint
yourself.
Errors are { "error": "<code>" }: not_enabled and not_configured (404)
when the tenant has no market-data access, mint_unavailable and
market_feed_unavailable (503) when the token cannot be issued right now. The
response is never cached; retry a 503 with backoff.
What you subscribe to, and the frames you get back, are Nuntius’s interface. Market data feed walks through connecting, subscribing and the quote frames.
Symbols carry their venue
Section titled “Symbols carry their venue”BTC.HL, WINFUT.B3 — the suffix is how the platform resolves pricing, and it
is part of the symbol, not decoration. Take symbols from the Nuntius symbol
catalog and send them to this API exactly as listed, for example as symbol on
an order. On B3 the catalog lists the bare code (WINFUT): add .B3.
Moving off /api/v1/symbols
Section titled “Moving off /api/v1/symbols”GET /api/v1/symbols/{venue} has been removed and answers 404. Its tick
size, lot size, leverage cap, contract fields, market status and display
fields now come from the Nuntius symbol catalog
(GET /catalog/{venue}, with the same feed session token).
/api/v1/symbols |
/catalog/{venue} |
|---|---|
ticker |
symbol (on B3 without the .B3 suffix) |
decimals |
priceDecimals |
tick, qtyStep, maxLeverage, contractMultiplier, contractCode, marketStatus, reopenAt, name, exchange, assetClass, instrumentType, iconUrl |
same name |
dayChangePct, dayVolumeUsd, fundingRate, openInterest |
GET /stats/24h?venue={venue} |
What changes when you move:
- Hyperliquid and Lighter values follow the venue’s own rules. For some
symbols the catalog’s
tickorqtyStepdiffers from what/api/v1/symbolsanswered; the catalog is the one the venue accepts. - Hyperliquid event markets (
Yes/Nooutcome contracts) are not in the catalog. defaultTpPctanddefaultSlPctare TRON app defaults, not market metadata, and are not in the catalog.
P&L without a price feed
Section titled “P&L without a price feed”If you need a live P&L figure (a scoreboard, a leaderboard), do not rebuild it
from quotes. GET /api/v1/accounts/{id}/state returns, per venue, equityUsd
and unrealizedPnlUsd, computed by the same engine that decides margin and
liquidation, so your number matches the account’s. Use
/ws/risk if you want it pushed.
Custom indicators and backtests
Section titled “Custom indicators and backtests”If you compute studies server-side, GET /api/v1/indicators and
POST /api/v1/backtests/run evaluate declarative indicator specs against the
same candle data, so a study renders identically in your UI and in a backtest.