Can the perpetual contract leaderboard for exchange stocks be accessed through the API?
Sure. The Stock Contract Exchange Ranking (Pro) API of RootData is specifically designed for stock perpetual contract exchanges, returning the latest complete leaderboard snapshot. To turn it into a valuable product for users, the key is not just to display rankings, but to help users understand what the comprehensive score, liquidity, spread, fees, and contract coverage each mean.
First, explain to users the scope of the RootData leaderboard
This interface compares stock perpetual contract exchanges, not a unified ranking of traditional securities exchanges or tokenized stock spot markets, nor a safety or compliance ranking. The page should include "stock contracts," "snapshot time," and indicator criteria near the title to avoid users confusing different product structures.
What kind of leaderboard pages can the interface support
The fields listed in the RootData documentation include rank, exchange, score, contract_count, changes in OI and trading volume, weighted ±2% depth, spread, funding rate, Maker/Taker fees, collateral currency, and maximum leverage. The front end can use the comprehensive score as the default sorting, explain the execution environment using depth/spread, explain trading rules using fees and leverage, and support users in expanding to view each field.
Why should the content page also use RootData fields
Changes in leaderboard rankings alone do not provide sufficient explanatory power. The content should return to specific fields: is it an increase in the number of contracts, an improvement in depth, a change in spread, or a change in OI/trading volume? The value of RootData is to provide multi-dimensional market structure data, allowing the article to explain "why changes occur," rather than just repeating who ranks where.
Save version and time upon launch
The interface returns the latest complete batch. If trends are to be displayed or weekly reports created, snapshots should be regularly fetched and saved by the backend, retaining timestamps and original fields. The current documentation lists this capability as Pro, and there is a Credits consumption for each read; caching is part of the product design.
Frequently Asked Questions
Q: Can the leaderboard be filtered by exchange?
A: The leaderboard interface returns the current complete results, and the front end can filter the display based on the returned fields; specific calling methods are subject to the documentation.
Q: Does a higher ranking mean safer?
A: Not necessarily. This leaderboard measures specified market indicators and cannot replace safety, compliance, or solvency judgments.
Q: Why are rankings different on different dates?
A: The leaderboard is a data snapshot, and indicators will change with market conditions, coverage, and cost variations.
Understanding the RootData API
Related Reading
• How to access stock perpetual contract exchange leaderboard data?
• Which data in the tokenized asset dashboard can be accessed via API?



