# UK Company Changes: Strike-offs, Liquidations & Status Feed (`eythan/uk-company-changes`) Actor

Monthly feed of status changes at UK Companies House companies: strike-off proposals, liquidations, administrations, SIC and name changes. Company-level only, no personal data.

- **URL**: https://apify.com/eythan/uk-company-changes.md
- **Developed by:** [Eythan Cohen](https://apify.com/eythan) (community)
- **Categories:** Business, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 company changes

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 Company Changes: Strike-offs, Liquidations & Status Feed

**Find UK companies heading for liquidation, administration or strike-off, every month. Filter by industry (SIC), postcode or company number.**

Every month Companies House publishes the whole UK company register. This Actor compares the
months for you and returns only what **changed**: companies proposed for strike-off, entering
liquidation or administration, changing industry code or name, or newly appearing. No scraping,
no login, no personal data.

**Who uses it**

- **Credit control and supplier risk:** find out when a customer or supplier enters liquidation.
- **Insolvency and turnaround professionals:** build a monthly list of distressed companies in a sector or area.
- **Analysts and researchers:** count business births and failures by industry and postcode.
- **AI agents:** a single reliable "did anything happen to this company?" tool.

### What does this Actor do?

Every month Companies House publishes a free snapshot of every company on the register. This Actor
compares consecutive snapshots and returns the **differences** as one record per change, so you do
not have to download and diff 5 million rows yourself.

- **Status moves**: for example Active to "Active - Proposal to Strike off", or to Liquidation.
- **Filter** by new status, SIC code prefix, postcode area, company number, name text and date range.
- **Company-level only**: no director, officer or shareholder (PSC) data and no street addresses.
- **No scraping and no login**: it uses Companies House's official free bulk data.

### How to use it

1. Open the **Input** tab and choose event types (default: status changes).
2. Optionally narrow by new status (for example `Liquidation`), SIC prefix (`62` for IT), or postcode area (`EC1`).
3. Set **Maximum results** and run. Results appear in the **Output** tab and via the API.

### Example inputs (copy, paste, run)

Counts are what these return against the data bundled today (August to October 2026).

**1. Companies that entered liquidation or administration in the latest month** (credit control)

```json
{"eventTypes": ["status_change"], "statusTo": ["Liquidation", "In Administration"], "dateFrom": "2026-10-01", "maxResults": 5000}
```

Returns about 2,470 companies, for example GREENS MOTORS LTD (Active to In Administration).

**2. IT companies with a strike-off proposal in the EC postcode area** (sector and area screening)

```json
{"eventTypes": ["status_change"], "statusTo": ["Active - Proposal to Strike off"], "sicPrefixes": ["62"], "postcodeAreas": ["EC"], "maxResults": 5000}
```

Returns about 960 companies across the two months.

**3. New restaurant and food-service companies in the latest month** (market entry tracking)

```json
{"eventTypes": ["new_company"], "sicPrefixes": ["56"], "dateFrom": "2026-10-01", "maxResults": 10000}
```

Returns about 4,700 newly appearing companies.

**4. Watch a list of companies for any change** (supplier monitoring)

```json
{"eventTypes": ["status_change", "name_change", "sic_change"], "companyNumbers": ["00076181", "00444860"], "maxResults": 100}
```

Returns every status, name or industry change for exactly those company numbers.

Run any of these on a schedule (Apify Schedules) and connect the results to email, Slack or a
webhook to get a monthly alert.

### Input

| Field | Meaning |
|---|---|
| `eventTypes` | status_change, new_company, name_change, sic_change, accounts_category_change, charges_change, category_change, dissolution_date_set |
| `statusTo` | only status changes into these statuses, for example `["Liquidation"]` |
| `dateFrom` / `dateTo` | monthly snapshot dates, `YYYY-MM-DD` |
| `sicPrefixes` | SIC codes starting with, for example `["62", "6820"]` |
| `postcodeAreas` | registered-office postcode prefixes, for example `["EC1", "M"]` |
| `companyNumbers` | specific company numbers |
| `nameContains` | text the company name must contain |
| `maxResults` | cap on records returned (you are charged per record returned) |

### Output example

```json
{
  "snapshotDate": "2026-10-01",
  "previousSnapshotDate": "2026-09-01",
  "eventType": "status_change",
  "companyNumber": "00444860",
  "companyName": "EXAMPLE COMPANY LIMITED",
  "field": "status",
  "oldValue": "Active",
  "newValue": "Liquidation",
  "currentStatus": "Liquidation",
  "category": "Private Limited Company",
  "sicCodes": ["62020 - Information technology consultancy activities"],
  "postTown": "LONDON",
  "postcodeOutward": "EC1V",
  "companyUrl": "https://find-and-update.company-information.service.gov.uk/company/00444860",
  "source": "Companies House"
}
```

### Pricing

Pay per result: you are charged for each change record returned, plus a tiny start fee. Use
`maxResults` to cap a run. You are never charged for records you do not receive.

### Good to know (limits)

- **Monthly granularity.** Changes are found by comparing monthly snapshots. This is not a real-time
  feed, and an event shows the snapshot in which it was first seen, not the exact filing date.
- **`removed_from_snapshot`** means the company no longer appears on Companies House's live-company
  snapshot (typically because it has been dissolved). Treat it as a strong signal, not a legal finding.
- **Coverage depends on available snapshots**; see `SUMMARY` in the run's key-value store for the
  snapshot dates included.
- **Companies House data is published free of charge** at download.companieshouse.gov.uk. This Actor
  adds the diffing, filtering and API delivery.

### Is it legal?

The data comes from Companies House's official free bulk download, which states it imposes no rules
on how register information is used and that users are responsible for complying with data
protection, copyright and other law. This Actor returns company-level fields only and deliberately
excludes officers, PSCs and street addresses. You remain responsible for your own use of the data,
including compliance with the UK GDPR if you combine it with personal data.

### Disclaimer

Not affiliated with, endorsed by or certified by Companies House. Information is provided as is, without
warranty, and is not legal, credit or financial advice. Contains public sector information published
by Companies House.

### Feedback

Found a wrong status, a missing filter, or want another register covered? Open an issue from the
Actor page.

# Actor input Schema

## `eventTypes` (type: `array`):

Which kinds of change to return. 'status_change' covers strike-off proposals, liquidations and administrations.

## `statusTo` (type: `array`):

Only return status changes INTO one of these statuses, e.g. 'Liquidation' or 'Active - Proposal to Strike off'. Leave empty for all.

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

Earliest monthly snapshot to include, format YYYY-MM-DD (snapshots are dated the 1st of each month).

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

Latest monthly snapshot to include, format YYYY-MM-DD.

## `sicPrefixes` (type: `array`):

Only companies whose SIC codes start with one of these, e.g. '62' (IT) or '6820' (real estate rental).

## `postcodeAreas` (type: `array`):

Only companies whose registered-office postcode starts with one of these outward-code prefixes, e.g. 'EC1', 'M', 'LS'.

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

Only these Companies House company numbers (8 characters, e.g. '08209948').

## `nameContains` (type: `string`):

Case-insensitive text the current company name must contain.

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

Stop after this many events. You are only charged for events returned.

## Actor input object example

```json
{
  "eventTypes": [
    "status_change"
  ],
  "statusTo": [
    "Liquidation",
    "In Administration"
  ],
  "dateFrom": "",
  "dateTo": "",
  "sicPrefixes": [],
  "postcodeAreas": [],
  "companyNumbers": [],
  "nameContains": "",
  "maxResults": 50
}
```

# Actor output Schema

## `changes` (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 = {
    "eventTypes": [
        "status_change"
    ],
    "statusTo": [
        "Liquidation",
        "In Administration"
    ],
    "maxResults": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("eythan/uk-company-changes").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 = {
    "eventTypes": ["status_change"],
    "statusTo": [
        "Liquidation",
        "In Administration",
    ],
    "maxResults": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("eythan/uk-company-changes").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 '{
  "eventTypes": [
    "status_change"
  ],
  "statusTo": [
    "Liquidation",
    "In Administration"
  ],
  "maxResults": 50
}' |
apify call eythan/uk-company-changes --silent --output-dataset

```

## MCP server setup

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

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/UyQLuKRFq8QnXgUlS/builds/2aSJn622DCyMbhZcv/openapi.json