HTTP Interfaces and External Systems for Securities

What the Data for This Category Looks Like

Data for securities financial reports comes from public periodic reports and temporary announcements disclosed by the Shanghai, Shenzhen, and Beijing Stock Exchanges. Updates follow fixed disclosure windows after quarter-end and year-end, while temporary announcements update when corresponding events occur. Document structures include structured financial statements, accounting policy explanations, and management discussion and analysis modules. Fields include security code, reporting period, operating revenue, attributable parent company net profit, earnings per share, and more. Units are mostly Renminbi yuan or ten thousand yuan, and some fields must comply with CSRC public disclosure regulations.

Constraints Imposed on HTTP Interfaces and External Systems

Securities financial report documents have large individual volume, numerous structured fields, and strict format specifications. This requires HTTP request response size and timeout settings to adapt to long content parsing and field validation. There is high demand for batch data pulling during disclosure windows, so concurrent request volume must be controlled to avoid triggering upstream interface rate limits. Incremental updates for temporary announcements require interfaces to support incremental pulling by reporting period or announcement ID. Some data source interfaces experience temporary fluctuations, so a reasonable retry mechanism must be configured.

Configuration Settings

Configuration Item	Recommended Value	Rationale
`HTTP_REQUEST_TIMEOUT`	`600 seconds`	Single securities financial report document takes a long time to parse, must adapt to response cycles for long-content requests
`MAX_RESPONSE_SIZE`	`10 MB`	Structured data and attachments for a single annual financial report can reach this upper limit, preventing request truncation
`UPSTREAM_HOST_WHITELIST`	`Add exchange data source IP ranges`	Complies with access permission verification rules of data source interfaces, avoids errors caused by disallowed host connections
`BATCH_REQUEST_LIMIT`	`5 per request`	Prevents triggering upstream interface rate limits during disclosure windows, ensuring successful batch pulling
`FIELD_STRICT_VALIDATION`	`Enabled`	Securities financial report fields must comply with CSRC disclosure specifications; validating field legitimacy reduces invalid data
`RETRY_STRATEGY`	`Retry 2 times on failure, 30-second interval`	Adapts to temporary fluctuations in data source interfaces, improving request success rate

The parameter values provided on this page are common starting points for configuration. Actual values are affected by material format, data volume, and business rules. Specific issues require individual analysis, and it is recommended to test against your own samples before finalizing settings.

Three Common Errors

Phenomenon: A Host 'xxx.xxx.xxx.xxx' is not allowed to connect error is returned after calling the HTTP interface, with a 403 status code. Cause: The IP address of the data source server has not been added to the UPSTREAM_HOST_WHITELIST configuration item.
Phenomenon: In version 4.9.0, the Chat model works normally, but the Embedding model cannot connect to OneAPI, and OneAPI returns a corresponding error. Cause: The upstream address and authentication parameters for the Embedding interface have not been configured separately, and the configuration from the Chat model is reused.
Phenomenon: No results are returned after initiating a financial report pulling request, or the request is interrupted early. Cause: The HTTP_REQUEST_TIMEOUT configuration has not been adjusted, and the default timeout period is insufficient to complete long document parsing.

How to Confirm Proper Configuration

Call the test interface to pull single-quarter public financial report data, check that the returned fields include required items such as security code, reporting period, and operating revenue.
Initiate no more than 5 batch pulling requests, confirm that all returned status codes are 200, and no rate limit prompts are triggered.
Initiate a request using an IP address that is not in the whitelist, confirm that a 403 Forbidden error is returned, verifying that the whitelist configuration is effective.
Adjust HTTP_REQUEST_TIMEOUT to 600 seconds, then initiate an annual financial report parsing request, confirm that the request is not interrupted early.

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.