# EU Surface Water Chemical Status Records — EEA WISE (`nexgensignal/eu-surface-water-chemical-status-records`) Actor

Keyless pay-per-record EEA WISE WFD surface-water chemical status — water body, ecological status, chemical status and chemical status without uPBT, verbatim. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-surface-water-chemical-status-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 sw chemical status 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 Chemical Status Records — EEA WISE

**Keyless. Pay per record. The official chemical status of Europe's surface waters — including the view that excludes ubiquitous persistent pollutants.**

This actor turns the **European Environment Agency (EEA) WISE Water Framework Directive (WFD) database** into clean, per-record data — the official chemical status of Europe's surface water bodies, including the uPBT-excluded view. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per status row, structured for water-status and compliance 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, each surface water body is assigned a chemical status. Because a handful of ubiquitous persistent bioaccumulative toxic (uPBT) substances — like mercury and certain brominated compounds — fail almost everywhere and can mask other trends, the directive also reports chemical status EXCLUDING those substances. This actor delivers one record per water body / cycle: the country, river basin, and water body; the ecological status; the overall chemical status; and the chemical status WITHOUT uPBT — all status labels carried verbatim. It is the chemical-status layer, with the uPBT-excluded lens built in.

### Who buys this and for what job

- **Water-quality analysts tracking surface-water chemical status with and without the ubiquitous substances**
- **Policy and reporting teams separating the uPBT overlay from underlying chemical trends**
- **Researchers studying how uPBT substances shape reported chemical status**
- **Data engineers** who want the WISE WFD surface-water chemical status 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 surface water body's chemical status for a cycle — a status line, never a person. 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.

### Sample output

![Sample output — EU Surface Water Chemical Status Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-surface-water-chemical-status-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: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",
  "chemical_status_value_without_upbt": "2",
  "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 chemical status",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE Water Framework Directive (WFD) database — surface-water chemical status. 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": "Official surface-water chemical status, at water-body / reporting-cycle grain from the EEA WISE Water Framework Directive database, including the chemical status assessed EXCLUDING the ubiquitous persistent bioaccumulative toxic (uPBT) substances (swChemicalStatusValueWithoutUPBT) alongside the overall chemical status. Status labels are 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:17Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `sw_chemical_status_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 | — | Optional 2-letter country code (e.g. DE, FR). |
| `year` | integer | — | Optional reporting cycle year to filter. |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per status row. Real example (values as reported):

```json
{
  "record_id": "ATOK1000010000: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",
  "chemical_status_value_without_upbt": "1",
  "source": "EEA WISE Water Framework Directive (WFD) \u2014 surface-water chemical status",
  "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 chemical-status row. 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`, `chemical_status_value`, and `chemical_status_value_without_upbt`. Plus `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 surface-water chemical status table (filtered to your optional `countryCode` and optional `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 **288,711 rows**. Because each record carries the `country_code`, the water-body identity, and the two chemical-status values, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The two status values are the point, and the fields make the comparison direct. Because every record carries both `chemical_status_value` and `chemical_status_value_without_upbt`, an analyst can isolate exactly how much of Europe's reported chemical failure is driven by the ubiquitous persistent substances — the bodies that are good without uPBT but fail with it — a distinction central to interpreting WFD chemical-status headlines. The `reporting_year` tracks change between cycles.

### Identifiers and joins

Every record carries the `eu_surface_water_body_code`, keying each status row to the fleet's priority-substance, exemption, and failing-pollutant cells for the same body, on a shared identifier.

### Why the uPBT view matters

Reported chemical status is famously binary and famously dominated by a few substances: once mercury alone can fail a body, the headline 'X% of waters fail chemical status' says little about the other pollutants. The without-uPBT value is the directive's own way of seeing past that overlay, and carrying both on one record lets a buyer produce the honest two-number picture — status as reported, and status once the ubiquitous substances are set aside — without stitching two datasets together.

### The status codes

Status is reported as the source's own coded value rather than resolved to a word, and it is carried verbatim so nothing is lost in translation; a downstream consumer maps the codes to labels against the WFD reference they already use. Carrying the ecological status alongside the two chemical-status values on one record means a buyer can screen bodies that are ecologically impaired, chemically failing, or failing only on the ubiquitous substances, each as its own filter.

### Cost guidance

One `sw_chemical_status_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, values, and flags are as filed; this actor reformats, it does not audit or recompute.
- **A label, not a verdict.** These are reported classifications and outcomes, not an independent compliance or health assessment.
- **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 multi-element status classification) and from the exemption cells (which record the exemptions claimed) — this cell carries the CHEMICAL status specifically, with the uPBT-excluded value alongside it. Its specific job is the **WFD surface-water chemical status (incl. without-uPBT)**.

### The NexGen Signal family

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

- [EU Waterbody Pressure Source Records — EEA WISE](https://apify.com/nexgensignal/eu-waterbody-pressure-source-records)
- [EU Groundwater Pollutant Failure Records — EEA WISE](https://apify.com/nexgensignal/eu-groundwater-pollutant-failure-records)
- [EU Surface Water Priority Substance Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-priority-substance-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)
- [EU Water Emission Load Records — EEA WISE](https://apify.com/nexgensignal/eu-water-emission-load-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 / cycle grain; no contact/operator/responsible-person field selected or emitted. No natural-person data of any kind. Values and status labels as filed, 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.

## `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-chemical-status-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-chemical-status-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-chemical-status-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-chemical-status-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/BgPS2Bq2kMdHz5OKK/builds/E2oh5qm3GQSdKmJrX/openapi.json