HTTP Interfaces and External Systems for Coke Yield Rates

Coke market and yield rate data comes from the Dalian Commodity Exchange official market interface and compliant bulk commodity data aggregation

What the data for this category looks like

Coke market and yield rate data comes from the Dalian Commodity Exchange official market interface and compliant bulk commodity data aggregation interfaces. Real-time intraday market data is pushed every 10 seconds. Daily yield rate reports are finalized by 17:00 on each trading day. Data uses a standardized JSON array format. Each element contains fields including contract identifier, trading date, opening price, closing price, settlement price, daily yield change, and total open positions. Price fields use yuan/ton as their unit, position volume uses lots, and yield change uses basis points.

Constraints on HTTP Interfaces and External Systems

Data sources must comply with the authentication rules of compliant interfaces. HTTP requests must carry signature parameters and identity identifiers. Intraday data updates at a high frequency. The interval of HTTP polling requests must match the 10-second push cycle to avoid exceeding interface rate limits. Daily yield rate reports have a fixed generation window. Scheduled tasks for external systems must be calibrated to trigger after 17:00 on trading days to avoid fetching ungenerated empty data. The unique attributes of fields and units require external system parsing logic to bind corresponding mappings, to avoid confusion with data from other bulk commodity categories.

How to Configure Settings

Configuration ItemRecommended ValueRationale
REQUEST_INTERVAL_SECONDS5-10 secondsMatches the 10-second intraday data update frequency to avoid triggering interface rate limits
TIMEOUT_THRESHOLD8 secondsMatches the average interface response time to avoid interrupting valid requests due to timeout
SCHEDULE_TRIGGER_TIME17:00 on trading daysMatches the completion time of daily yield rate reports to ensure complete data is fetched
RESPONSE_PARSE_MODEStrict field matchingAdapts to the standardized JSON structure to avoid parsing failures caused by field order or new fields
AUTH_SIGN_ALGORITHMHMAC-SHA256Complies with the authentication requirements of exchange interfaces to ensure request legitimacy

The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require case-by-case analysis, and testing on independent samples is recommended before finalizing configuration values.

Three Common Errors

  • A 200 status code is returned after calling the HTTP interface, but no yield-related fields are present in the response body. This occurs when the required contract_code parameter is not included as specified by the interface, resulting in empty returned data.
  • Empty daily report data is obtained after a scheduled task triggers. This happens when the scheduled task trigger time is earlier than 17:00 on the trading day, before the daily yield rate report has been completed.
  • Type errors occur when parsing response data, making it impossible to correctly map position volume values. This is caused by failing to set the lot unit conversion logic for the coke category's position_volume field, leading to exceptions when calculating values using unit rules from other commodity categories.

How to Verify Proper Configuration

  • Initiate a single HTTP request, and confirm the response body includes coke-specific fields such as trade_date and closing_price.
  • Configure a polling task, initiate multiple consecutive requests, and verify all response status codes are 200 with no duplicate or redundant data.
  • Wait until after 17:00 on a trading day to trigger a scheduled task, and confirm the obtained daily report data is not empty.
  • Parse the response data, and confirm the unit mapping of the position_volume field matches the lot rules for the coke category.

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.