ArticleAPI

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

RRootData Editorial Team
Published 5 minUpdated

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?

Related content

APIArticle

How does the wallet automatically complete the project background behind tokens?

When wallet users view a token, they usually also need to know which project it corresponds to, who the team members are, whether it has secured funding, or if there are upcoming events. The RootData API can supplement structured data such as projects, individuals, funding rounds, calendars and news to the asset page, enabling wallets to evolve from a "balance and price interface" into a verifiable information portal.

RRootData Editorial Team
5 min
APIArticle

How to choose a Web3 data API: Build, buy, or combine?

Building in-house and procurement are not mutually exclusive. For Web3 products, the real decision is which data must be collected and defined internally, and which structured foundational data is more suitable for direct integration. The RootData API organizes project, financing, investor, person, tag, ecosystem, calendar, leaderboard, and tokenized market data into callable capabilities, reducing the repetitive investment in entity cleaning and relationship maintenance.

RRootData Editorial Team
5 min
APIArticle

When displaying RootData API data to end users, what should be confirmed regarding authorization and signatures?

Displaying API data on web pages, wallets, exchanges, or AI responses is just the first step in technical connectivity. The product also needs to confirm the display range of fields, update and caching rules, source identification, redistribution permissions, and the visible boundaries of user responsibilities, to avoid misunderstanding "can be called" as "can be used freely."

RRootData Editorial Team
5 min
APIArticle

Is the free quota sufficient for testing the RootData API? How can I estimate the usage in a production environment?

The Basic plan of the RootData API currently provides 1,000 Credits per month and a limit of 60 requests per minute, which is sufficient for small-scale field, coverage, and product experience validation; however, it cannot replace production usage assessment. What really needs to be tested is: which RootData data objects are called each time your page or Agent completes a user task.

RRootData Editorial Team
5 min