文章API

Which data in the tokenized asset dashboard can be accessed through the RootData API?

RRootData 编辑部
發布於 5 min更新於

The tokenized asset dashboard cannot only display "price fluctuations." The same stock or ETF may simultaneously exist on-chain with different issuers, different chains, and centralized exchange contracts; the RootData API's tokenized stock interface places these records within the same query framework, facilitating product comparison across market coverage, liquidity, and issuance dimensions.

RootData Coverage of Tokenized Stock Interface

The Get Tokenized Stock Quotes (Pro) API in the documentation is /open/tokenized_markets, which allows querying on-chain and centralized exchange records of tokenized stocks. It supports filtering by underlying_symbol, underlying_entity_id, market_segment, issuer, exchange, chain, and contract address; this means that products can build dashboards around an underlying asset, an issuer, or a trading market, rather than just displaying by token name.

Which fields can constitute cross-market comparisons

The returned data includes instrument_id, product_id, underlying asset, issuer, market segment, trading venue, chain, price and type, 24-hour change, trading volume, OI, funding rate, spread, depth, fees, leverage, issuance volume, AUM, collection time, and data_status. The supply and AUM metrics of CEX records differ from those of on-chain issuance records and cannot be simply added together.

How to avoid erroneous aggregation of products

The documentation clearly states: global_product AUM should be counted only once per product_id; only when there is no global total should independent per_chain contributions be considered. The page needs to display AUM scope, data status, and collection time simultaneously, and distinguish between "no data," "partial data," and "expired data."

Expanding from market pages to research pages

Combining tokenized asset market data with RootData's stock contract exchange rankings, project information, and market snapshots can help users understand where a particular asset has records across issuers, chains, or CEXs, as well as where liquidity and price discovery occur. However, it does not imply that users have rights to the underlying securities, nor does it constitute any investment advice.

Frequently Asked Questions

Q: Can on-chain issuance and CEX contracts directly merge trading volumes?

A: Market segments, field metrics, and time windows should be confirmed first; it is not advisable to assume they can be simply added together.


Q: Why is AUM sometimes empty?

A: Some records or CEX records may not apply or have not verified that field; it should be understood in conjunction with data_status and scope fields.


Q: Can I query by codes like NVDA?

A: The interface supports filtering by underlying asset codes; specific parameters are subject to the current documentation.


Understanding RootData API

View API Documentation

Related Reading

• How to access stock perpetual contract exchange ranking data?

• Can the stock perpetual contract rankings of exchanges be accessed via API?

相關推薦

API文章

錢包如何自動補全代幣背後的項目背景?

錢包用戶看到一個代幣時,通常還需要知道它對應什麼項目、團隊是誰、是否有融資或即將發生的事件。RootData API 可將項目、人物、融資、日曆和資訊等結構化資料補到資產頁,讓錢包從“餘額與價格介面”延伸為可核驗的信息入口。

RRootData 编辑部
5 分鐘
API文章

Web3 數據 API 如何選:自建、採購還是組合?

自建與採購並不是非此即彼。對 Web3 產品而言,真正需要決定的是哪些數據必須由自己採集和定義,哪些結構化基礎資料更適合直接接入。RootData API 將項目、融資、投資者、人物、標籤、生態、日曆、榜單和代幣化市場數據組織成可調用能力,可減少實體清洗和關係維護的重複投入。

RRootData 编辑部
5 分鐘