> 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/quick-start-guide.md).

# Quick Start Guide

Verify your connection, make your first service request, and receive the response.

### Before you begin

Complete [Onboarding](https://docs.lhv.com/home/connect/fundamentals/authentication) and ensure you have:

* Access to the test environment.
* A valid connection certificate and its associated private key.
* Your `Client-Code` and `Client-Country` values.

Read [Authentication and Certificates](https://docs.lhv.com/home/connect/fundamentals/lhv-certificates) for connection requirements.

The examples below use the UK Connect test environment. Use the certificate, client details, and account supplied for that environment.

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

### 1. Verify your connection

Send a Heartbeat request to check your connection and certificate configuration.

Replace `YOUR_CLIENT_CODE` and `YOUR_CLIENT_COUNTRY` with your test client details, and update the certificate and private key paths.

```
curl --include \
  --cert "/path/to/client-certificate.pem" \
  --key "/path/to/client-private-key.pem" \
  --header "Client-Code: YOUR_CLIENT_CODE" \
  --header "Client-Country: YOUR_CLIENT_COUNTRY" \
  "${CONNECT_BASE_URL}/heartbeat"
```

The response body should contain a Heartbeat timestamp, for example:

```
<HeartBeatResponse>
    <TimeStamp>2026-10-21T12:00:00.000+00:00</TimeStamp>
</HeartBeatResponse>
```

The timestamp will vary.

A successful Heartbeat confirms connectivity and certificate configuration. You can then proceed to your first banking service request.

#### If the connection fails

Check that your certificate is valid for the test environment, that the private key matches it, and that your client details are correct.

If server certificate verification fails, check your system’s trusted certificate authorities and the [certificate guidance](https://docs.lhv.com/home/connect/fundamentals/lhv-certificates). Contact the Connect support team if you need help configuring trust.

### 2. Request your account balance

The [Account Balance](https://docs.lhv.com/home/connect/services/account-reports/account-balance) service provides a simple first business request.

Create a file named `account-balance.xml` using the following structure. Replace `YOUR_TEST_ACCOUNT_IBAN` with your test account IBAN.

```xml
<?xml version="1.0" encoding="UTF-8"?>
<Document xmlns="urn:iso:std:iso:20022:tech:xsd:camt.060.001.03">
    <AcctRptgReq>
        <GrpHdr>
            <MsgId>QUICKSTART-BALANCE-001</MsgId>
            <CreDtTm>2026-10-21T12:00:00+00:00</CreDtTm>
        </GrpHdr>
        <RptgReq>
            <ReqdMsgNmId>camt.052.001.06</ReqdMsgNmId>
            <Acct>
                <Id>
                    <IBAN>YOUR_TEST_ACCOUNT_IBAN</IBAN>
                </Id>
            </Acct>
            <AcctOwnr>
                <Pty/>
            </AcctOwnr>
        </RptgReq>
    </AcctRptgReq>
</Document>
```

Submit the request using your test connection details:

```
curl --include \
  --cert "/path/to/client-certificate.pem" \
  --key "/path/to/client-private-key.pem" \
  --header "Client-Code: YOUR_CLIENT_CODE" \
  --header "Client-Country: YOUR_CLIENT_COUNTRY" \
  --header "Content-Type: application/xml" \
  --data-binary "@account-balance.xml" \
  "${CONNECT_BASE_URL}/account-balance"
```

A successful submission returns HTTP `202 Accepted` with no response body. The balance report is generated separately and made available through Connect’s messaging services.

### 3. Receive and process the response

Read [Messaging Pattern](https://docs.lhv.com/home/connect/fundamentals/messaging) to understand how asynchronous responses are delivered and processed.

To complete your account balance request:

1. Retrieve the response through [Messages Services](https://docs.lhv.com/home/connect/services/messages).
2. Read the balance report using the [Account Balance response specification](https://docs.lhv.com/home/connect/services/account-reports/account-balance).
3. After processing the report, [mark the message as processed](https://docs.lhv.com/home/connect/services/messages/mark-message-as-processed).

You can also configure webhooks to receive notifications when messages become available, reducing the need to poll for updates. Depending on the configuration, the notification can include the full message body. See [Webhook Format and Processing](https://docs.lhv.com/home/connect/services/webhooks/introduction-and-payload-format) for details and setup guidance.

### 4. Explore other services

You have completed the first integration flow when you can:

* Receive a successful Heartbeat response.
* Submit an account balance request.
* Retrieve and process the balance report.

Explore the [Service Catalogue](https://docs.lhv.com/home/connect/services) to add further services, and review [News and Updates](https://docs.lhv.com/home/connect/news-and-updates) for changes relevant to your integration.


---

# 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/quick-start-guide.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.
