What this category of data includes
Data sources for this category include the China Government Procurement Network, local government procurement websites, fiscal integration systems, procurer budget systems, and supplier credit records. The update frequency is daily.
Daily covered documents span the full procurement workflow: procurement requirements, procurement plans, bidding documents, bid submissions, bid evaluation reports, winning bid announcements, procurement contracts, and responses to inquiries. Data structures are built around government procurement projects, including fields such as project ID, project name, regulatory body, executing body, and document association ID. Teams must adapt to specific data formats based on connected external systems. No unified standardized field template exists for this data.
Constraints imposed on HTTP interfaces and external systems
Interfaces using daily updated data sources must use scheduled pull tasks. Frequent API calls may exceed external system limits, so scheduled pulls prevent this issue.
Differences in data formats across multiple sources require interfaces to adapt to varied return structures. Teams must use the responseData parameter to flexibly extract corresponding fields.
The diversity of full-process documents requires interfaces to support filtering specific documents by project ID. This avoids returning irrelevant data.
The regulatory nature of government procurement projects requires interface calls to carry valid authentication information. This ensures compliant data access. Teams must also strictly control the accuracy of request parameters to prevent regulatory penalties from incorrect parameters.
How to configure settings
These configurations are designed for FastGPT v4.17.0.
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
Authorization | Bearer Token format, valid token obtained from the fiscal integration system | All external systems related to government procurement require identity authentication to prevent request interception |
| Request timeout | 30–60 seconds | Matches typical response duration of government procurement interfaces, avoids task blocking from prolonged waits |
responseData extraction rules | Extract announcement body and associated project fields from returned content, retain first 1000 characters | Aligns with core needs of policy Q&A, controls context length within FastGPT processing limits |
variables binding | Bind procurement project ID and regulatory department ID as context variables | Enables pulling targeted policy documents for specific projects, avoids returning full irrelevant data |
| Scheduled pull frequency | 1 time per day, executed at 2:00 AM daily | Matches daily update frequency of data sources, reduces request pressure on external systems |
| Number of entries per request | Top 200 entries | Controls single return data volume, avoids exceeding FastGPT processing thresholds |
Three common configuration errors
- Interface calls return the
403 Forbiddenerror. This occurs when theAuthorizationparameter is not configured correctly, an expired fiscal system authentication token is used, or valid authorization information is not included. - Policy documents returned after sending a request are empty. This occurs when the procurement project ID variable in
variablesis not bound correctly, leading to missing request parameters and inability to locate policy basis for the target project. - Scheduled pull tasks fail to execute. This occurs when a reasonable request timeout is not set, exceeding the response limit of government procurement interfaces and causing requests to be interrupted by external systems.
How to verify correct configuration
- Call the test interface, check that the returned
responseDataincludes expected government procurement policy document fragments, and that fields match the bound project variables. - Review FastGPT interface logs, confirm that the
Authorizationparameter is correctly included and follows the Bearer Token format specification. - Verify scheduled pull task execution records, confirm that daily 2:00 AM pull tasks complete successfully with no error messages.
- Send requests with different procurement project IDs, confirm that returned document content matches the policy basis of the corresponding project.
The values provided here are common starting points, and should be evaluated against the reader's own samples.
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-28.