> 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/property-data/woz-api/changelog.md).

# Changelog

### 1.20 - 07-09-2025

* Improved address matching (handles case variations)
* Missing 2024 WOZ data bug squashed

### 1.06 - 11-30-2023

* Inner surface area added.

### 1.05 - 2-21-2023

* Ping function now also works for the GET request

### 1.04 - 11-10-2022

* Added ping function to check availability of next year's WOZ value via a free API service. Post request to **api.altum.ai/woz/ping**

### 1.03 - 24-8-2022

* Added optional *index* parameter as input to remove the IndexedValue as output. Default = 1
* Optimized the parsing of data to increase coverage of the API

### 1.02 - 8-6-2022

* Bugfix for diplaying BAGID as string instead of an integer
* Bugfix for displaying OuterSurfaceArea as integer instead of a decimal
* Added IndexedValue for latest known WOZ value, indexing the value based on the Kadaster index from latest date e.g. 1-1-2020 till latest known Kadaster index month e.g. 5-2022.

### 1.01 - 3-6-2022

* Redesigned architecture to mitigate issues where in some cases WOZ-values were not properly retrieved


---

# 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/property-data/woz-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.