> 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/services/messages/get-request-by-request-id.md).

# Get request by request ID

## Service Description

Use this service to retrieve the full content of a previously submitted request by its unique request ID.

## Request

<mark style="color:green;">`GET`</mark> <https://connect.lhv.com/v2/requests/{RequestId}>

### Headers

<table><thead><tr><th width="174.95703125">Name</th><th width="193.484375">Value</th><th>Description</th></tr></thead><tbody><tr><td>Client-Code</td><td><code>customer value</code></td><td>For Service Providers only. Company registration code of the Service Provider or its customer. When using the Service Provider own value also related customers messages are returned by default</td></tr><tr><td>Client-Country</td><td><code>customer value</code></td><td>For Service Providers only. Should match the value of Client-Code</td></tr></tbody></table>

### Body

This request doesn't have a body.

## Response

<table><thead><tr><th width="174.95703125">Name</th><th width="193.484375">Value</th><th>Description</th></tr></thead><tbody><tr><td>Content-Type</td><td><code>application/json</code></td><td>Format of the message body</td></tr><tr><td>X-Bank-Code</td><td><code>LHVUK</code>, <code>LHVEE</code></td><td>LHV Bank entity</td></tr></tbody></table>

### Body

{% tabs %}
{% tab title="200 - request" %}
{% hint style="success" %}
OK
{% endhint %}

```xml
<Document xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:iso:std:iso:20022:tech:xsd:camt.060.001.03">
    <AcctRptgReq>
        <GrpHdr>
            <MsgId>MESSAGE_20250519T060345</MsgId>
            <CreDtTm>2025-05-19T05:03:45</CreDtTm>
        </GrpHdr>
        <RptgReq>
            <ReqdMsgNmId>camt.053.001.02</ReqdMsgNmId>
            <Acct>
                <Id>
                    <IBAN>GB89LHVB04030400000000</IBAN>
                </Id>
            </Acct>
            <AcctOwnr>
                <Pty />
            </AcctOwnr>
            <RptgPrd>
                <FrToDt>
                    <FrDt>2025-05-18</FrDt>
                    <ToDt>2025-05-18</ToDt>
                </FrToDt>
                <FrToTm>
                    <FrTm>00:00:00+02:00</FrTm>
                    <ToTm>23:59:59+02:00</ToTm>
                </FrToTm>
                <Tp>ALLL</Tp>
            </RptgPrd>
        </RptgReq>
    </AcctRptgReq>
</Document>
```

{% endtab %}

{% tab title="204 - no request" %}
{% hint style="info" %}
Request ID doesn't exist
{% endhint %}
{% endtab %}

{% tab title="403 - error" %}
{% hint style="danger" %}
Error code and description
{% endhint %}

```json
<Errors>
    <Error>
        <ErrorCode>FORBIDDEN</ErrorCode>
        <Description>User doesn't exist</Description>
    </Error>
</Errors>
```

{% endtab %}
{% endtabs %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.lhv.com/home/connect/services/messages/get-request-by-request-id.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.