# Environment Agency WEEE Treatment & Export Approval Signals (`starshaped_bullsnake/environment-agency-weee-treatment-export-change-signals`) Actor

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

## Pricing

from $30.00 / 1,000 weee treatment/export approval 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

## Environment Agency WEEE Treatment & Export Approval Change Signals

Monitors two Environment Agency documents from the [official WEEE public-registers page](https://www.gov.uk/government/publications/waste-electrical-and-electronic-equipment-weee-public-registers): the approved authorised treatment facility (AATF) register and approved exporter (AE) register. Both current ODS links are resolved dynamically. Producer and compliance-scheme documents are excluded. The publisher has generally updated these registers monthly, but controls the cadence.

### Identity and signals

The stable identity is `approvalType + ":" + approvalNumber`, using source columns `AATF approval number` and `AE approval number`. Approval numbers are annual/instance identities, not permanent cross-year organisation identities. The canonical record retains approval type/number, operator name, approval date, status, size, and a privacy-minimised site (source name plus postcode).

Signals are `APPROVAL_ADDED`, `STATUS_CHANGED`, `SIZE_CHANGED`, `OPERATOR_NAME_CHANGED`, `SITE_CHANGED`, `APPROVAL_NO_LONGER_LISTED`, and `APPROVAL_CANCELLED`. Cancellation is emitted only for an explicit transition to a source status containing “Cancelled”. Disappearance means only no longer listed; renewal and cancellation are never inferred from operator/site similarity or absence.

### Dual-source atomicity and anomaly guard

The first successful run validates both complete current-year sheets, creates one combined baseline, and emits zero items (`BASELINE_INITIALIZED`). An unchanged run emits zero. `maxItems` limits only Dataset output. AATF and AE ZIP/container, `content.xml`, sheet, headers, keys, hashes, minimum counts, previous/current ratios, and mass removals are checked separately, plus combined cross-source validation. If either source fails, the Actor emits no business signals and preserves the entire previous combined snapshot. Dataset and `OUTPUT` finish before snapshot commit.

### Sample, privacy, and legal basis

`mode=sample` produces deterministic signals through production diff/filter code with no HTTP, production named KVS access, or snapshot mutation. Personal contacts, email, telephone, operator street address, and other unnecessary fields are excluded. Site monitoring uses only organisation/site name and postcode, and `before`/`after` records remain compact.

Contains Environment Agency information © Environment Agency copyright and database right 2026, licensed under the [Open Government Licence v3.0](https://www.nationalarchives.gov.uk/doc/open-government-licence/version/3/). No third-party exception was displayed when verified on 18 September 2026. This is a publication-change monitor, not legal advice or real-time approval verification; source corrections can produce signals.

# Actor input Schema

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

Live official comparison or isolated sample demonstration.

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

Optional signal-type filter.

## `approvalTypes` (type: `array`):

Optional AATF or AE filter.

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

Refresh the full dual-source baseline without emitting signals.

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

Dataset output limit only; the complete dual-source snapshot is retained.

## 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/environment-agency-weee-treatment-export-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/environment-agency-weee-treatment-export-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/environment-agency-weee-treatment-export-change-signals --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,starshaped_bullsnake/environment-agency-weee-treatment-export-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/Mmx0lvC08nmd0KtDx/builds/zL0QqwxlfgnoC9GD3/openapi.json