# UK FSA AppNo Portfolio Status Monitor (`plym-actor-factory/uk-fsa-appno-portfolio-monitor`) Actor

Watch FSA Approval Numbers (AppNo) and emit typed APPEARED/DROPPED/ACTIVITIES\_CHANGED/AUTHORITY\_CHANGED events from the official FSA Approved Food Establishments daily CSV (OGL v3). Not FHRS hygiene ratings; not FSA alerts/RASFF; not FSIS Est# twin; not HTML scrape; not unpaid supplier-audit SaaS.

- **URL**: https://apify.com/plym-actor-factory/uk-fsa-appno-portfolio-monitor.md
- **Developed by:** [Daniel Witney](https://apify.com/plym-actor-factory) (community)
- **Categories:** AI, Automation, Business
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $20.00 / 1,000 fsa appno status event delivereds

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 FSA Approved Food Establishment Approval Number Portfolio Status Event Monitor

Watch a book of **FSA Approval Numbers (AppNo)** and emit typed directory status/activity events when the official **Food Standards Agency Approved Food Establishments — Daily update** CSV shows an establishment **appearing**, **leaving the published approved list**, or **materially changing activities / competent authority**.

**Not** FHRS / Scores-on-the-Doors hygiene ratings. **Not** an FSA food-alert / RASFF ticker. **Not** unpaid supplier-audit SaaS scrape. **Not** the US FSIS Est# twin (different regulator, geography, ID scheme).

### Coverage honesty (AppNo exact match + daily CSV cadence)

- **Source:** Official FSA OGL v3 daily CSV\
  `https://fsaopendata.blob.core.windows.net/fsaopendatacatalog/source_data.ApprovedEstPublication_Daily.csv`\
  (live-verified HTTP 200; fields include `AppNo`, `TradingName`, address, `All_Activities`, `CompetentAuthority`, `GeographicLocalAuthority`, `InsertedDate`).
- **Keys:** **AppNo exact match** after normalize (trim / uppercase / collapse internal whitespace). TradingName+postcode is **not** used as a primary match.
- **Cadence:** **Daily** FSA extract (not intra-day).
- **Geography:** Verified blob coverage includes **England / Wales / Northern Ireland / Crown Dependencies**. **Scotland (Food Standards Scotland)** publishes separately and is **not** in this daily file — do not claim full-UK single-file coverage.
- **Fields:** Activities and authority mapped from FSA CSV columns (no invented statuses).

### Events

| Event | When |
|-------|------|
| `FSA_APP_APPEARED` | Watched AppNo missing → present on approved list |
| `FSA_APP_DROPPED` | Watched AppNo present → missing from approved list |
| `FSA_ACTIVITIES_CHANGED` | `All_Activities` fingerprint changed while still present |
| `FSA_AUTHORITY_CHANGED` | Competent and/or geographic local authority changed while still present |
| `RUN_STATUS` | Non-billable health row every successful run |

First observation of an AppNo stores a **baseline only** (no product charge).

### Modes

- **`sourceMode=fixture`** (default): Store health / CI. With `emitFixtureDemoEvents=false` (default) emits **only** `RUN_STATUS` / `FIXTURE_HEALTH` → **0** product charges.
- **`sourceMode=live`**: Official FSA daily CSV (**no API key**). One CSV pull, then in-memory filter to the watchlist — does **not** bill national rows.

### Pricing (Model A)

- `fsa-appno-status-event-delivered` @ **$0.02** / unique delivered event
- `apify-actor-start` @ **$0.00005**
- Quiet books ≈ $0 product charge

### Input

See `.actor/input_schema.json`. Primary field: `approvalNumbers` (alias `appNos`). Optional `signalGroups`: `directory`, `activities`, `authority`.

### Legal

**GREEN** — FSA open data under **Open Government Licence v3**. Cite FSA + retrieval date. Default product fields = AppNo + trading name + activities/authority + address (business facility data; no consumer PII).

### A1b wedge

Approval-number watchlist × scheduled official daily FSA CSV snapshot diff → typed approval-directory status/activity events only for the book. Existing Store shelf is alert/RASFF/FHRS (wrong jobs) or empty AppNo portfolio PPE. See `opportunity/reports/phase3-a1b-next3-v12.md` (#1 PASS → build #32). Competitors cited from v12 only: `taroyamada/food-safety-alert-portfolio-report` (0 MAU, alerts); EU RASFF scrapers `promptica` / `scrapers_lat` (1); FHRS hygiene scrapers (exhausted adjacent).

### Private

`isPublic` must remain **false** for this launch.

# Actor input Schema

## `approvalNumbers` (type: `array`):

FSA Approval Numbers (AppNo) to monitor against the official Approved Food Establishments daily CSV. Exact match after normalize (trim/uppercase/collapse spaces). Invalid entries are skipped with no charge. Not a nationwide premises dump — only AppNos on the book are evaluated.

## `appNos` (type: `array`):

Optional alias for approvalNumbers — same AppNo keys, merged into the watchlist.

## `signalGroups` (type: `array`):

Which change groups to evaluate: directory (APPEARED/DROPPED), activities, authority. Default: all.

## `maxRunSeconds` (type: `integer`):

Wall-clock budget for the run (CSV fetch + watchlist diff).

## `maxEvents` (type: `integer`):

Stop after this many unique change events are delivered (does not include RUN\_STATUS).

## `resumeFromCheckpoint` (type: `boolean`):

If true, resume establishment snapshots and seen event\_uids from the default Key-Value Store.

## `sourceMode` (type: `string`):

fixture = local/CI / Apify Store daily auto-test default (no network; emits RUN\_STATUS only unless emitFixtureDemoEvents=true). live = official FSA Approved Establishments daily CSV (OGL v3; no API key).

## `emitFixtureDemoEvents` (type: `boolean`):

When sourceMode=fixture, if true push fabricated change events from local fixtures (unit/local demos only). Default false so Store daily auto-tests never emit fake FSA events or charge fsa-appno-status-event-delivered. Production: leave false and use sourceMode=live. SAMPLE rows only: demo events use placeholder entities (never real companies/IDs), are flagged sample=true / isSample=true, and are NEVER charged.

## `asOfHint` (type: `string`):

Optional as\_of label for events / RUN\_STATUS. Defaults to InsertedDate date from the daily CSV when present.

## `maxTotalChargeUsd` (type: `number`):

Optional soft budget hint for delivered change events. Platform ACTOR\_MAX\_TOTAL\_CHARGE\_USD also applies when set.

## `csvUrl` (type: `string`):

Optional override for the official FSA Approved Establishments daily CSV. Default: https://fsaopendata.blob.core.windows.net/fsaopendatacatalog/source\_data.ApprovedEstPublication\_Daily.csv

## Actor input object example

```json
{
  "approvalNumbers": [
    "1000",
    "1003",
    "1004"
  ],
  "signalGroups": [
    "directory",
    "activities",
    "authority"
  ],
  "maxRunSeconds": 55,
  "maxEvents": 500,
  "resumeFromCheckpoint": true,
  "sourceMode": "fixture",
  "emitFixtureDemoEvents": false
}
```

# Actor output Schema

## `OUTPUT` (type: `string`):

JSON summary: delivered, charged, runStatus, checkpoint, stats, FSA AppNo coverage limits

# 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("plym-actor-factory/uk-fsa-appno-portfolio-monitor").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("plym-actor-factory/uk-fsa-appno-portfolio-monitor").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 plym-actor-factory/uk-fsa-appno-portfolio-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,plym-actor-factory/uk-fsa-appno-portfolio-monitor"
        }
    }
}
```

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/aD1GP5M0M1BoXMuIk/builds/PtuzHSItBvOeGd6DM/openapi.json