> 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/connect/readme.md).

# Welcome to LHV Connect API

Integrate your systems with LHV Bank’s banking services.

LHV Connect enables clients to access banking services directly from their own systems. A UK Connect connection can provide access to services offered by both LHV Bank Limited (LHV UK) and LHV Bank AS (LHV EE), depending on your agreed service configuration.

Use this documentation to prepare your connection, implement supported services, and understand how to process requests and responses.

### Get started

API access requires onboarding with LHV Bank. To begin your integration:

1. Review [Onboarding](https://docs.lhv.com/home/connect/fundamentals/authentication) to understand the steps for obtaining access.
2. Read [Authentication and Certificates](https://docs.lhv.com/home/connect/fundamentals/lhv-certificates) to prepare your connection.
3. Follow the [Quick Start Guide](https://docs.lhv.com/home/connect/quick-start-guide) to verify connectivity and make your first request.

### Understand how Connect works

Connect supports synchronous and asynchronous operations. Depending on the service, a response may be returned directly or delivered separately through Connect’s messaging services.

For asynchronous updates, we recommend using webhooks to receive event notifications as they become available, reducing the need to poll for updates. See the [Webhook documentation](https://docs.lhv.com/home/connect/services/webhooks/introduction-and-payload-format) for details.

Before implementing a service, review its request and response behaviour and read the [Messaging Pattern](https://docs.lhv.com/home/connect/fundamentals/messaging) guide to understand how to receive and process messages.

The [Connect Fundamentals](https://docs.lhv.com/home/connect/fundamentals) section explains the core concepts and connection requirements.

### Explore the services

Browse the [Service Catalogue](https://docs.lhv.com/home/connect/services) for service descriptions and technical specifications, including account reports, payments, and virtual IBAN services.

Consult each service’s reference for request formats, required fields, and response details. The services available to your integration depend on your agreed service configuration.

### UK and Estonia services

Clients can use a UK Connect connection to access both UK and EE services, depending on their agreed service configuration.

This portal documents the UK Connect interface and UK services. For EE service specifications, refer to the [LHV EE Connect documentation](https://partners.lhv.ee/en/connect).

If you use EE services through UK Connect, read [LHV UK and Estonia integrations](https://docs.lhv.com/home/connect/fundamentals/lhv-uk-and-estonia-integrations) alongside the relevant service specifications.

### Keep your integration up to date

Review [News and Updates](https://docs.lhv.com/home/connect/news-and-updates) for published changes relevant to your integration.

### Service status

Visit the [LHV Status Page](https://status.lhv.ee/) for information and announcements about service availability and interruptions.


---

# 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/connect/readme.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.
