# EU Surface Water Failing Pollutant Records — EEA WISE (`nexgensignal/eu-surface-water-failing-pollutant-records`) Actor

Keyless pay-per-record EEA WISE WFD surface-water failing pollutants — water body, river basin, the specific failing pollutant, and ecological/chemical status labels, verbatim. Water-body grain, no person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-surface-water-failing-pollutant-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 failing pollutant records

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

## EU Surface Water Failing Pollutant Records — EEA WISE

**Keyless. Pay per record. Every river-basin-specific pollutant recorded as causing a European surface water body to fail status.**

This actor turns the **European Environment Agency (EEA) WISE Water Framework Directive (WFD) database** into clean, per-record data — the river-basin-specific pollutants (RBSP) recorded as causing surface-water status failure across Europe. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per failing-pollutant record, structured for environmental and water-management analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Under the Water Framework Directive, member states report the river-basin-specific pollutants that cause a surface water body to miss good status. This actor reads that table and flattens each failing-pollutant line into a single analysis-ready record: the country, river basin district and sub-unit, the water body (code, name, and category), the ecological and chemical STATUS LABELS carried verbatim, the specific failing pollutant, and any free-text pressure/impact notes. Status labels are carried exactly as reported — a label, never a compliance verdict. It is the failing-pollutant layer beneath Europe's surface-water status map.

### Who buys this and for what job

- **Water-quality and river-basin analysts mapping which pollutants drive surface-water failures**
- **Environmental consultancies and NGOs targeting the substances behind status failures**
- **ESG and catchment-management products attributing failures to specific pollutants**
- **Data engineers** who want the WISE WFD failing-pollutant table as clean rows from a keyless source.

### EEA licence — reuse with acknowledgement

One licence rider travels on every record. EEA data may be **reused, including commercially, provided the source is acknowledged**: "Source: European Environment Agency (EEA)." Where third-party content is marked, it keeps its own terms. These are reported values and status labels as filed — not a compliance verdict.

### Water-body grain — no person data

The unit of every record is a failing-pollutant line for a surface water body — a water body and its reported attributes, never a person. WISE WFD reporting is at water-body / river-basin level: there is **no contact, operator, or responsible-person field** in the source table, and none is selected or emitted — the query reads only the water-body identity, the status labels, and the failing pollutant and pressure notes. A person-key guard runs on every record as a backstop. The `file_url`, where present, points to the official EEA/Eionet reporting file (an organisation reporting system), never a person.

### Sample output

![Sample output — EU Surface Water Failing Pollutant Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-surface-water-failing-pollutant-records.png)

*Real rows from a live run of this actor (first 5 rows, selected columns).*

One full record from the same run, exactly as delivered:

```json
{
  "record_id": "ATOK1000010000:None:2016",
  "reporting_year": 2016,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT1000",
  "rbd_name": "DANUBE",
  "eu_sub_unit_code": "AT1001",
  "sub_unit_name": "DANUBE",
  "eu_surface_water_body_code": "ATOK1000010000",
  "surface_water_body_name": "NO INTERNATIONAL NAME",
  "surface_water_body_category": "RW",
  "natural_awb_hmwb": "Natural water body",
  "ecological_status_or_potential_value": "3",
  "chemical_status_value": "3",
  "failing_rbsp": "None",
  "failing_rbsp_other": null,
  "significant_pressure_other": null,
  "significant_impact_other": null,
  "has_descriptive_data": 1,
  "file_url": "http://cdr.eionet.europa.eu/at/eu/wfd2016/districts/at1000/envwvttw/SWB_AT_20170509.xml",
  "source": "EEA WISE Water Framework Directive (WFD) — surface-water failing pollutants",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE Water Framework Directive (WFD) database — surface-water river-basin-specific failing pollutants. Reuse is permitted, including for commercial purposes, provided the source is acknowledged: 'Source: European Environment Agency (EEA)'. Third-party content, where marked, keeps its own terms.",
  "attribution": "Source: European Environment Agency (EEA), WISE Water Framework Directive (WFD) database.",
  "disclaimer": "Surface-water river-basin-specific pollutants (RBSP) causing status failure, at water-body / pollutant / reporting-cycle grain from the EEA WISE Water Framework Directive database. Each record names a water body, the specific pollutant recorded as failing, and the ecological and chemical STATUS LABELS carried VERBATIM as reported — a status label, never a compliance verdict. Water-body grain — there is no contact, operator, or responsible-person field in the source, and none is selected or emitted; a person-key guard runs on every record as a backstop.",
  "observed_at": "2026-09-25T17:34:21Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `failing_pollutant_record` | $0.05 | $0.045 | $0.04 | $0.0335 |

Delivered before charged. Blocked runs and empty results cost nothing.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `countryCode` | string | — | `countryCode` is optional — 2-letter country code (e.g. DE, FR). |
| `year` | integer | — | Optional WFD reporting cycle year to filter (e.g. 2016, 2022). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per failing-pollutant record. Real example (values as reported):

```json
{
  "record_id": "ATOK1000010000:Zinc:2016",
  "reporting_year": 2016,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT1000",
  "rbd_name": "DANUBE",
  "eu_surface_water_body_code": "ATOK1000010000",
  "surface_water_body_name": "Example Reach",
  "surface_water_body_category": "RW",
  "ecological_status_or_potential_value": "3",
  "chemical_status_value": "2",
  "failing_rbsp": "Zinc",
  "file_url": "https://cdr.eionet.europa.eu/at/...",
  "source": "EEA WISE Water Framework Directive (WFD) \u2014 surface-water failing pollutants",
  "observed_at": "2026-08-22T00:00:00Z"
}
```

An unbilled `RUN_RECEIPT` records the robots check, the filters, rows seen and delivered, and whether charged equals delivered.

### Field reference

Each record is one failing-pollutant line. Identity: `record_id`, `country_code`, `country_name`, `eu_rbd_code`, `rbd_name`, `eu_sub_unit_code`, `sub_unit_name`, `eu_surface_water_body_code`, `surface_water_body_name`, `surface_water_body_category`, `natural_awb_hmwb`, and `reporting_year`. Status: `ecological_status_or_potential_value` and `chemical_status_value` (labels, verbatim). Failure: `failing_rbsp`, `failing_rbsp_other`, `significant_pressure_other`, and `significant_impact_other`. Provenance also includes `has_descriptive_data` and `file_url`. Provenance travels on every record: `source`, `source_url`, `licence`, `attribution`, `disclaimer`, and `observed_at`.

### How a run works

A run first re-reads the source host's robots posture from your runtime — the EEA DiscoData host — and stops at the door if that ever changes. It pages the WISE WFD failing-pollutant table (filtered to your optional `countryCode` and `year`), and flattens each row to one record — carrying every status label and value **verbatim**, never anything person-shaped — delivered **before** it is charged, so a blocked or empty run costs you nothing. The actor stops at your `maxRecords` ceiling and records `charge_equals_delivered` in the receipt.

### Coverage and scope

The table holds on the order of **300,588 rows** across reporting countries, river basin districts, and the 2016 and 2022 WFD reporting cycles. Because each record carries the `country_code`, the water-body identity, and the `reporting_year`, segmenting by country, basin, or cycle is straightforward. Pull one country, or the whole table to seed a water-status warehouse.

### Identifiers and joins

Every record carries the `eu_surface_water_body_code`, a stable WISE identifier that keys each failing-pollutant line back to its water body across the fleet's other WISE cells — the water-body status classification, the ecological and chemical exemptions, and the river-basin-district threshold values. A buyer can therefore assemble a full picture of a water body — its status, the pollutants failing it, the exemptions claimed, and the regulatory thresholds in its basin — on a shared identifier rather than a fuzzy name match, and the `reporting_year` keeps the 2016 and 2022 cycles cleanly separable for trend work.

### Working with the data

The failing pollutants are a diagnostic layer, and the fields make them queryable. Because every record pairs a `failing_rbsp` with a water body's `ecological_status_or_potential_value` and `chemical_status_value`, an analyst can rank which pollutants drive the most failures in a basin or country in a single group-by, and the `reporting_year` lets two cycles be diffed to see whether a pollutant's footprint grew or shrank. The water-body identity keys each line back to the fleet's water-body status cell for the full classification picture.

### Cost guidance

One `failing_pollutant_record` per delivered row: cost = rows delivered × your plan's per-record price. Scope with `countryCode` and `year` to keep runs bounded. 1,000 rows is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **As reported.** Status labels and values are as filed by member states for the WFD reporting cycle; this actor reformats, it does not audit or recompute.
- **A status label, not a verdict.** These are reported classifications and exemptions, not an independent compliance assessment.
- **Two cycles merged.** The table carries both the 2016 and 2022 reporting cycles; the `reporting_year` field distinguishes them — filter on it if you want a single cycle.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

It is distinct from **eu-waterbody-quality-records** (the overall water-body STATUS classification) — this cell names the specific POLLUTANTS causing surface-water failure. It is a different directive and grain from **eu-nitrate-monitoring-records** (Nitrates Directive), **eu-bathing-water-quality-records** (Bathing Water Directive), and **eu-wastewater-compliance-records** (Urban Waste Water Directive). Its specific job is the **WFD surface-water failing river-basin-specific pollutants**.

### The NexGen Signal family

Part of the NexGen Signal family of pay-per-record data products:

- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)
- [EU Bathing Water Quality Records — EEA](https://apify.com/nexgensignal/eu-bathing-water-quality-records)
- [EU Nitrate Monitoring Records — EEA](https://apify.com/nexgensignal/eu-nitrate-monitoring-records)
- [EU Wastewater Compliance Records — EEA UWWTD](https://apify.com/nexgensignal/eu-wastewater-compliance-records)
- [EU Pesticide Water Monitoring Records — EEA](https://apify.com/nexgensignal/eu-pesticide-water-monitoring-records)

*Source: European Environment Agency (EEA), WISE Water Framework Directive (WFD) database (discodata.eea.europa.eu). EEA data may be reused, including commercially, provided the source is acknowledged: "Source: European Environment Agency (EEA)"; marked third-party content keeps its own terms. Water-body grain; no contact, operator, or responsible-person field is selected or emitted, no natural-person data of any kind. Status labels and values as filed for the WFD reporting cycle, not a compliance verdict.*

# Actor input Schema

## `countryCode` (type: `string`):

Optional 2-letter country code (e.g. DE, FR).

## `year` (type: `integer`):

Optional reporting cycle year to filter (e.g. 2016, 2022).

## `maxRecords` (type: `integer`):

Maximum records delivered and billed.

## Actor input object example

```json
{
  "maxRecords": 10
}
```

# Actor output Schema

## `results` (type: `string`):

Delivered records.

# 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 = {
    "maxRecords": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-surface-water-failing-pollutant-records").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 = { "maxRecords": 10 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-surface-water-failing-pollutant-records").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 '{
  "maxRecords": 10
}' |
apify call nexgensignal/eu-surface-water-failing-pollutant-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-surface-water-failing-pollutant-records"
        }
    }
}
```

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/yHKpBXp6ZiiEZ5PYK/builds/1KHuSLlza4roWMBtx/openapi.json