# UK Gazette Insolvency Monitor: Winding-Up Alerts (`automatic/uk-gazette-insolvency-monitor`) Actor

Know the day a UK customer or supplier goes into insolvency. Official Gazette winding-up petitions, administrations and liquidations with company number, petitioner, practitioner contacts, claims deadlines and risk flags. Schedule it: each run delivers only new notices.

- **URL**: https://apify.com/automatic/uk-gazette-insolvency-monitor.md
- **Developed by:** [Philip Kirkbride](https://apify.com/automatic) (community)
- **Categories:** Business, Lead generation
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $7.00 / 1,000 notices

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## UK Gazette Corporate Insolvency Monitor

Know the day a UK customer, supplier or borrower goes into insolvency. Every official corporate insolvency notice from The Gazette arrives as one clean row: who it is (company number and Companies House link), what happened (winding-up petition, order, administration, liquidation, creditor meeting), who is acting (the insolvency practitioner or petitioner with their published phone and email) and what is due (hearing, claims and meeting deadlines).

- **Only new notices on a schedule.** Run it daily and each run delivers only the notices you have not received before, never a repeat. A quiet day costs only the run start.
- **Bad news flagged.** Every row says `isAdverse` and a plain `riskSignal` such as `windingUpPetition` or `administratorAppointed`. Turn on `onlyAdverse` and solvent liquidations and dismissed petitions are skipped and not charged.
- **Watch your own book.** Up to 50 company numbers (with or without leading zeros, or pasted as Companies House links) or 20 company names, matched against current, previous and trading names.
- **Ready to act on.** Petitioner, court and case number, hearing date and place, office holders with IP numbers, firms and addresses, the last date to prove a debt, and the full notice text.
- **Straight into your tools.** Slack, email, Google Sheets or your own webhook through Apify integrations.

Built for credit controllers, trade-credit insurers, lenders, factoring and invoice-finance teams, debt buyers and insolvency practitioners.

**Run it with `{}` or the prefilled input for a quick sample of current notices.** Empty input returns the 10 newest corporate insolvency notices, marked `usedExample: true` in OUTPUT.

### Use cases

- **Credit control:** stop shipping on credit the day a customer's winding-up petition is advertised.
- **Supplier risk:** learn when a key supplier appoints administrators, before deliveries stop.
- **Debt recovery:** submit your claim before the published claims deadline, with the liquidator's contact in the same row.
- **Lending and insurance:** feed adverse events for your portfolio into your risk system every morning.
- **Business development:** see which practitioners and law firms are acting, and where, as notices are published.

### What you get

- Notice ID, link, official notice code and type, publication time in UTC, edition (London, Edinburgh or Belfast), and issue and page once assigned.
- `isAdverse`, `riskSignal` and `insolvencyProceeding` (compulsory liquidation, creditors' or members' voluntary liquidation, administration, receivership, moratorium) for alert routing.
- Company name, registration number and Companies House link, previous and trading names, registered office and nature of business when published.
- Court, case number, petitioner and hearing place for court proceedings.
- Office holders (liquidators, administrators, official receivers) and the petitioner's solicitor, with IP numbers, firms and addresses, plus the published contact name, phone numbers and email addresses.
- Dates: hearing, last day to give notice of appearance, petition filed, winding-up order, appointment, resolution, creditors' meeting or decision, claims deadline, and every other date marked in the notice.
- The full notice text as published, and a stable `idempotencyKey` per notice for your CRM or data warehouse.

### Also available

The company registry suite: pick the job.

| Actor | Use when |
|---|---|
| **UK Gazette Insolvency Monitor (this Actor)** | UK winding-up, administration and liquidation alerts |
| [UK Companies House](https://apify.com/automatic/companies-house-scraper) | UK company profiles, officers and filings |
| [UK Companies House Bulk](https://apify.com/automatic/uk-companies-house-bulk) | Filter UK companies by SIC and area |
| [Northdata Company Monitor](https://apify.com/automatic/northdata-company-monitor) | European register notices and company changes |
| [Sanctions & AML Screener](https://apify.com/automatic/opensanctions-screener) | Screen names and wallets against sanctions lists |

### Output example

A winding-up petition from a run on 15 November 2026:

```json
{
  "noticeId": "5252906",
  "noticeUrl": "https://www.thegazette.co.uk/notice/5252906",
  "noticeCode": "2450",
  "noticeType": "Petitions to Wind Up (Companies)",
  "eventGroup": "windingUpPetitions",
  "isAdverse": true,
  "riskSignal": "windingUpPetition",
  "insolvencyProceeding": "compulsoryLiquidation",
  "category": "Corporate Insolvency",
  "publishedAt": "2026-11-13T14:50:26Z",
  "edition": "London",
  "issueNumber": null,
  "pageNumber": null,
  "companyName": "BIG SOUP RESIDENTIAL LIMITED",
  "companyNumber": "12016534",
  "companiesHouseUrl": "https://find-and-update.company-information.service.gov.uk/company/12016534",
  "previousCompanyNames": [],
  "tradingNames": [],
  "registeredOffice": null,
  "natureOfBusiness": null,
  "otherCompanies": [],
  "court": "HIGH COURT OF JUSTICE",
  "courtCaseNumber": "CR-2026-LDS-001032",
  "petitioner": "THE BIG SOUP THEATRE GROUP LIMITED",
  "hearingPlace": "Business and Property Courts in Leeds, Fourth Floor, West Gate, 6 Grace Street, Leeds, LS1 2RP",
  "practitioners": [],
  "firms": [
    "Addleshaw Goddard LLP"
  ],
  "contactName": null,
  "contactPhones": [
    "0113 209 2550"
  ],
  "contactEmails": [
    "conor.mcdermott@addleshawgoddard.com"
  ],
  "hearingDate": "2026-11-24",
  "appearanceDeadline": "2026-11-23",
  "petitionFiledDate": "2026-10-12",
  "windingUpOrderDate": null,
  "appointmentDate": null,
  "resolutionDate": null,
  "meetingDate": null,
  "claimsDeadline": null,
  "otherDates": [
    "2026-11-23"
  ],
  "noticeText": "In the HIGH COURT OF JUSTICE BUSINESS AND PROPERTY DIVISION INSOLVENCY AND COMPANIES LIST IN LEEDS Court Number: CR-2026-LDS-001032 In the Matter of BIG SOUP RESIDENTIAL LIMITED (Company Number 12016534) (THE \"COMPANY\") and in the Matter of the INSOLVENCY ACT 1986 A Petition to wind-up the above-named Company (registered number 12016534) of 1st Floor, Crown Works, Luton Street, Keighley, England, BD21 2LE presented on 12 October 2026 by THE BIG SOUP THEATRE GROUP LIMITED (registered number 06582704) of Crown Works, Luton Street, Keighley, England, BD21 2LE (the \"Petitioner\") claiming to be a creditor of the Company will be heard at the Business and Property Courts in Leeds, Fourth Floor, West Gate, 6 Grace Street, Leeds, LS1 2RP. Date: 24 November 2026 Time: 10:00 hours (or as soon thereafter as the Petition can be heard) Any person intending to appear on the hearing of the Petition (whether to support or oppose it) must give notice of intention to do so to the Petitioner or their solicitors in accordance with Rule 7.14 of the Insolvency (England and Wales) Rules 2016, SI 2016/1024 by 16.00 hours on 23 November 2026. The Petitioner's Solicitor is: Addleshaw Goddard LLP, 3 Sovereign Square Sovereign Street Leeds LS1 4ER. Telephone: 0113 209 2550 E-mail: conor.mcdermott@addleshawgoddard.com Ref: MCDECB/413288-1. Dated: 10 November 2026",
  "country": "GB",
  "source": "The Gazette",
  "detailsIncluded": true,
  "idempotencyKey": "uk-gazette:notice:5252906",
  "scrapedAt": "2026-11-15T03:46:42Z"
}
```

### Choose your notices

Pick notice types and a date range:

```json
{
  "noticeTypes": ["windingUpPetitions", "windingUpOrders", "administration"],
  "publishedFrom": "2026-11-06",
  "publishedTo": "2026-11-13",
  "maxItems": 500
}
```

Or check specific companies by number, link or name across the last year:

```json
{
  "companyNumbers": ["06743749", "SC707504", "https://find-and-update.company-information.service.gov.uk/company/05282362"],
  "companyNames": ["Saki Snacks (Midlands) Ltd"]
}
```

| Input | Meaning |
| --- | --- |
| `noticeTypes` | `windingUpPetitions`, `windingUpOrders`, `courtLiquidation`, `administration`, `receivership`, `creditorsVoluntaryLiquidation`, `membersVoluntaryLiquidation`, `otherCorporateInsolvency`. Empty keeps every corporate type. |
| `noticeCodes` | Exact four-digit Gazette codes such as `2450`, combined with `noticeTypes`. |
| `publishedFrom`, `publishedTo` | UK publication dates, inclusive. Default: the last 7 days up to today, or the last year when you watch company numbers or names. Up to 366 days per run. |
| `companyNumbers` | Up to 50 UK companies: `06743749`, `6743749`, `CRN 06743749`, `SC707504` or a Companies House link. Entries that are not company numbers are skipped and named in the run status. |
| `companyNames` | Up to 20 names, matched against current, previous and trading names. Ltd or Limited, "The", "&" or "and" and punctuation do not matter. A name with its legal form ("Acme Ltd") finds that company; without it ("Acme"), every company whose name contains those whole words. A company number typed here is used as a number. |
| `onlyAdverse` | Default false. Skip members' (solvent) voluntary liquidations and dismissed winding-up petitions; skipped notices are not charged. |
| `maxItems` | Maximum rows per run. Default 200. A typical week has about 1,500 to 2,000 corporate notices. |
| `includeDetails` | Default true. Set false for a much faster list with company name, notice type, date and risk flags, plus the company number when the list shows it (about half of notices). Watchlist matches are still checked against the notice. |

Empty values (`[]` or `""`) behave like omitted fields. Unknown fields are ignored and named in the run status. Invalid values end the run without results and with a message naming the field.

### Scheduled monitoring

Turn on `onlyNewSinceLastRun` and give each watchlist its own `ledgerName`. Each run delivers only notices that ledger has not delivered before, oldest first, and continues where the previous run stopped.

```json
{
  "noticeTypes": ["windingUpPetitions", "windingUpOrders", "administration"],
  "onlyAdverse": true,
  "onlyNewSinceLastRun": true,
  "ledgerName": "client-a-petitions",
  "maxItems": 1000
}
```

- The first run delivers the last 7 days, or from `publishedFrom`. Set `bootstrapMode` to `baseline` to start with future notices only.
- Each run looks back `overlapHours` (default 48) for notices published late. Delivered notices are never repeated.
- If a run stops at `maxItems` or its spending limit, the next run delivers the rest.
- To change a ledger's filters, use a new `ledgerName` or set `resetLedger` once.

OUTPUT reports `status` (`complete`, `no_results`, `partial` or `failed`), `new`, `unchanged`, `pending`, `skippedNotAdverse`, `watermarkBefore`, `watermarkAfter`, `complete`, `warnings`, `inputWarnings` and errors for every run.

### Get alerts in Slack, email or your own system

Save your input as a task, add a daily schedule, then open the task's **Integrations** tab:

- **Slack** or **email**: get a message when a run finishes, with a link to the new notices.
- **Webhook**: receive the run ID and read the new rows from the dataset in your own system.
- **Google Sheets**, Make, Zapier or n8n: append each day's new notices to a sheet or a workflow.

With monitoring on, each day's dataset holds only that day's new notices, so every alert is news.

### Pricing

**$0.007 per notice ($7.00 per 1,000) plus $0.005 per run start.** One result is one saved notice row. Skipped, already delivered and failed notices are not charged. The start fee is charged per GB of memory, with a minimum of one; the default 512 MB run is one start event.

| Example at 512 MB | Notices | Cost |
| --- | ---: | ---: |
| Console prefill | 10 | $0.075 |
| Daily monitor with about 20 new notices | 20 | $0.145 |
| Daily monitor with nothing new | 0 | $0.005 |
| 1,000 notices in one run | 1,000 | $7.005 |

Use `maxItems` and the run's spending limit to cap the cost.

### Good to know

- Corporate insolvency notices only. Personal insolvency, bankruptcy and partnership notices are never collected.
- Company strike-off and dissolution notices are not included. Company numbers are given as printed in the notice and linked to Companies House; no Companies House lookup is made.
- `isAdverse` and `riskSignal` follow the official notice code; for general notices (dividends, decisions) the kind of liquidation is read from the notice wording and can be null.
- Petitioner, hearing place, deadlines and contacts are read from the published wording. Unusual wording can leave a field empty; the full `noticeText` and the notice link are always there.
- CVAs and moratoriums appear when the Gazette files them under a corporate insolvency code, mostly under `otherCorporateInsolvency`.
- With full details, about one notice per second is collected, so a week of every type takes about 25 minutes. The default one-hour timeout fits about 3,000 notices; a run near its limit stops cleanly with what it has. Switch `includeDetails` off for a list in seconds.
- Monitoring delivers each notice at most once. A run interrupted mid-delivery can skip a few notices; run once without monitoring for that window to backfill. A notice that cannot be read in three runs is skipped and named in OUTPUT warnings. Corrections published to a notice that was already delivered are not sent again.
- Northern Ireland notices often carry fewer structured details, so court and dates can be empty; the notice link always works.
- Only one run can use a ledger at a time; an overlapping run returns nothing and says so.

# Actor input Schema

## `noticeTypes` (type: `array`):

Corporate insolvency notice types to keep, for example winding-up petitions and administrations. Leave empty for every corporate type.

## `publishedFrom` (type: `string`):

First publication date (UK), for example 2026-11-01. Empty means 7 days before the end date, or one year when watching companies. With monitoring, it sets only the first run's starting point.

## `publishedTo` (type: `string`):

Last publication date (UK), inclusive, for example 2026-11-13. Empty means today. Not used with monitoring.

## `companyNumbers` (type: `array`):

UK companies to watch, for example 06743749, SC707504, CRN 6743749 or a Companies House link. Up to 50. Leading zeros may be omitted; entries that are not company numbers are skipped with a note.

## `companyNames` (type: `array`):

Company names to watch, for example Saki Snacks (Midlands) Ltd. Ltd or Limited, The, & or and, and punctuation do not matter. With the legal form it finds that company; without it, any company whose name contains those whole words. Matches current, previous and trading names. Up to 20.

## `maxItems` (type: `integer`):

Maximum notice rows saved in one run, for example 500. A typical week has about 1,500 corporate insolvency notices.

## `includeDetails` (type: `boolean`):

Add court, case number, office holders, firms, registered office and key dates from each notice. Turn off for a faster list with company name, notice type and date (and the company number when the list shows it).

## `onlyAdverse` (type: `boolean`):

Skip solvent (members' voluntary) liquidations and dismissed winding-up petitions, for example for a credit-risk alert feed. Skipped notices are not charged.

## `onlyNewSinceLastRun` (type: `boolean`):

Deliver only notices this ledger has not delivered before, for example on a daily schedule. The first run delivers the last 7 days (or from Published from).

## `ledgerName` (type: `string`):

Name of the delivery history, for example client-a-watchlist. Use one name per set of filters; runs sharing a name must not overlap.

## `bootstrapMode` (type: `string`):

What the first run of a new ledger does, for example baseline to start with only future notices.

## `overlapHours` (type: `integer`):

Hours before the last delivered notice to look again for late-published notices, for example 48. Already delivered notices are never repeated.

## `resetLedger` (type: `boolean`):

Forget this ledger's history and start again, for example after changing filters. Use once, then switch off.

## `mode` (type: `string`):

Optional alias, for example monitor. Leave empty and use the monitoring switch instead.

## `noticeCodes` (type: `array`):

Four-digit corporate insolvency codes, for example 2450 for winding-up petitions. Combined with Notice types.

## Actor input object example

```json
{
  "noticeTypes": [
    "windingUpPetitions",
    "windingUpOrders",
    "administration"
  ],
  "maxItems": 10,
  "includeDetails": true,
  "onlyAdverse": false,
  "onlyNewSinceLastRun": false,
  "ledgerName": "uk-gazette-insolvency-ledger",
  "bootstrapMode": "emit",
  "overlapHours": 48,
  "resetLedger": false
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "noticeTypes": [
        "windingUpPetitions",
        "windingUpOrders",
        "administration"
    ],
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("automatic/uk-gazette-insolvency-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "noticeTypes": [
        "windingUpPetitions",
        "windingUpOrders",
        "administration",
    ],
    "maxItems": 10,
}

# Run the Actor and wait for it to finish
run = client.actor("automatic/uk-gazette-insolvency-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "noticeTypes": [
    "windingUpPetitions",
    "windingUpOrders",
    "administration"
  ],
  "maxItems": 10
}' |
apify call automatic/uk-gazette-insolvency-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,automatic/uk-gazette-insolvency-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/D3r0IHmfYDUUAtRmM/builds/SimoWmz7cw1MOYpJr/openapi.json
