UK Insolvency Notice Monitor - The Gazette avatar

UK Insolvency Notice Monitor - The Gazette

Pricing

from $0.02 / actor start

Go to Apify Store
UK Insolvency Notice Monitor - The Gazette

UK Insolvency Notice Monitor - The Gazette

Watches The Gazette for new UK insolvency notices - corporate winding-up, administration, liquidation, receivership, or personal bankruptcy/IVA. Each scheduled run emits only notices published since the last run, with company name and number, plus optional webhook POST.

Pricing

from $0.02 / actor start

Rating

0.0

(0)

Developer

FJ Banks

FJ Banks

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

7 hours ago

Last modified

Share

UK Insolvency Notice Monitor — The Gazette

Watches The Gazette (the UK's official public record) for new insolvency notices and, on every scheduled run, emits only the notices published since the last run — deduplicated, with the company name/number and a direct link. Optional webhook POST to Slack, Zapier, Make or n8n.

Choose corporate insolvency (winding-up, administration, liquidation, receivership), personal insolvency (bankruptcy orders, IVAs), or all.

Who it's for

BuyerUse
Debt collection / recovery agenciesNew corporate liquidations = act before the pool of assets shrinks
Credit insurers & credit-control teamsReal-time risk signal on customers and their customers
Insolvency practitioners / turnaround advisorsPetitions to wind up = a company that may still be saveable
Commercial landlords & suppliersA tenant/customer entering administration, the day it's gazetted
CompetitorsA rival winding down — their customers and staff are in play
Journalists & researchersCompany-failure rate by sector or region
Asset buyers / auctioneersLiquidations mean plant, stock and IP coming to market

Quick start

  1. Paste nothing — there is no API key. The Gazette is a free public record.
  2. Pick a scope (corporate / personal / all) and optionally a text filter (a town, a sector keyword, an insolvency practitioner's name).
  3. Run once to seed state (firstRunLookbackDays controls the backfill).
  4. Schedule it (Apify Console → Schedules) — daily, or a few times a day for speed-to-lead. Later runs are incremental automatically.

Input

FieldTypeDefaultDescription
scopecorporate | personal | allcorporateWhich insolvency notices to track.
textstringOptional free-text filter across the whole notice (company name, town, court, practitioner).
includeDetailbooleantrueFetch each notice's linked-data record for company number / court / case number (1 extra request per notice).
firstRunLookbackDaysinteger 1–303First run only: how many days of notices to fetch.
webhookUrlstringPOST {source, scope, window, count, notices[]} here each run.
maxResultsinteger 1–5000500Cap per run. Excess rolls to the next run.

Output

One dataset item per new notice:

FieldExample
notice_id"5203210"
notice_code"2441"
notice_type"Resolutions for Winding-up"
is_corporatetrue
title"TRINITY EUROPE LIMITED"
published"2026-09-03T01:05:22"
company_name"TRINITY EUROPE LIMITED"
company_number"06763121"
court"High Court of Justice" (when in the notice)
case_number"CR-2026-001234" (when in the notice)
registered_office(when in the notice)
notice_urlhttps://www.thegazette.co.uk/notice/5203210
scraped_at"2026-09-03T09:00:00.000Z"

Webhook payload

POST <webhookUrl>
{ "source": "uk-insolvency-monitor", "scope": "corporate",
"window": { "from": "2026-09-02", "to": "2026-09-03" },
"count": 7, "notices": [ /* same objects as dataset items */ ] }

Webhook failure is logged, not fatal — the data is still in the dataset.

How incremental mode works

Cross-run state (seen notice IDs + last-run time) lives in a named key-value store, uk-insolvency-monitor-state, namespaced by a hash of scope + text so multiple schedules on this actor keep separate state. Runs after the first fetch from the day before the previous run up to today (Gazette publish dates), then drop every notice ID already seen. The seen-set is capped at 30,000 IDs (~2 weeks of all UK insolvency notices).

Notes on The Gazette API

  • No key, no auth, free — data published under the Open Government Licence.
  • The API returns intermittent HTTP 500s; this actor retries transient failures (3 attempts, exponential backoff) and, if it still fails mid-run, pushes what it has and resumes from there next run (partial: true in the summary).
  • Corporate vs personal is a client-side filter on the notice code (24xx = corporate, 25xx = personal) because the Gazette search API only accepts one notice-type per request.

Local development

npm install
npm test # 15 unit tests, fully mocked
echo '{"scope":"corporate","firstRunLookbackDays":3}' > storage/key_value_stores/default/INPUT.json
npm start

Deploy your own copy

$npm i -g apify-cli && apify login && apify push

Data source & licensing

Data comes from The Gazette (thegazette.co.uk), the UK's official public record of record, published by The Stationery Office on behalf of HM Government. Notices are Crown copyright, published under the Open Government Licence v3.0.

Part of a small suite of UK public-register monitors, same publisher, same pattern (incremental, no duplicates, webhook-ready):


Changelog

  • 0.1 — Initial release: corporate/personal/all scope, text filter, incremental dedup, notice-detail enrichment, webhook, transient-error retry.