What This Type of Data Looks Like
Data related to power grid equipment yield is primarily sourced from provincial power trading settlement systems and equipment operation and maintenance management platforms. The data update rhythm consists of a full daily summary completed at 2 AM daily for the previous day, plus hourly incremental operation data synchronization. This documentation uses structured JSON format. A single data entry includes fields such as unique device identifier, associated substation name, daily per-unit power generation revenue, daily total revenue, and daily equivalent utilization hours. The units for these fields are string, string, yuan/kWh, yuan, and hour respectively; no percentage-based statistical units are used.
Constraints Imposed on HTTP Interfaces and External Systems
Dedicated interfaces from power trading systems require strict identity verification, so integration must adapt to dedicated identity verification rules. The mixed incremental and full update rhythm requires interfaces to support resumable uploads and incremental pull parameters, to avoid duplicate synchronization or missed data. Structured fields and fixed units require enabling strict field validation in interface configurations, to ensure returned data exactly matches the preset structure. The large single return volume for bulk device data requires adapting pagination query parameters, to prevent interface timeouts.
Recommended Configuration Settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
incremental_sync_interval | 3600 seconds | Matches the hourly incremental update rhythm of power grid equipment data |
full_sync_cron | 0 2 * | Corresponds to the daily full data update task at 2 AM |
response_page_size | 100 entries | Adapts the volume of device data returned per interface call to avoid timeouts |
field_validate_mode | strict | Ensures returned fields exactly match the preset structure of power grid equipment data |
auth_type | API_KEY | Adapts to the identity verification requirements of dedicated power system interfaces |
request_timeout | 120 seconds | Accommodates interface response times for large power grid equipment datasets |
The parameter values provided on this page are standard starting points for configuration. Actual values may vary based on data volume, business rules, and deployment context. It is recommended to test using internal samples before finalizing setup.
Three Common Mistakes
- Phenomenon: When calling the interface to generate yield reporting content, the revenue data of the subsequent device overlaps with that of the previous device. Cause: The
incremental_sync_thresholdparameter is not configured, causing the incremental data returned by the interface to not filter already synced device identifiers, resulting in data interference. - Phenomenon: When receiving power grid equipment data via webhook, table-formatted fields cannot be parsed correctly. Cause: The
response_parse_modeparameter is not set tostructured_json; the default parsing mode cannot adapt to structured power grid equipment data documents. - Phenomenon: A 403 status code is returned when debugging the interface locally. Cause: API_KEY type identity verification is not used, and a generic token configuration is used instead, which does not comply with the identity verification rules of power system interfaces.
How to Verify Proper Configuration
- Initiate a test request, check that returned fields exactly match the preset power grid equipment data structure, and verify that field units comply with configuration requirements.
- Review interface call logs to confirm that request intervals match the
incremental_sync_intervalsetting, with no frequent timeout errors. - Verify that webhook receiving endpoints can correctly parse received structured data, with no missing fields or format errors.
- Simulate a bulk device data request, confirm that pagination parameters returned by the interface match the
response_page_sizesetting, and that data is complete and not missing.
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.