ArticleAPI

How to access RootData stock perpetual contract exchange ranking data?

RRootData Editorial Team
Published 5 minUpdated

The trading volume of stock perpetual contracts cannot independently indicate the trading experience. The RootData API provides the stock contract exchange leaderboard as a Pro feature, and the interface returns a complete snapshot of the current leaderboard, suitable for exchange comparisons, research pages, and data products, but should not be packaged as profit or safety recommendations.

RootData What does the leaderboard API specifically provide?

The API documentation for the Stock Contract Exchange Ranking (Pro) interface is /open/stock_leaderboard, which reads the latest complete leaderboard each time. The returned fields include rank, exchange, overall score, number of valid contracts, 24-hour open interest/trading volume change, weighted ±2% depth, volume-weighted price spread, funding rate, Maker/Taker fees, margin currency, and maximum leverage. It places activity, liquidity, and costs within the same comparative framework, rather than just listing trading volume.

How to translate the fields into user-understandable comparisons

The overall score is used for ranking entry; contract_count indicates coverage; weighted_depth_2pct_usd and spread_pct are used to observe execution conditions; OI and trading volume changes reflect short-term variations; fees, margin, and maximum leverage affect trading rules. Each field answers different questions, and the page should display them separately to avoid implying that "the top rank is the best for all users."

RootData What product modules is the data suitable for

A four-layer module can be established: "Leaderboard table + Exchange details drawer + Indicator explanation + Snapshot time." For research tools, daily leaderboard snapshots can be saved to observe changes in depth, spreads, and OI; for media or content products, changes in the leaderboard should be interpreted as market structure signals rather than trading conclusions.

Three things to verify before product launch

Confirm that the API Key is Pro, confirm Credits consumption and polling frequency, and confirm the update time displayed on the front end. The interface documentation states that this API costs 20 Credits per call, so it is not advisable to connect directly to the API with every user refresh; it is more suitable for the backend to fetch and cache periodically.

Frequently Asked Questions

Q: Does the leaderboard only look at trading volume?

A: No. This interface also returns fields such as depth, spreads, OI changes, fees, and contract coverage.

Q: Can the results be used as trading recommendations?

A: No. The leaderboard reflects comparisons of specified data within a time window and does not constitute investment or trading advice.

Q: Why is it necessary to save historical snapshots?

A: The leaderboard reads the latest complete results; if trend analysis is needed, the product should retain historical data itself.


Understand RootData API

View API documentation

Related Reading

• Can the perpetual contract leaderboard for exchange stocks be accessed via API?

• Which data in the tokenized asset dashboard can 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