# Streaming API - Periodic Short-Lived Connections (Scheduled Lambda Catch-up Pattern)

**URL:** <http://forum.companieshouse.gov.uk/t/streaming-api-periodic-short-lived-connections-scheduled-lambda-catch-up-pattern/12502>\
**Category:** API Question\
**Created:** [December 3, 2025, 11:33am UTC](http://forum.companieshouse.gov.uk/t/streaming-api-periodic-short-lived-connections-scheduled-lambda-catch-up-pattern/12502 "2025-12-03T11:33:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kyrylo.skriaha](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/k/8e8cbc/32.png) [@kyrylo.skriaha](http://forum.companieshouse.gov.uk/u/kyrylo.skriaha)\
**Post date:** [December 3, 2025, 11:33am UTC](http://forum.companieshouse.gov.uk/t/streaming-api-periodic-short-lived-connections-scheduled-lambda-catch-up-pattern/12502/1 "2025-12-03T11:33:43Z")

</div>

Hi,

We’re planning to use the Streaming API with periodic reconnections every 30 minutes via scheduled AWS Lambda:

1. Connect with last saved timepoint
2. Read available events
3. Save timepoint and disconnect
4. Repeat in 30 minutes (~48 reconnections/day)

Question: Is this reconnection frequency acceptable, or does it risk rate limiting?

Your documentation mentions “repeatedly opening connections can lead to rate limiting,” but doesn’t define what “repeatedly” means.

Thanks!

---

<div class="post-metadata">

**Author:** ![kyrylo.skriaha](http://forum.companieshouse.gov.uk/letter_avatar_proxy/v4/letter/k/8e8cbc/32.png) [@kyrylo.skriaha](http://forum.companieshouse.gov.uk/u/kyrylo.skriaha)\
**Post date:** [December 9, 2025, 3:30pm UTC](http://forum.companieshouse.gov.uk/t/streaming-api-periodic-short-lived-connections-scheduled-lambda-catch-up-pattern/12502/2 "2025-12-09T15:30:34Z")

</div>

Reposting the answer from support:

> The proposed Streaming API usage is acceptable, provided there are no more than 10 active connections per API key at any given time.