> 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-valuation-and-market/avm-api/changelog.md).

# Changelog

#### 2.2 - 2022-09-28

* Fixed issue with not accepting both Upper case and Lower case for house number addition letters.

#### 2.1  - 2022-08-02

* Updated house-types input. See [House types](/english/property-valuation-and-market/avm-api/house-types.md)

#### 2.0 - 2022-03-21

* Added [AccuracyIndicator](/english/property-valuation-and-market/avm-api/accuracy-indicator.md) to the output = "AccuracyIndicator": 1

#### 1.03 - 2021-07-27

#### Changed

* User is able to input and overwrite house-type
* Added Error 400 response when the house does not exist in the database. The error message is "Output: The given house address not found in database, the combination of Post Code, House Number and House Addition does not exist.".
* Added Error 400 response when the prediction is too low. The message is "Output: The prediction is too low.".
* Added Error 400 response when the house-type is not supported. The message is "Output: The given house type is unsupported or unknown."

#### 1.0.2 - 2021-01-25

#### Added

* Added house type as input "housetype" to overwrite default
* Added usage of internal reference API for optimized reference objects
* Latest AVM model with increased [accuracy and reliability](https://altum.ai/accuratesse-altum-ai/)

#### Fixed

* BAG ID is now 16 characters

#### Removed

* WOZ functionality - this is now part of the [WOZ API](https://docs.altum.ai/apis/woz-api)


---

# 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-valuation-and-market/avm-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.