What this category's data looks like
Steam coal market data primarily comes from domestic coal spot trading markets, industry monitoring institutions, and futures exchanges. Spot data updates on a natural day basis, while active futures contract data refreshes every 15 minutes. Data is output in a structured format, including fields such as trading market, statistical time, transaction average price, highest transaction price, lowest transaction price, daily trading volume, origin listed price, port pickup price, and more. The unit is uniformly yuan/ton. Fields vary across different trading scenarios: port data includes indicators related to loading and unloading efficiency, while origin data includes mine inventory indicators.
Constraints imposed on the "sharing and embedding" workflow
The multi-scenario update cadence, differentiated field structure, and multi-market nature of steam coal data impose clear constraints on the sharing and embedding process. First, scenarios with different update frequencies require matching caching strategies to avoid data lag or resource waste. Second, the multi-field structure requires embedding configurations to support custom filtering, preventing redundant data from being returned and harming display effects. Third, the multi-market nature requires sharing links to carry market parameters, ensuring that embedded content displays accurate data for the target scenario. Finally, data compliance requirements mandate attaching source identifiers to ensure data credibility.
How to set configurations
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
shareCacheTTL | Spot scenario: 86400 seconds, Futures scenario: 900 seconds | Matches the update cadence of steam coal spot data (daily updates) and futures data (15-minute updates), avoiding cache expiration or data lag |
shareCustomFields | ["Trading Market","Statistical Time","Transaction Average Price","Highest Transaction Price","Lowest Transaction Price","Trading Volume"] | Covers core steam coal data indicators, filters redundant fields, and simplifies embedded display content |
shareAuthMode | userToken | Supports binding user identifiers, meets user traceability requirements for non-login windows, and allows configuration of authorization validity periods |
embedComponentWidth | 300–1200 pixels | Adapts to container sizes across different scenarios, preventing display overflow or layout chaos |
shareDataAppendSource | Enabled | Complies with compliance requirements for steam coal market data display, improving data credibility |
apiRequestTimeout | 10 seconds | Matches the average response time of steam coal data interfaces, avoiding embedded page loading timeouts |
The parameter values provided on this page are common starting points for configuration setup. Actual values are affected by material form, data volume, and business rules. Specific issues require case-by-case analysis, and testing against local samples prior to finalization is recommended.
Three common configuration mistakes
- After embedding a non-login sharing window, the user identifier required to call the MCP Server cannot be obtained.
shareAuthModeis not configured asuserToken, and user identifier passthrough is not enabled. - The steam coal data displayed on the embedded page deviates from real-time market data by more than 1 hour.
shareCacheTTLis set to an excessively long duration, and caching requirements for spot and futures scenarios are not differentiated. - A 404 error is returned when calling the share generation interface in a workflow. The version used is lower than v4.9.7, or the share link auto-generation function is not enabled in application settings.
How to verify correct configuration
- Open the configured sharing link, check if the page includes data source identifiers, and verify that the returned fields match the configuration of
shareCustomFields. - Switch the market parameter in the sharing link, confirm that the embedded page displays steam coal data corresponding to the selected trading scenario.
- Simulate non-login access to the sharing link, check if the request header carries a user identifier parameter, and verify that the MCP Server can normally obtain this identifier.
- Call the share generation interface in a workflow, confirm that the returned URL format is correct and can normally access the corresponding data.
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.