# England & Wales Charity Register Change Signals (`starshaped_bullsnake/england-wales-charity-register-change-signals`) Actor

- **URL**: https://apify.com/starshaped\_bullsnake/england-wales-charity-register-change-signals.md
- **Developed by:** [Starshape Tools](https://apify.com/starshaped_bullsnake) (community)
- **Categories:** Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 charity register change signals

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

## England & Wales Charity Register Change Signals

**This is a change-intelligence Actor, not a current charity directory scraper.** It compares successive official Charity Commission bulk extracts and emits only meaningful organisation-level changes.

### Source and scope

The source is the Charity Commission for England and Wales [full register download](https://register-of-charities.charitycommission.gov.uk/en/register/full-register-download). The Charity Commission publishes a daily extract; this means the files are generated daily, not that every charity changes daily. The Actor uses the official `charity`, `charity_annual_return_history`, `charity_classification`, and `charity_area_of_operation` JSON ZIPs. All four must report the same `date_of_extract` or the run stops without replacing its snapshot.

Only main charities (`linked_charity_number = 0`) are primary entities. The stable public identity is `registered_charity_number`; `organisation_number` is retained only for safe joins. Linked/subsidiary charities are not independently emitted as primary entities in v1.

### Signals

- `NEW_CHARITY_REGISTERED`: first appears as explicitly Registered in a normal comparison. It does not assert that the underlying organisation was newly formed.
- `CHARITY_REMOVED`: an explicit transition to Removed. It only means Register status changed to Removed; it does not imply dissolution, misconduct, merger, or regulatory action. A disappeared row is an error, never a removal signal.
- `REGISTER_STATUS_CHANGED`: other explicit registration-status transitions.
- `CHARITY_NAME_CHANGED`
- `CLASSIFICATION_CHANGED` and `AREA_OF_OPERATION_CHANGED`, with added and removed canonical set items. Row order is ignored.
- `ANNUAL_RETURN_FILED`: the latest stable financial-period/cycle filing identity first appears. Receipt-date or row-order corrections alone do not repeat the signal.
- `REPORTING_STATUS_CHANGED`: only the source field's explicit transition; the Actor does not calculate compliance.
- `INCOME_CHANGED`: a numeric latest-income change. It is observational only and is not an assessment of growth, health, risk, distress, or quality. Null transitions are suppressed.

### Operation

On a fresh live store the Actor validates all sources, writes a complete compressed snapshot, emits zero Dataset rows, and reports `BASELINE_INITIALIZED`. An unchanged comparison is successful with zero signals. `maxItems` limits Dataset output only, never the snapshot. `baselineOnly` refreshes a validated baseline without emitting signals.

Schedule live mode daily after the source's usual publication window. Filters select signal types, charity numbers, statuses, classification/area text, and minimum income deltas. Filtering never changes the full snapshot.

Sample mode is deterministic and isolated: it makes no HTTP request, opens no production named store, changes no snapshot, and runs production diff/filter logic. It demonstrates eight core signal types with non-empty output. The input form defaults to live for real runs and prefills sample for a safe example.

### Safety and limitations

The Actor checks HTTPS host, HTTP status, content type, minimum size, ZIP magic, JSON shape, required properties, unique main keys, extraction-date alignment, minimum counts, and a 40% relative count-collapse guard. Fetch, parse, validation, Dataset, or summary failure leaves the prior snapshot unchanged. The snapshot is committed last.

The Actor deliberately does not fetch trustee data. It drops all contact names, addresses, emails, phones, and other individual-level fields at the source-normalisation boundary. Results cover the England & Wales register and are not legal, financial, compliance, fraud, or funding advice.

Contains public sector information licensed under the [Open Government Licence v3.0](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/). Source: Charity Commission for England and Wales. OGL exclusions, including third-party rights, continue to apply.

### Output example

```json
{
  "signalType": "INCOME_CHANGED",
  "registeredCharityNumber": "1234567",
  "charityName": "Example Charity",
  "previousValue": 100000,
  "currentValue": 125000,
  "absoluteDelta": 25000,
  "percentageDelta": 25,
  "sourceExtractDate": "2026-09-17"
}
```

# Actor input Schema

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

Live official comparison or isolated deterministic sample.

## `signalTypes` (type: `array`):

Optional signal-type filter.

## `charityNumbers` (type: `array`):

Optional registered-charity-number filter.

## `registrationStatuses` (type: `array`):

Optional source registration-status filter.

## `classifications` (type: `array`):

Optional classification text filter.

## `areasOfOperation` (type: `array`):

Optional area text filter.

## `minIncomeChangeAbsolute` (type: `number`):

Optional absolute income-delta threshold.

## `minIncomeChangePercent` (type: `number`):

Optional percentage income-delta threshold.

## `baselineOnly` (type: `boolean`):

Refresh the full baseline without emitting signals.

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

Caps Dataset output only; never truncates the snapshot.

## Actor input object example

```json
{
  "mode": "sample",
  "baselineOnly": false,
  "maxItems": 30
}
```

# Actor output Schema

## `OUTPUT` (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 = {
    "mode": "sample",
    "maxItems": 30
};

// Run the Actor and wait for it to finish
const run = await client.actor("starshaped_bullsnake/england-wales-charity-register-change-signals").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 = {
    "mode": "sample",
    "maxItems": 30,
}

# Run the Actor and wait for it to finish
run = client.actor("starshaped_bullsnake/england-wales-charity-register-change-signals").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 '{
  "mode": "sample",
  "maxItems": 30
}' |
apify call starshaped_bullsnake/england-wales-charity-register-change-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,starshaped_bullsnake/england-wales-charity-register-change-signals"
        }
    }
}
```

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/ZDbbSGjAGq5txSwaS/builds/I9qAbqFAZPXGaRjmF/openapi.json