> 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/fundamentals/response-compression.md).

# Response Compression

Our API requires response compression for all requests when certain conditions are met. This enables us to return larger payloads while maintaining fast response times.

Currently, this applies to [Messages Services](/home/connect/services/messages.md) that return message bodies in the response.

A response will be compressed when the following conditions are met:

* The response body is at least **10 MB** in size.
* The client request includes `Accept-Encoding` header specifying one of the supported compression types:

| Accept-Encoding Header | Details                                                                                  |
| ---------------------- | ---------------------------------------------------------------------------------------- |
| gzip                   | The response will be compressed using gzip.                                              |
| deflate                | The response will be compressed using deflate.                                           |
| gzip, deflate          | The response will be compressed using gzip, as this is our preferred compression scheme. |

{% hint style="danger" %}
If a message body exceeds 10 MB and the client does not support compression (i.e., does not include a supported `Accept-Encoding` header), our API returns an error — most likely an HTTP 500. The exact outcome may vary depending on the client’s implementation.
{% endhint %}

We recommend making use of the `Accept-Encoding` header containing compressed forms for all requests if possible, provided that the HTTP client in use can handle compressed payloads. This will ensure response times will be minimised no matter the overall size of the response body. Most modern HTTP clients should handle decompression out of the box, so no extra implementation would be required to read a compressed body.

{% hint style="info" %}
We also provide a dedicated service for quick and easy compression testing. More details are available at: [Get compressed message for testing](/home/connect/services/messages/get-next-message-1.md)
{% endhint %}


---

# 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/fundamentals/response-compression.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.