What data for this category looks like
Data for this category primarily comes from the budget management integrated system, project declaration materials, fund payment data, business system ledgers, and satisfaction surveys. The update frequency is annual. Documents processed daily include performance target forms, self-assessment forms, performance evaluation reports, supporting material lists, and rectification reports. Fields involved include performance indicators, fund usage details, evaluation scores, and similar items. There is no fixed unified unit, and adjustments are made based on specific evaluation projects. Data is collected around the achievement of performance targets for fiscal fund use, serving annual evaluation work of finance bureau performance departments, budget units, third-party evaluation institutions, and competent departments.
What constraints these characteristics impose on the "HTTP APIs and External Systems" link
The annual update frequency means API call frequency should not be too high. A longer cache validity period can be configured. Multiple heterogeneous data sources require APIs to support authentication rules for different internal systems. Supporting material documents require APIs to support file upload and binary data transmission. Batch verification needs require APIs to support pagination queries or batch request parameters. For internal office scenarios, APIs must adapt to local area network access environments to avoid cross-domain or access permission issues. APIs must focus on performance-related data to match the business requirements of fiscal expenditure performance evaluation.
Reference only; verify against the target FastGPT release and deployment documentation.
How to configure settings
| Configuration Item | Recommended Approach | Rationale |
|---|---|---|
Authorization | Bearer ${internal_system_key} | Adapts to the standard authentication format for fiscal internal business systems, ensuring compliance with API access permission requirements |
variables | {"target_year": "current evaluation year", "dept_id": "budget unit code"} | Binds fixed query conditions for annual performance evaluations to accurately pull data for the corresponding batch |
responseData | Only retain performance indicator, fund payment record, and evaluation score fields | Filters redundant data to reduce resource consumption for API transmission and parsing |
| Timeout setting | 600 seconds | Adapts to the processing duration of batch verification and large file uploads to avoid request interruptions mid-process |
| File upload limit | Within 1000 MB | Matches the common storage size of performance evaluation supporting materials, covering most business scenarios |
| Retry mechanism | Calibrated based on actual testing | Addresses temporary fluctuations in internal systems to ensure stability of data pulling |
Three common configuration mistakes
- Symptom: An error
GET http://10.1.3.9:3000/login net::ERR_INCOMPoccurs when other devices on the local area network access the API, and the page fails to load. Cause: Cross-domain rules or port mapping for intranet access are not configured, preventing normal connection establishment within the internal network. - Symptom: An unsupported file format error is returned when calling the API to upload performance supporting materials. Cause: Allowed file types are not limited in the API configuration, or the document format required by the internal system is not supported.
- Symptom: A request frequency limit exceeded error occurs when calling the API with a single API key. Cause: Multi-key rotation rules are not configured, and the usage logic for different keys is not bound via the
variablesparameter, resulting in the single key’s request rate exceeding the limit.
How to confirm the configuration is correct
- Call the API to pull performance data for the corresponding batch, and check whether the returned fields match the preset core data scope.
- Upload supporting materials that meet the format requirements of the internal system, and confirm that the API can receive them normally and complete data submission.
- Test API access from multiple terminals on the local area network to confirm that all terminals can initiate requests normally.
- Simulate temporary fluctuations in the internal system, and check whether the API triggers the preset retry logic and resumes normal responses.
The values provided here are common starting points and should be measured 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.