Notice of Change
This page lists important service-level changes that may impact your integration with LHV Connect. Each notice includes a summary of whatβs changing, who it affects, and any required actions.
Notices are listed in reverse chronological order, with the newest changes at the top.
π£ Response Compression in Connect API
Issued: 22 April 2025 Original Production Release: 26 May 2025 Updated: 28 May 2025 New Production Release: 9 June 2025
The roll out of the response compression change has been delayed to give customers more time to prepare. The new production release date is: 9 June 2025
Whatβs Changing and Why
LHV Connect is introducing response compression for large API responses to improve performance and transmission efficiency. Compression applies to payloads β₯10MB and helps reduce bandwidth usage, especially for endpoints that return large message bodies (e.g., Get next message). Most modern HTTP clients support decompression automatically, but behavior may vary depending on the tools or libraries used.
This change is currently available in Prelive environment and is scheduled for Production rollout on 9 June 2025 (previously planned for 26 May 2025).
Does This Affect You?
This change may impact you if:
You use the UK Connect API:
https://connect.lhv.com
(Clients usinghttps://connect.lhv.eu
are not affected)You use Connectβs Message Services, such as
GET /messages/next
You expect to receive API responses β₯10MB
Your HTTP client does not support response decompression or lacks a compatible
Accept-Encoding
header
If a compressed response is triggered but your client cannot decompress it, the API may return an error (e.g., HTTP 500). Currently, the most likely affected service is Account Statement delivery.
What You Need to Do
To ensure compatibility:
Add the
Accept-Encoding
header to your requests:gzip
,deflate
, or bothConfirm that your HTTP client supports decompression (most modern libraries do this by default)
Compression will only be applied if:
The response body is at least 10MB, and
The request includes a supported
Accept-Encoding
header
Now we have also available a dedicated service for quick and easy testing of Compression. More details at Get compressed message for testing
Additional Information and Resources
For more details see Response Compression
Last updated
Was this helpful?