# UK Gazette Insolvency - Company Winding-Up & Liquidation (`j0401/uk-gazette-insolvency`) Actor

Corporate insolvency notices from The Gazette (UK public record): winding-up orders and petitions, liquidator appointments, meetings and dividends, with company number and official notice link. Personal insolvency excluded.

- **URL**: https://apify.com/j0401/uk-gazette-insolvency.md
- **Developed by:** [Wenhao Yang](https://apify.com/j0401) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.03 / 1,000 uk corporate insolvency notices

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Insolvency - Company Winding-Up & Liquidation

Corporate insolvency notices from **The Gazette**, the UK's official public
record: the earliest public signal that a company is in trouble. The 23-25
October 2026 scan (Friday-Sunday) carried **about 500 corporate notices**
across about a dozen notice types; a busy three-weekday window carries
roughly 1,100-1,300, and a five-day weekday window about 1,700.

Included: winding-up orders and petitions, resolutions for winding up,
appointments of liquidators and administrators, meetings of creditors,
notices to creditors, notices of dividends, final meetings.

**Personal insolvency is excluded.** Bankruptcy orders, individual voluntary
arrangements and individual dividends are personal data and never appear in
this dataset. For one corporate type (2403, re-use of a prohibited name) the
free-text body is not published because the statutory template can name an
individual.

### Low cost

**From $0.00005 per record, down to $0.00003 at Gold.** Pay only for the
notices or aggregate rows you receive.

### What you get per notice

| field | meaning |
|---|---|
| `noticeId`, `noticeUrl` | the Gazette notice ID and its official page |
| `companyName` | the company the notice is about |
| `companyNumber` | Companies House number where the notice states one |
| `noticeType`, `noticeCode` | e.g. `Winding-Up Orders` / `2452`, `Appointment of Liquidators` / `2443` |
| `published`, `updated` | publication timestamp |
| `registeredOffice`, `principalTradingAddress` | the registered-office / principal-trading address where the notice states it (not every notice does; capped at 300 characters) |
| `content` | the notice body as plain text (capped at 4,000 characters) |
| `latitude`, `longitude` | the notice's location where the Gazette supplies one |
| `windowStart`, `windowEnd` | the scan window |

### Search it

- **Company** - `company="HEMEL"` (substring).
- **Company number** - `companyNumber="09241129"` (exact).
- **Notice type** - `noticeType="Petitions to Wind Up"`, `"Appointment of Liquidators"`.
- **Notice code** - `noticeCode="2452"`.
- **Keyword** - `keyword="High Court"`.
- **Window** - `dateFrom="2026-10-21"`, `dateTo="2026-10-25"` (up to 5 days).

### Example inputs

**A company's insolvency trail**

```json
{ "company": "HEMEL ACCESS", "dateFrom": "2026-10-21", "dateTo": "2026-10-25",
  "maxResults": 50 }
```

**Winding-up orders in the last three days**

```json
{ "noticeType": "Winding-Up Orders", "maxResults": 100 }
```

**Everything mentioning one court**

```json
{ "keyword": "High Court", "dateFrom": "2026-10-22", "dateTo": "2026-10-25",
  "maxResults": 100 }
```

### Aggregate it

Set `groupBy` with no filters for the window summary. To combine it with
filters, set `mode:"aggregate"` explicitly (a filter without `mode` routes to
the record search):

```json
{ "mode": "aggregate", "groupBy": "day" }
```

`groupBy` = `noticeType` (default), `noticeCode` or `day`. Every row carries
`groupKey`, `groupCount`, `groupBy` and `totalMatched`.

The default (empty) run scans the last three days and returns the
notice-type summary.

### Scan window and rate limit

The Gazette sets **`Crawl-delay: 10`** in robots.txt, so this actor waits ten
seconds between requests and scans **at most 5 days per run** (3 days by
default). For longer histories, run consecutive windows.

### Source and licence

The Gazette, published by The Stationery Office under the **Open Government
Licence v3**. The licence does not cover personal data, which is why personal
insolvency notices are excluded.

Source: [The Gazette insolvency notices](https://www.thegazette.co.uk/insolvency/notice).

# Actor input Schema

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

search = corporate notices matching your filters. aggregate = one row per group. Leave blank to auto-route: filters -> search, no filters -> aggregate.

## `company` (type: `string`):

Company name substring, case-insensitive (e.g. "HEMEL").

## `companyNumber` (type: `string`):

Exact company number where the notice states one (e.g. "09241129").

## `noticeType` (type: `string`):

Notice type or code substring (e.g. "Winding-Up Orders", "Appointment of Liquidators", "Petitions to Wind Up").

## `noticeCode` (type: `string`):

Exact Gazette notice code, e.g. "2452" (winding-up order) or "2443" (appointment of liquidators).

## `keyword` (type: `string`):

Free-text substring in the notice body (e.g. "High Court", a trading name, a town).

## `dateFrom` (type: `string`):

Window start, YYYY-MM-DD. Defaults to three days before dateTo.

## `dateTo` (type: `string`):

Window end, YYYY-MM-DD. Defaults to today. The window may not exceed 5 days (the Gazette sets a 10-second crawl delay).

## `groupBy` (type: `string`):

noticeType -> the notice category; noticeCode -> the Gazette code; day -> publication date. Blank defaults to noticeType.

## `maxResults` (type: `integer`):

Cap the number of search records pushed (0 = the default 50, maximum 2000). Aggregate returns every group.

## Actor input object example

```json
{
  "maxResults": 50
}
```

# Actor output Schema

## `recordsUrl` (type: `string`):

UK corporate insolvency notice records - as JSON

## `datasetUrl` (type: `string`):

No description

## `runUrl` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("j0401/uk-gazette-insolvency").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("j0401/uk-gazette-insolvency").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 '{}' |
apify call j0401/uk-gazette-insolvency --silent --output-dataset

```

## MCP server setup

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

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/qVcFGH5hExzAGIIeg/builds/8qKOPOVLPMPQi2H3G/openapi.json