What the data for this category looks like
Coke-related due diligence data is mainly sourced from domestic bulk commodity spot trading platforms, coastal port supervision systems, and public reports released by the China Coking Industry Association. Update frequencies follow multiple tiers: spot transaction prices are updated daily, port coke inventory levels are updated weekly, and industry supply and demand analysis reports are released every ten days. Most documents are in structured table format, with fields including origin name, coke specification parameters, today's transaction price, weekly average price, port inventory, cross-regional transportation mileage, and more. Transaction price units are yuan/ton, inventory units are ten thousand tons, ash content and volatile matter in specification parameters are measured as mass percentage values, and transportation mileage units are kilometers.
Constraints imposed on HTTP interfaces and external systems
The multi-source, heterogeneous nature of coke due diligence data creates multiple constraints for HTTP interface and external system integration. Different data sources have large differences in update frequencies. Interfaces must support custom pull intervals to adapt to daily spot price updates and weekly port inventory updates, avoiding invalid requests or data lag. Structured fields include multiple detailed specification parameters and various units. Interfaces must include built-in field mapping and unit conversion logic to meet the field naming and format requirements of external systems. Bulk data such as port inventory has a large volume. Interfaces must support pagination pull parameters to prevent single request timeouts or rate limit triggers.
How to configure settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
API_REQUEST_TIMEOUT | 600 seconds | Bulk coke inventory data pulling takes a long time; the default 300 seconds cannot cover full requests |
DATA_PULL_CYCLE | Set to 86400 seconds for spot data sources, 604800 seconds for port data sources | Matches the actual update rhythm of daily spot price updates and weekly port inventory updates |
FIELD_MAPPING_RULE | Configure in the format "external field:data source field", for example ton_price:spot_price | Adapts to external system field naming conventions and avoids field mismatch errors |
UNIT_CONVERSION_SWITCH | Enabled | Coke data includes multiple units such as yuan/ton and ten thousand tons, which need to be converted to the unified format required by external systems |
PAGE_SIZE | 100 | Balances request efficiency and data volume, preventing triggering rate limits due to overly large single requests |
UPLOAD_FILE_MAX_SIZE | 1000 MB | Adapts to the conventional file size of coke due diligence reports, avoiding triggering size limits during upload |
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 specific analysis, and it is recommended to test on your own samples before finalizing settings.
Three common mistakes
- Phenomenon: When calling the create file collection interface to upload a coke due diligence CSV file, a
field format mismatcherror is returned, and upload cannot be completed. Cause: TheFIELD_MAPPING_RULEwas not configured to adapt to the column names of the CSV file, so the interface cannot recognize the coke data fields in the file. - Phenomenon: When pulling bulk port inventory data, the interface returns a
504 Gateway Timeoutstatus code. Cause: TheAPI_REQUEST_TIMEOUTwas not configured with a sufficiently long duration, which cannot cover the pulling time of full bulk data sets. - Phenomenon: The ash content parameter field in the data received by the external system is empty. Cause: Full field return was not enabled in the interface configuration, and fine-grained specification parameter fields were cropped by default, resulting in missing key data.
How to confirm proper configuration
- Call the test interface to pull a single spot price data entry, check whether the returned fields match the configured
FIELD_MAPPING_RULE, and whether the units meet the requirements of the external system. - Upload a single coke due diligence CSV file, check whether the file collection is created successfully, and whether the fields are fully mapped to the external system format.
- Initiate a bulk port inventory data pull request, check whether the interface returns the expected status code, with no timeout or rate limit errors.
- View the running logs of the scheduled pull task, confirm that the pull time interval matches the configured
DATA_PULL_CYCLE.
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.