What the data for this category looks like
Iron ore market data is primarily sourced from the official market API of the Dalian Commodity Exchange and daily settlement data from domestic spot trading platforms. Real-time incremental market data is pushed every 15 minutes during trading hours. A complete daily report document is generated after the daily market close. The document structure includes contract identifier, delivery standards, supply origin, daily transaction average price, daily highest and lowest prices, daily trading volume, and daily position volume. The units for transaction average price, highest and lowest prices are yuan per ton. The units for trading volume and position volume are trading lots.
Constraints on deployment and upgrade workflows
The high-frequency updates and fixed field format of iron ore market data impose clear constraints on deployment and upgrade processes. First, data sources rely on public network APIs, so proxy forwarding configuration is required for internal network deployments. Second, separate pull tasks are needed for real-time market data and daily full data, with scheduled intervals matching the exchange’s update rhythm. Third, fixed field structures require pre-configured field mapping rules during deployment to avoid missing fields after parsing. Fourth, interface parsing logic must be updated synchronously during version upgrades to prevent task failures caused by minor adjustments to the data source API format.
How to configure parameters
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
PARSE_FIELD_MAPPING | contract_code: Contract Code, avg_price: Average Transaction Price, trade_volume: Transaction Volume | Matches fixed field names in iron ore market report documents to avoid missing fields after knowledge base parsing |
CRON_JOB_INTERVAL | 15 minutes | Matches the Dalian Commodity Exchange’s 15-minute real-time market data update rhythm during trading hours |
DAILY_FETCH_TIME | 15:30 | Matches the typical time when the exchange generates complete daily market data |
UPLOAD_FILE_MAX_SIZE | 200 MB | Matches the typical maximum size of individual iron ore daily report documents |
PROXY_ENABLED | Enabled | Supports access to public network market APIs for internal network deployments |
API_REQUEST_TIMEOUT | 30 seconds | Matches typical response latency ranges for the exchange’s market APIs to avoid timeout interruptions |
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, so specific issues require specific analysis. It is recommended to test on your own samples before finalizing settings.
Three common configuration errors
- The
docker buildcommand returns the errorERROR: failed to solve: archive/tar: unknown file mod. The cause is incorrect permission mapping between the deployment server and data source configuration files, which prevents normal reading of configuration files during the build process. - A
404 - Resource Not Founderror is returned when calling the market data API. The cause is that the deployment server IP is not added to the whitelist of the Dalian Commodity Exchange market data API, or the configured contract identifier format does not meet the exchange’s requirements. - Some fields in iron ore daily reports are empty after upgrading to version 4.9.0. The cause is that the
PARSE_FIELD_MAPPINGconfiguration was not updated synchronously during the upgrade, and the new version’s parsing rules do not match the old field mapping.
How to verify correct configuration
- Manually trigger a real-time market data pull task, check that the returned dataset includes all preset fields, and that units conform to yuan per ton and trading lots.
- Test access to the Dalian Commodity Exchange market data API in an internal network deployment environment, confirm that the proxy configuration is active, and no connection timeout or rejection errors occur.
- After upgrading the version, compare the
PARSE_FIELD_MAPPINGconfiguration before and after the upgrade to confirm that the field mapping rules have not been modified unexpectedly. - View FastGPT task logs to confirm that all real-time market data pull tasks in the last 15 minutes have executed successfully, with no failed 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.