# Northern Ireland Charity Register Change Signals (`starshaped_bullsnake/northern-ireland-charity-register-change-signals`) Actor

- **URL**: https://apify.com/starshaped\_bullsnake/northern-ireland-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 $3.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

## Northern Ireland Charity Register Change Signals

This is a change-intelligence Actor, not a Northern Ireland charity directory or a replacement for the official CCNI Register.

It downloads the complete live CSV export from the Charity Commission for Northern Ireland, validates and privacy-minimizes the data, compares it with the last successful full snapshot, and emits one Dataset item per meaningful organisation-level change. The OpenDataNI catalogue records CCNI as publisher, a daily cadence and the UK Open Government Licence; it is used only as catalogue/licence evidence, never as the production data mirror.

### Signals

- `NEW_CHARITY_REGISTERED`: a six-digit registration number newly appears and is not Removed.
- `CHARITY_REMOVED`: the same registration number changes explicitly to `Removed` in the current official export. Disappearance alone is never removal evidence.
- `CHARITY_NAME_CHANGED`, `COMPANY_NUMBER_CHANGED`.
- `REPORTING_STATUS_CHANGED`: transitions among `REGISTERED`, `RECEIVED_ON_TIME`, `RECEIVED_LATE`, `OVERDUE`, and `REMOVED`. Daily overdue/late day-count drift is discarded.
- `INCOME_CHANGED`, `EXPENDITURE_CHANGED`: observational comparisons of the latest reported totals, with both financial-period ends and amounts.
- `CLASSIFICATION_CHANGED`: set changes across what the charity does, whom it helps, and how it works; order-only changes are ignored.

`Reg charity number` is retained as a six-digit string and is the stable entity identity. Company-number `0` is treated as missing. No annual-return signal is inferred because the live export has no receipt-date field that provides a stable filing identity.

### Running

Use `{"mode":"sample","maxItems":30}` for a deterministic, non-empty demonstration. Sample mode performs no HTTP, never opens the production named key-value store, passes fixtures through the production normalization/diff/filter path, and reports `snapshotUpdated: false`.

Live mode fetches the official CSV. The first successful run writes a full baseline, emits zero signals, and reports `BASELINE_INITIALIZED`. Identical canonical state is a normal zero-signal success. `maxItems` and all filters affect Dataset output only, never the stored snapshot. Supported filters include signal types, charity numbers, reporting statuses and classifications, with absolute/percentage thresholds for income and expenditure.

Processing is fetch → validate → privacy projection → normalize → stable-key/count checks → previous snapshot → diff → Dataset → `OUTPUT` → compressed snapshot commit. The commit is last, so source, Dataset or summary failures retain the previous good snapshot. Guards reject non-CSV/HTML responses, unexpected redirects, missing columns, small files, fewer than 7,000 entities, insufficient Removed coverage, conflicting identities, major count collapse and implausible mass disappearance.

### Source, licence, privacy and limitations

Source: [CCNI official charity search and live CSV export](https://www.charitycommissionni.org.uk/charity-search/). Catalogue/licence evidence: [OpenDataNI Register of Charities](https://admin.opendatani.gov.uk/dataset/register-of-charities). Contains public sector information licensed under the UK Open Government Licence. The stated catalogue cadence is daily, but `fetchedAt` is an observation timestamp—not an official extract date when the response supplies no `Last-Modified` or `ETag`.

The snapshot and outputs exclude public address, website, email, telephone, trustees, named contacts, individual details, raw rows and account documents. They retain only organisation-level regulatory, classification and financial fields needed for comparison.

Finance values are source observations, not audited conclusions or advice. A financial-period shift may naturally change the latest totals; the output includes period context. CCNI cautions that some detailed zero-valued financial fields can reflect disclosure requirements rather than an economic zero, so this Actor compares only `Total income` and `Total spending` and excludes detailed/constant-zero fields. Source corrections can generate signals. Scheduling daily is reasonable, but publication timing is controlled by CCNI.

# Actor input Schema

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

Live official comparison or isolated deterministic sample.

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

Optional signal-type filter.

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

Optional six-digit registration-number filter.

## `reportingStatuses` (type: `array`):

Optional canonical reporting-status filter.

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

Optional exact classification filter.

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

Refresh the complete baseline without emitting signals.

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

Suppress smaller absolute income changes.

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

Suppress smaller percentage income changes.

## `minExpenditureChangeAbsolute` (type: `number`):

Suppress smaller absolute expenditure changes.

## `minExpenditureChangePercent` (type: `number`):

Suppress smaller percentage expenditure changes.

## `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/northern-ireland-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/northern-ireland-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/northern-ireland-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/northern-ireland-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/6uPISJkK5VChFVmJY/builds/ZpgEjGqESS5klnkNa/openapi.json