Integrating tokenized asset data into the pricing engine: What can the API access, and how to integrate it?
Market makers do not manually monitor the market—market data, depth, and fees must be integrated into the system, to be automatically processed by the pricing engine. The key questions before integration are: Can the data be programmatically obtained? Are the fields sufficient for pricing? Are the latency and quotas acceptable? This article outlines the API integration path for tokenized asset sector data based on the actual needs of the market-making system. (Specific interface fields, quotas, and pricing are subject to the API documentation published on the day of release.) Market makers do not manually monitor the market—market data, depth, and fees must be integrated into the system, to be automatically processed by the pricing engine. The key questions before integration are: Can the data be programmatically obtained? Are the fields sufficient for pricing? Are the latency and quotas acceptable? This article outlines the API integration path for tokenized asset sector data based on the actual needs of the market-making system. (Specific interface fields, quotas, and pricing are subject to the API documentation published on the day of release.)
Who is this article suitable for?
- The market-making technical team that needs to integrate tokenized asset data into the pricing engine;
- The data product manager responsible for evaluating data procurement;
- The exchange technical team designing the liquidity monitoring system.
What three types of data does the market-making system need?
Market data: Prices, spreads, ±2% depth from various exchanges—real-time input for the pricing engine. The key metric is the update frequency: minute-level delays can generally meet the needs for low-frequency quotes, but may not meet the requirements for high-frequency quotes. It is recommended to test the delay before selection. The display format of the fields can be compared with QQQ detail page 's "Stock Contract Overview" to assess whether the granularity meets the pricing model.
Fee data: Funding rates, Maker/Taker fees, leverage parameters—directly related to the calculation of the net space for pricing. The frequency of changes in fee data is relatively low, but the accuracy requirement is high.
Structural data: Market share, OI, leaderboard rankings—used to monitor pattern changes and abnormal alerts. This type of data does not need to be real-time but should have a historical series; otherwise, trend judgments cannot be made. The rankings of stock derivatives exchanges and the rankings of stock spot exchanges 's public indicators can serve as a reference for the demand for structural data.
Integration path: Four steps
- Apply for a key: Start with the free basic version to verify whether the field completeness meets the requirements of the pricing engine;
- Field mapping: Map API fields to your internal data model—pay special attention to unifying the underlying ID, as the entity association of multiple issuer versions and multiple exchange contracts needs to be verified; the statistical caliber of each field can be found in tokenized asset methodology ;
- Dual-source verification: Before going live, cross-check the page data of tokenized asset dashboard with the API returns for a period to confirm consistency;
- Incremental upgrade: After field verification passes, evaluate the upgrade subscription tier based on call volume rather than the feature list.
Usage restrictions
- The number of API interfaces, quotas, rate limits, and pricing are subject to the current display on the official website; this article does not cite specific numbers;
- Data accessed for internal systems must comply with the usage scope agreements in the licensing terms; common questions regarding interfaces and fields can be found in tokenized asset FAQ .
Start verifying fields from the free quota
Go to the RootData API documentation to apply for a basic version key, and use it for a period to verify whether the three types of fields meet your pricing engine—after field matching, evaluate whether to upgrade the subscription.
