Warnings
Unlike errors, warnings do not block the request. They indicate that some input values were not valid or redundant, and the API has automatically corrected or adjusted them to valid values.
The request is still processed successfully.
The response includes a list of warnings (if any).
Each warning contains a
codeand adescriptionexplaining what was changed.
Warning Code 01
01Description:
This warning occurs when the provided value for inner_surface_area is below the minimum limit allowed by the API.
When this happens, the API automatically adjusts the value to the minimum valid limit.
Example:
{
"code": "01",
"description": "inner_surface_area: 30.0 is below the minimum limit of 53.8. Value has been adjusted to inner_surface_area: 53.8."
}Warning Code 02
02Description:
This warning occurs when the provided value for inner_surface_area is outside the maximum limit allowed by the API.
When this happens, the API automatically adjusts the value to the maximum valid limit.
Example:
{
"code": "02",
"description": "inner_surface_area: 200.0 is outside the maximum limit of 33.75. Value has been adjusted to inner_surface_area: 33.75."
}Warning Code 03
03Description:
This warning occurs when the value provided for one of the following measures — wall_insulation, floor_insulation, sloped_roof_insulation, or flat_roof_insulation — is not valid for the specified build_year.
In such cases, the API automatically adjusts the measure to a different valid value.
Example:
Warning Code 04
04Description:
This warning occurs when the value provided for either living_room_windows or bedroom_windows is not valid for the specified build_year.
In such cases, the API automatically adjusts the field to a different valid value.
Example:
Warning Code 05
05Description:
This warning occurs when heat_usage is provided together with an incompatible installation type.
The field
heat_usageis only valid wheninstallation = 7.For all other installation types, the API ignores
heat_usage.
Example:
Warning Code 08
08Description:
This warning occurs when pv_total_watt_peak is explicitly set for a solar panel. Since pv_total_watt_peak can already be calculated as:
the API ignores the fields pv_area and specific_watt_peak for that panel to avoid conflicting or redundant inputs.
Details:
Applies individually to each solar panel (
solar panel 1,solar panel 2, …).Only one input method should be used: either set
pv_total_watt_peakdirectly or providepv_areaandspecific_watt_peak.
Example:
Warning Code 11
11Description:
This warning occurs when the current energy label already matches the target_label.
In this case, no further adjustment is necessary because the building already meets the intended target.
Example:
Warning Code 61
61Description: This warning occurs when a selected material for a filter is not valid.
In such cases, the API automatically remove the filter.
Last updated