> For the complete documentation index, see [llms.txt](https://docs.altum.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.altum.ai/english/sustainability/sustainability-api-v2/changes-from-previous-version.md).
# Changes from previous version
## 1. Request body
Embed input has changed.
From:
```
{
"data": {
"post_code": "2771DS",
"house_number": "87",
"house_addition": "",
"target_label": "A++++",
"eco_delta": 0
}
}
```
To
```
{
"postcode": "2771DS",
"housenumber": "87",
"houseaddition": "",
"target_label": "A++++",
"eco_delta": 0
}
```
**The feature names have also changed for consistency with other apis.**
## 2. Inputs
**a. Basic features**
roof\_type (new)
sloped\_roof\_insulation (changed from roof\_insulation)
flat\_roof\_insulation (changed from roof\_insulation)
electric\_cooking (new)
cooling (new)
district\_heating\_allowed (new)
electricity\_generation (new)
solar\_panels (per solar panel) (changed from integer to list)
* pv\_total\_watt\_peak
* pv\_area (changed from separate solar\_panels\_surface)
* specific\_watt\_peak
* angle
* orientation
* free\_roof\_area
* roof\_type
#### b. Costs assumptions
cost\_indicators (changed from codes to names)
* fixed\_gas\_price
* variable\_gas\_price
* energy\_tax\_gas
* fixed\_electricity\_price
* variable\_electricity\_price
* energy\_tax\_electricity
* fixed\_heat\_price
* energy\_tax\_heat
* variable\_heat\_price
* tax\_credit
* feed\_in\_compensation
* feed\_in\_cost
* fixed\_solar\_panel\_costs
* netting\_percentage
* gas\_yearly\_price\_increase
* electricity\_yearly\_price\_increase
* external\_heating\_yearly\_price\_increase
* term
* discount\_rate
* tax\_rate
* custom\_costs
see [Cost indicators](/english/sustainability/sustainability-api-v2/cost-indicators.md)
#### c. Measure filters
* wall\_filters
* sloped\_roof\_filters
* flat\_roof\_filters
* floor\_filters
see [Measure filters](/english/sustainability/sustainability-api-v2/measure-filters.md)
## 3. Outputs
number \_of\_doors
solar\_panel\_yield
energy\_cost\_monthly
energy\_cost\_yonthly
return\_on\_investment
sloped\_roof\_insulation (changed from roof\_insulation)
flat\_roof\_insulation (changed from roof\_insulation)
cooling (new)
electric\_cooking (new)
solar\_panels (per solar panel)
* roof\_surface
* roof\_type
* original\_watt\_peak\_capacity
* total\_watt\_peak\_capacity
* added\_watt\_peak\_capacity
* added\_panels
* inclination\_angle
* orientation
## 4. Output modifications
from:
```
"usage": {
"gas": 1630,
"energy": 2286,
"city_heating": 0
},
"usage_potential": {
"gas": 1362,
"energy": 75,
"city_heating": 0
}
```
to:
```
"gas_usage": {
"current": 1630,
"potential": 1362
},
"electricity_usage": {
"current": 2286,
"potential": 75
},
"city_heating_usage": {
"current": 0,
"potential": 0
}
```
*energy becomes electricity*
## 5. Feature modifications
The value of some features now go from 1 to 4 instead of 0 to 3. Like:
wall\_inulation, floor\_insulation, living\_room\_windows, bedroom\_windows and the new flat\_roof\_insulation, sloped\_roof\_insulation
For example: “mediocre” wall\_insulation was 1 and now it has the number 2
See documentation for more info.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.altum.ai/english/sustainability/sustainability-api-v2/changes-from-previous-version.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.