LogoLogo
Connect
Connect
  • 🏑Welcome to LHV Connect API
  • πŸ“ΊNews and Updates
    • πŸ“ˆPerformance and Stats
    • πŸ””Notice of Change
  • 🧭Quick Start Guide
  • πŸŽ₯Connect Fundamentals
    • Authentication and Certificates
    • Environments
    • Messaging Pattern
    • Service Provider model
    • Technical limitations
    • Encoding and Languages
    • Response Compression
    • Dates and Time Zones
    • Response Codes and Error handling
    • Onboarding
    • Live Proving
    • LHV UK and Estonia integrations
    • FAQ and Tips
  • πŸ“–Service Catalogue
    • πŸ’šHeartbeat
      • Heartbeat - GET
      • Heartbeat Advanced - GET
    • πŸ“©Messages Services
      • Get next message
      • Get list of messages
      • Get list of messages V2
      • Get message by response ID
      • Count number of messages
      • Mark message as processed
      • Mark batch of messages as processed
      • Mark batch of messages as processed V2
      • Messages Metadata
      • Get compressed message for testing
    • πŸ’°Account Information Services
      • Account Balance
      • Account Statement
      • Transaction Notification
        • Incoming Bacs Credit Notification
    • πŸ’ΈPayment Initiation Services
      • Pain.001.001.09
      • Pain.002.001.10
      • Samples
      • Authentication methods
      • Payment Scheme Selection
      • Payment Return Initiation
      • Payments Service Idempotency
      • Payments Originating Overseas
      • Legacy documents
        • pain.001.001.03 format
    • βœ…Confirmation of Payee Services
      • Confirmation of Payee - Requester
      • Confirmation of Payee - Responder
    • πŸ˜Άβ€πŸŒ«οΈVIBAN Services
      • VIBAN Open
      • VIBAN Bulk Open
      • VIBAN Modify
      • VIBAN Info
      • VIBAN Close
      • VIBAN Notification
    • πŸ”—Indirect Scheme Access
      • Agency Account Synchronization
      • RTF - Routing Table Files message
      • 🧾Payment Collection Services
        • πŸ’·Bacs Direct Debit
          • Bacs Direct Debit Mandate Initiation Request
          • Bacs Direct Debit Mandate Initiation Response
          • Bacs Direct Debit Mandate Initiation Response Confirmation
          • Bacs Direct Debit Mandate Cancellation Request
          • Bacs Direct Debit Mandate Cancellation Response
          • Direct Debit Incoming Collection Notification Request
          • Direct Debit Collection Notification Response
          • Direct Debit Collection Notification Response Confirmation
          • Direct Debit Reversal Notification Request
          • Examples
    • πŸ“¨Webhooks
      • Webhook Format and Processing
      • Managing Webhook Configurations
      • Webhook Security
      • Webhook Metadata
      • Full Bodied Webhooks
  • πŸ—“οΈReference
    • Glossary
    • Code Reference Tables
      • Balance Type Codes
      • Credit and Debit Transaction Codes
      • Payment Scheme Codes
      • Direct Debit Scheme Codes
      • Payment Reject Codes
      • Payment Return Codes
      • Bacs Direct Debit Mandate Reject Codes
      • Bacs Direct Debit Reject Codes
      • Bacs Direct Debit Reversal Reason
      • Bank Transaction Codes
      • Transaction Purpose Codes
      • Category Purpose Codes
      • Private Person Identification Codes
      • Organisation Identification Type Codes
      • Payment Priority Codes
      • Charges Bearer Codes
  • ☎️Support
    • Contact
Powered by GitBook
On this page

Was this helpful?

  1. News and Updates

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.

For assistance with updates or other aspects of the Connect API, please contact operations@lhv.com.

πŸ“£ Response Compression in Connect API

Issued: 22 April 2025 Production Release: 26 May 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 26 May 2025.

Does This Affect You?

This change may impact you if:

  • You use the UK Connect API: https://connect.lhv.com (Clients using https://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 both

  • Confirm 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


PreviousPerformance and StatsNextQuick Start Guide

Last updated 1 day ago

Was this helpful?

πŸ“Ί
πŸ””