# UK Insolvency Notice Alerts: Gazette Winding-Up Petitions (`accountable_eel/uk-insolvency-notice-alerts`) Actor

Every new UK corporate insolvency notice in The Gazette: winding-up petitions and orders, administrations, liquidations, by type, keyword or company number. Monitor The Gazette for winding up petitions: only-new alerts to Slack, Discord or Telegram, or UK administration notices to Google Sheets.

- **URL**: https://apify.com/accountable_eel/uk-insolvency-notice-alerts.md
- **Developed by:** [Adriana Voss](https://apify.com/accountable_eel) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.00 / 1,000 insolvency notice returneds

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 Insolvency Notice Alerts: Gazette Winding-Up Petitions

Every new UK corporate insolvency notice in The Gazette: winding-up petitions and orders,
administrations and liquidations, filtered by type, keyword or company number. Personal
bankruptcy notices are never returned. Only-new-notice alerts for credit control and
trade-credit teams, with optional Discord, Slack or Telegram delivery. Charged per notice found.

### How to use

1. **In the Apify Console.** Open the actor page and click **Start** — the `companyNumbers` field is already pre-filled with a working example. Results land in the run's dataset as soon as each item is found.
2. **Via the API.** Call it directly with a POST request — no Console needed once you have an API token:
   ```bash
   curl "https://api.apify.com/v2/acts/accountable_eel~uk-insolvency-notice-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
     -X POST \
     -H "Content-Type: application/json" \
     -d '{"companyNumbers":[""]}'
   ```
3. **On a schedule.** Save this actor as an Apify **Task** with the input you want, then add a **Schedule** (hourly, daily, weekly) so it runs on its own — no server of your own required.

### Input

```json
{
  "companyNumbers": [
    ""
  ]
}
```

Optional. One Companies House number per line (8 characters, e.g. 08706800 or SC123456). Leave empty to watch every corporate notice of the chosen type. Accepted formats: 08706800, SC123456.

`noticeTypes` picks the Gazette notice family (winding-up petition by default). Optional
`keywords` and `companyNumbers` narrow the feed. `sinceDays` defaults to 3. Turn on
`onlyNewSinceLastRun` for monitoring.

### Output

| query | found | status | searchSummary | noticeCount | notices | noticeId | title | noticeCode | noticeType | sourceName | companyName | companyNumber | publishedAt | summary | petitionHearingDate | courtOrInsolvencyPractitioner | url | companiesHouseUrl | isNew | firstSeenAt | scrapedAt |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
|  | true | OK | <search run> | <notices returned> | \<all notices (full list)> | <gazette notice id> | <headline> | <gazette notice code> | <notice type> | \<notice label (as published)> | <company name> | <company number> | <published> | <notice summary> | <hearing date> | <court> | <gazette notice> | <companies house page> | \<is this notice new?> | <first seen on a run> | 1970-01-01T00:00:00.000Z |

One row per corporate notice. Personal (25xx) notices are dropped before billing.

### Example runs

For UK credit-risk and trade-credit monitors. Change the field named in each note.

**1. Winding-up petitions, only new (who: credit control)** — change `noticeTypes` / monitoring

```json
{ "noticeTypes": "winding-up-petition", "onlyNewSinceLastRun": true }
```

**2. Administrations this week (who: trade-credit team)** — change `noticeTypes`

```json
{ "noticeTypes": "administration", "sinceDays": 7 }
```

**3. Watchlist by company number (who: portfolio risk)** — change `companyNumbers`

```json
{ "companyNumbers": ["01234567"], "noticeTypes": "all-corporate" }
```

### Pricing

### Related actors

- [UK Companies House API: Company Data & Officers](https://apify.com/accountable_eel/companies-house-uk-lookup): full company data and officers for the company behind a notice.

### Use it from Clay, n8n, Make, or an AI agent

This actor runs synchronously over plain HTTP — call it directly from a script, a workflow tool, or an AI agent, no Apify Console needed once you have an API token.

```bash
curl "https://api.apify.com/v2/acts/accountable_eel~uk-insolvency-notice-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>" \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"companyNumbers":[""]}'
```

**n8n.** Add an HTTP Request node: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~uk-insolvency-notice-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body Content Type `JSON`, JSON Body `{"companyNumbers":[""]}` (swap in an expression from an earlier node for a real value).

**Clay.** Add an "HTTP API" column: Method `POST`, URL `https://api.apify.com/v2/acts/accountable_eel~uk-insolvency-notice-alerts/run-sync-get-dataset-items?token=<YOUR_TOKEN>`, Body `{"companyNumbers":["{{notice}}"]}`, mapping the row's notice into the `companyNumbers` array.

**MCP.** In Claude, Cursor, or any MCP client with the Apify MCP server, ask for "UK Gazette insolvency notice alerts" — the agent will find and run this actor.

# Actor input Schema

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

Optional. One Companies House number per line (8 characters, e.g. 08706800 or SC123456). Leave empty to watch every corporate notice of the chosen type. Accepted formats: 08706800, SC123456. You're only charged for the ones we actually find — a miss costs nothing.

## `noticeTypes` (type: `string`):

Personal insolvency (bankruptcy orders, IVAs) is never returned. Receivership and moratorium notices are not offered yet: their Gazette codes were not in the sample this actor was built from.

## `keywords` (type: `array`):

Optional. One per line. A notice is kept when its company name or notice text contains any of them (case-insensitive).

## `sinceDays` (type: `integer`):

1 to 60. The Gazette publishes insolvency notices every working day; the window is counted back from today.

## `testRun` (type: `boolean`):

Turn this on to test your input on a small sample before running the full list. Turn it off to process everything.

## `onlyFound` (type: `boolean`):

Only keep rows where something was actually found. Misses are always free, whether or not you show them here.

## `includeKeywords` (type: `array`):

Optional. Only keep results that mention at least one of these words (e.g. a job title, a city, a product name). Leave empty to keep everything.

## `excludeKeywords` (type: `array`):

Optional. Drop any result that mentions one of these words. Leave empty to skip nothing.

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

Optional. Stop the run once this many results have been found — useful for a quick, cheap sample. Leave blank for no limit.

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

Turns this actor into an insolvency alert. A notice counts as new when its Gazette notice ID has not been returned for this watchlist before. Already-seen notices are dropped before you are billed. The first run returns up to your cap and remembers the rest of the window.

## `deltaName` (type: `string`):

Leave empty and the memory is kept per notice type, keywords and company numbers. Type your own name to keep two schedules apart.

## `quietRunOutput` (type: `string`):

A quiet run is a search with no new notices. 'Nothing' writes zero items, so an integration never has to skip rows.

## `notifyUrl` (type: `string`):

Optional, needs monitoring on. After the notices are billed, each new notice is posted here as one message: headline, date, link and summary. Discord or Slack: paste the channel's webhook URL. Telegram: https://api.telegram.org/bot<token>/sendMessage?chat_id=<chat id>. Any other URL receives JSON. Messages are free, and a message that fails never fails the run (the row's notifyErrors says why). Stored encrypted, never logged or written to the results.

## `notifyFormat` (type: `string`):

Leave on "Detect from the link": discord.com links get Discord messages, hooks.slack.com Slack, api.telegram.org Telegram, anything else JSON.

## `maxNotificationsPerRun` (type: `integer`):

Up to 100. Above this, one "+N more" message says how many more notices are in the run's dataset.

## `columns` (type: `array`):

Choose which pieces of information to include in each result row. All are included by default.

## `expandRows` (type: `boolean`):

When on, each notice found gets its own row instead of being grouped under its notice. You're still only charged once per notice, no matter how many rows it produces.

## `maxConcurrency` (type: `integer`):

Parallel requests. Keep conservative — this target has no browser fallback, so getting blocked costs more than slow-and-steady.

## Actor input object example

```json
{
  "companyNumbers": [],
  "noticeTypes": "all-corporate",
  "keywords": [],
  "sinceDays": 3,
  "testRun": false,
  "onlyFound": false,
  "includeKeywords": [],
  "excludeKeywords": [],
  "onlyNewSinceLastRun": false,
  "deltaName": "",
  "quietRunOutput": "summary",
  "notifyFormat": "auto",
  "maxNotificationsPerRun": 20,
  "columns": [
    "searchSummary",
    "noticeCount",
    "notices",
    "noticeId",
    "title",
    "noticeCode",
    "noticeType",
    "sourceName",
    "companyName",
    "companyNumber",
    "publishedAt",
    "summary",
    "petitionHearingDate",
    "courtOrInsolvencyPractitioner",
    "url",
    "companiesHouseUrl",
    "isNew",
    "firstSeenAt"
  ],
  "expandRows": true,
  "maxConcurrency": 5
}
```

# Actor output Schema

## `results` (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 = {
    "companyNumbers": [],
    "keywords": [],
    "includeKeywords": [],
    "excludeKeywords": []
};

// Run the Actor and wait for it to finish
const run = await client.actor("accountable_eel/uk-insolvency-notice-alerts").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 = {
    "companyNumbers": [],
    "keywords": [],
    "includeKeywords": [],
    "excludeKeywords": [],
}

# Run the Actor and wait for it to finish
run = client.actor("accountable_eel/uk-insolvency-notice-alerts").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 '{
  "companyNumbers": [],
  "keywords": [],
  "includeKeywords": [],
  "excludeKeywords": []
}' |
apify call accountable_eel/uk-insolvency-notice-alerts --silent --output-dataset

```

## MCP server setup

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

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/AAz28lyNb26E8TP30/builds/2Y1btKzH9ZEoHVy4D/openapi.json