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 code and a description explaining what was changed.

Warning Code 01

Description: 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 03

Description: 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:

{
  "code": "03",
  "description": "wall_insulation: 2 is not allowed for build_year: 2010. Allowed values: [4]. Set wall_insulation: 4."
}

Warning Code 04

Description: 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:

{
  "code": "04",
  "description": "living_room_windows: 1 is not valid for build_year: 2010. Allowed values: [2, 3, 4]. Value has been adjusted to living_room_windows: 3."
}

Warning Code 05

Description: This warning occurs when heat_usage is provided together with an incompatible installation type.

• The field heat_usage is only valid when installation = 7.

• For all other installation types, the API ignores heat_usage.

Example:

{
  "code": "05",
  "description": "heat_usage is not valid with installation: 2. Value has been ignored."
}

Warning Code 08

Description: 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:

pv_total_watt_peak = pv_area × specific_watt_peak

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_peak directly or provide pv_area and specific_watt_peak.

Example:

{
  "code": "08",
  "description": "For solar panel 1, pv_total_watt_peak is already set. pv_area and specific_watt_peak have been ignored."
}

Warning Code 11

Description: 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:

{
  "code": "11",
  "description": "Current building with energy label A already meets target_label B."
}

or

{
  "code": "11",
  "description": "Current building with energy label A already meets default target_label A."
}