What the data for this category looks like
Sources of black home appliance intelligent due diligence data include the National Home Appliance Energy Efficiency Public Service Platform, 3C Certification Query System, brand’s public product library, and supply chain management system. Compliance-related fields such as 3C certificate number and energy efficiency level are updated when certifications change. Basic product parameters are updated when new products launch. Monthly sales data is synchronized monthly.
Each individual due diligence data entry contains three structured field categories: product identification, compliance verification, and supply chain association. The fields include product_model, 3c_cert_id, energy_efficiency_level, supplier_registration_code, monthly_sales_volume. Energy efficiency level uses an enumerated number, sales volume is an integer, and certificate number uses a string format.
What constraints these characteristics impose on HTTP Interfaces and External Systems
Compliance data updates do not follow a fixed schedule, and are only triggered when certifications change. As a result, HTTP interfaces must support incremental queries by 3c_cert_id or product_model to reduce interface call frequency.
Data comes from three distinct systems. External system integration requires configuring multiple endpoint routes, each corresponding to a different field set pulling logic. Some fields are updated monthly as structured data. Interfaces must support time range parameters to ensure alignment of data across time dimensions.
Fields include multiple types: enumerated values, integers, and strings. Interfaces must have strict parameter validation rules to block invalid requests. Additionally, black home appliance models are numerous, so single-batch returned data volume may be large. Interfaces must support pagination query logic.
Configuration Settings
| Configuration Item | Recommended Value | Rationale |
|---|---|---|
external_api_endpoint | ["https://energy.efficiency.gov.cn/api/v1", "https://3c-cert.gov.cn/api/v2", "https://supplier-scm.com/api/v1"] | Official interface addresses for the three data sources, covering full due diligence data for compliance, certification, and supply chain |
api_request_timeout | 30 seconds | Response delays for black home appliance compliance interfaces typically fall within the 10-25 second range. 30 seconds covers most normal requests |
incremental_sync_cursor | last_update_time | Compliance data uses update time as the unique identifier for incremental pulls, which aligns with the interface design logic of each data source |
response_field_whitelist | ["product_model", "3c_cert_id", "energy_efficiency_level", "monthly_sales_volume"] | Only retain fields required for due diligence reports, reducing data transmission volume and processing overhead |
page_size | 50 entries | Single-batch returned data volume is moderate, avoiding interface timeouts or memory overflow |
auth_type | api_key | Most external interfaces in the home appliance industry use API key authentication, which aligns with general integration specifications |
The parameter values provided on this page are common recommended starting points for configuration. Actual values are affected by material form, data volume, and business rules. Specific issues require case-by-case analysis. It is recommended to test on your own samples before finalizing settings.
Three Common Misconfigurations
- Symptom: Interface returns
413 Request Entity Too Largeerror. Cause:response_field_whitelistis not configured, and redundant non-required fields from the data source are pulled, causing the response body to exceed the interface size limit. - Symptom: Duplicate product data appears in due diligence reports. Cause:
last_update_timeis not used as the incremental pull cursor, and all data is pulled fully without filtering previously synchronized old records. - Symptom: Interface returns
400 Bad Requestwith a field format error prompt. Cause: Parameter validation rules are not configured, and an energy efficiency level value outside the enumerated range is passed, which does not meet the interface requirements of the data source.
How to Verify Successful Configuration
- Initiate a single interface request, and verify that the returned fields exactly match the list configured in
response_field_whitelist. - Configure the incremental pull cursor parameter, initiate a request, and confirm that only data updated within the time range marked by the cursor is returned.
- Initiate a request using credentials that do not comply with authentication rules, and confirm that the corresponding authentication failure error code is returned.
- Initiate batch requests, and confirm that the returned data pagination logic aligns with interface design, with no excessive volume of returned data.
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.