> 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/nta-8800-energylabel-api/changelog.md).

# Changelog

Changelog of the deploy of the Energylabel API in format iteration (1.01) and (expected) release date (year, month and day).

### 1.12- 2025-07-02

* EPOnline version update from V4 to V5.

### 1.11- 2025-03-06

* Optimized the service to better process larger number of API requests

### 1.10- 2024-12-11

* Added a correction for the calculated yearly gas consumption "estimated\_gas\_usage", based on statistical averages of houses in the Netherlands.

### 1.09 - 2024-12-05

* Added "current\_estimated\_BENG1\_score" output. This output display the current estimated BENG1 score.

### 1.08 - 2024-09-16

* EPOnline version update from V3 to V4.

### 1.07 - 2024-06-18

* Added "measures\_method" output. This output indicates the method used to determine the measures.
* Fixed bug related to "build\_year" and "living\_room\_windows" mismatch. 

### 1.06 - 2024-02-02

* Added "definitive\_BENG2 score" output. This output display the definitve BENG2 score.
* Implemented a data-driven approach by utilizing known information to enhance the accuracy of the estimated measures.

### 1.05 - 2023-12-15

* Added "estimated\_city\_heating\_usage" output. This output display the yearly heat consumption in GJ.

### 1.04 - 2023-12-05

* Added "inhabitants" input

### 1.03 - 2023-10-09

* Added current "CO2" output
* Added "watt\_panels" input to interpret "solar\_panels" input as watt peak capacity solar panels. Example input: "solar\_panels": 15000, "watt\_panels": 0

### 1.02 - 2023-09-23

* Added "ventilation" as input/output

### 1.01 - 2023-08-29

* Added /bag endpoint for requesting sustainability advice based on BAG ID (VBO)


---

# 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/nta-8800-energylabel-api/changelog.md?ask=<question>&goal=<user_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.