> For the complete documentation index, see [llms.txt](https://docs.lhv.com/home/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lhv.com/home/open-banking/lhv-bank-open-banking-api.md).

# LHV Bank Open Banking API

LHV Open Banking API - additional technical information page

{% hint style="info" %}
This page is your go-to resource for additional technical information about our Open Banking API.

Here, you’ll find:

* **Quarterly Performance and Uptime Statistics** to keep you updated on our API's reliability.
* **Dynamic Updates** and insights beyond the core technical specifications.

We are currently in the **pilot testing phase**, preparing for the full launch. As we gather feedback and make improvements, we’ll keep this space updated with the latest data and developments.

Stay tuned for more updates!
{% endhint %}

## Additional links

* Technical Specification - <https://priora.saltedge.com/docs/aspsp/v1#introduction>
* LHV Bank - <https://lhv.com/>


---

# 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.lhv.com/home/open-banking/lhv-bank-open-banking-api.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.