Missing Updates from Companies House Streaming API for Recent CS01 Acceptances

API Issues
1

Hi Team,

We have integrated the Companies House Streaming API to receive updates for changes in company details—specifically due date changes—via the following endpoint:

https://stream.companieshouse.gov.uk/companies

We have several active companies whose CS01 filings were accepted between 07/11/2025 and 16/11/2025.
These updates are already reflected on the Companies House website; however, we did not receive any corresponding events through the Streaming API.

Could you please investigate why the Streaming API did not deliver these updates?
If possible, we would appreciate it if you could republish the relevant updates.

I will be able to share the list of 8 company number via an email for which we didn’t received events.

Thank you for your assistance.

2

Hi,

We have checked one of the examples (16079562 – Accepted on 16/11/2025) because that’s the latest and therefore the most likely to still be in the streams.

We did send a ‘companies’ stream event with updated CS01 dates:

{“resource_kind”:“company-profile”,“resource_uri”:“/company/16079562”,“resource_id”:“16079562”,“data”:{“accounts”:{“accounting_reference_date”:{“day”:“30”,“month”:“11”},“next_accounts”:{“due_on”:“2026-08-14”,“period_end_on”:“2025-11-30”,“period_start_on”:“2024-11-14”},“next_due”:“2026-08-14”,“next_made_up_to”:“2025-11-30”},“can_file”:true,“company_name”:“ALASTRA LABS LTD”,“company_number”:“16079562”,“company_status”:“active”,“confirmation_statement”:{“last_made_up_to”:“2025-11-16”,“next_due”:“2026-11-30”,“next_made_up_to”:“2026-11-16”},“date_of_creation”:“2024-11-14”,“etag”:“e5ee724ac6cf4d1f0520bf867035fb19c5d5021e”,“jurisdiction”:“england-wales”,“links”:{“filing_history”:“/company/16079562/filing-history”,“officers”:“/company/16079562/officers”,“persons_with_significant_control”:“/company/16079562/persons-with-significant-control”,“self”:“/company/16079562”},“registered_office_address”:{“address_line_1”:“30 Churchill Place”,“country”:“United Kingdom”,“locality”:“London”,“postal_code”:“E14 5RE”},“sic_codes”:[“62012”,“70210”,“70229”,“73110”],“type”:“ltd”},“event”:{“timepoint”:104542819,“published_at”:“2025-11-16T09:53:02”,“type”:“changed”}}

Note the CS date object values are correct:

“confirmation_statement”:

{“last_made_up_to”:“2025-11-16”,

“next_due”:“2026-11-30”,

“next_made_up_to”:“2026-11-16”}

And for info, two F/H stream events for the CS01 transaction itself - one when the transaction was accepted and a second when the image was appended to it:

{“resource_kind”:“filing-history”,“resource_uri”:“/company/16079562/filing-history/MzQ4OTA3MTY5M2FkaXF6a2N4”,“resource_id”:“MzQ4OTA3MTY5M2FkaXF6a2N4”,“data”:{“barcode”:“XEFFX84B”,“category”:“confirmation-statement”,“date”:“2025-11-16”,“description”:“confirmation-statement-with-no-updates”,“description_values”:{“made_up_date”:“2025-11-16”},“links”:{“self”:“/company/16079562/filing-history/MzQ4OTA3MTY5M2FkaXF6a2N4”},“transaction_id”:“MzQ4OTA3MTY5M2FkaXF6a2N4”,“type”:“CS01”},“event”:{“timepoint”:211810872,“published_at”:“2025-11-16T09:53:02”,“type”:“changed”}}

{“resource_kind”:“filing-history”,“resource_uri”:“/company/16079562/filing-history/MzQ4OTA3MTY5M2FkaXF6a2N4”,“resource_id”:“MzQ4OTA3MTY5M2FkaXF6a2N4”,“data”:{“barcode”:“XEFFX84B”,“category”:“confirmation-statement”,“date”:“2025-11-16”,“description”:“confirmation-statement-with-no-updates”,“description_values”:{“made_up_date”:“2025-11-16”},“links”:{“document_metadata”:“https://document-api.company-information.service.gov.uk/document/uhPWZIJZ0SvWJw8eITay9VSG0d2M7hJAa-i1mjpmYZI",“self”:“/company/16079562/filing-history/MzQ4OTA3MTY5M2FkaXF6a2N4”},“pages”:3,“transaction_id”:“MzQ4OTA3MTY5M2FkaXF6a2N4”,“type”:“CS01”},“event”:{“fields_changed”:[“links.document_metadata”],“timepoint”:211810881,“published_at”:“2025-11-16T09:53:39”,“type”:"changed”}}

We have however sent the profile events again.

SDN

3

All the records are now successfully updated on our end. We really appreciate your assistance in looking into this and expediting the process. We will review our internal integration to understand why the original events were not received.

Thanks again for your support.