> 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/platform/kadaster-transaction-api-subscription.md).

# Kadaster Transaction API subscription

The Kadaster Transaction API is available through credits within your paid subscription on the Platform. The API is not available in the free trial.

The number of credits per call is in the [Cost Calculator](https://platform.altum.ai/abonnement?tab=calculator) on the platform.

### What is the Kadaster Transaction API?

The Transaction API is a paid service where transaction data can be requested from the Kadaster for a home. Check out the documentation below.

{% content-ref url="/pages/-MhMyhJrqm7Rd5GLJsPV" %}
[Kadaster Transaction API](https://docs.altum.ai/english/property-valuation-and-market/kadaster-transaction-api.md)
{% endcontent-ref %}

### How do I avoid unnecessary costs when using the API?

Eg. if no transaction is (yet) known. It is possible to 'ping' the Transaction API on the presence of the requested data. To do this, send an API call as usual, only not on api.altum.ai/transaction but on api.altum.ai/transaction/ping. With a positive feedback on this request, you can run the API call at the usual URL. With the ping you first check whether transaction data is available. The ping only works with a paid subscription and is not counted as paid usage.


---

# 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/platform/kadaster-transaction-api-subscription.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.
