What this category's data looks like
Sources of Traditional Chinese Medicine (TCM) financial report data include official disclosure announcements from publicly listed TCM enterprises, industry operation data released by regulatory authorities, and public quotation data from specialized Chinese herbal medicine markets. Update cadences fall into two categories: fixed schedule and real time. Regular financial reports are updated quarterly and annually. Industry operation data is updated monthly. Market quotations are updated daily. Each financial report document includes modules such as enterprise operation data, production data, product revenue structure, and R&D investment details. Fields include production base area, decoction piece production capacity, single-item revenue, and R&D investment amount. Units are mu, ton, yuan, and ten thousand yuan respectively.
Constraints on HTTP interfaces and external systems
The multi-source and multi-update-frequency nature of TCM financial report data requires HTTP interfaces to support scheduled pull tasks configured by data source, and distinguish between full synchronization and incremental synchronization logic for fixed cycles. Non-standard financial unit fields such as mu and ton in production data require interfaces to support unit mapping configuration, to align with the default unit rules of external systems. Detailed production and R&D field requirements require interfaces to expose parameters for filtering by field dimension, to avoid returning redundant data. Different authentication requirements across multiple data sources require interfaces to support dynamic switching configuration for multiple API keys, to adapt to authentication rules of different data sources.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
SYNC_DATA_INTERVAL | 3600 seconds (full synchronization), 300 seconds (incremental synchronization) | Matches the update frequency of financial report data. Full synchronization covers quarterly and annual fixed disclosure cycles, while incremental synchronization adapts to real-time market data |
FIELD_UNIT_MAPPING | Enable unit mapping rules | Aligns non-standard financial units such as mu and ton in TCM financial reports with the unit system of external systems |
API_AUTH_TYPE | Multi-key dynamic authentication | Adapts to authentication requirements of different data sources. For example, exchange APIs use token authentication, while market APIs use signature authentication |
REQUEST_TIMEOUT | 600 seconds | Covers the longest response time for multi-source data aggregation, preventing timeouts caused by large data volumes |
BATCH_SYNC_SIZE | 100 items per batch | Balances interface load and synchronization efficiency, adapting to the return volume of single-batch financial report data |
FILTER_FIELD_LIST | production base area, decoction piece production capacity, single-item revenue | Select core fields as needed, reducing data processing pressure on external systems |
The parameter values provided on this page are common starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require targeted analysis. It is recommended to test on your own samples before finalizing settings.
Three common mistakes
- Phenomenon: When calling the financial report data interface, passing different
pageNumparameters returns exactly the same data set. Cause: The interface does not correctly implement pagination logic, and does not offset the query result set based on thepageNumparameter. - Phenomenon: When calling associated external data interfaces, the interface automatically shuts down and returns a
429 Too Many Requestsstatus code. Cause: The interface authentication configuration has expired, or concurrent requests exceed the call limit, triggering automatic rate limiting. - Phenomenon: The production base area field in TCM financial report data received by the external system displays abnormal values. Cause:
FIELD_UNIT_MAPPINGis not configured, and the interface directly returns raw unit data, which conflicts with the parsing rules of the external system.
How to confirm correct configuration
- Invoke the test interface with different
pageNumparameters, and verify that the offset of the returned result set aligns with expectations. - Check the field units returned by the interface to confirm alignment with the unit rules of external systems. This verification can be completed by comparing the original data and the field format of the returned data.
- Simulate calls to multiple data sources, confirm that the interface automatically switches authentication methods to complete requests, and verify there are no authentication failure logs.
- Review the running logs of scheduled synchronization tasks, confirm that synchronization actions are triggered at the configured interval, and verify there are no abnormal interruption records.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-09-14.