# EU Species Threat Records — EEA BISE (`nexgensignal/eu-species-threat-records`) Actor

Keyless pay-per-record EEA BISE highly-important species threats — EUNIS species id, EU threats-and-pressures code and label, and reported rank, as filed. Species grain, no person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-species-threat-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 species threat 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 Species Threat Records — EEA BISE

**Keyless. Pay per record. The most important threats to Europe's protected species, by species and threat code.**

This actor turns the **European Environment Agency (EEA) Biodiversity Information System for Europe (BISE)** into clean, per-record data — the highly important THREATS reported for Europe's protected species under the Habitats Directive assessment. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per species-threat, structured for conservation and biodiversity analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

When member states assess the conservation status of Europe's protected species, they record the threats and pressures acting on each — agriculture, pollution, hydrological change, and more — and flag the ones that matter most. This actor reads that highly-important-threats table and delivers one record per species-threat: the EUNIS SPECIES identifier, the coded THREAT (the standard EU threats-and-pressures code and its label), and the reported QUANTITY/rank of how important it is — all carried as filed. It is the species-threat layer of Europe's biodiversity reporting, distinct from the site-level threats cell.

### Who buys this and for what job

- **Conservation NGOs and biodiversity researchers** ranking the threats that matter most per species.
- **Environmental consultancies** linking species threats to the pressures behind them.
- **Policy and agri-environment teams** targeting the threat codes most often flagged as important.
- **Data engineers** who want the BISE species-threat 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 classifications as filed — not an assessment of this actor's making.

### Species grain — no person data

The unit of every record is a threat to a species — a species identifier, a threat code, and a rank, never a person. BISE reporting is at species / threat level: the EUNIS id identifies a species, never a person; there is **no contact or named-individual field** in the source table, and none is selected or emitted. A person-key guard runs on every record as a backstop.

### A note on scale, honestly

The source table holds **6,761 rows** as verified by an exact `COUNT(*)` at build time, which matches the planning index for this category exactly. It spans the protected species and the threats flagged as highly important for each. The live count above is authoritative.

### Sample output

![Sample output — EU Species Threat Records — EEA BISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-species-threat-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": "8:A02",
  "species_eunis_id": "8",
  "threat_code": "A02",
  "threat_label": "Conversion from one type of agricultural land use to another (excluding drainage and burning)",
  "rank": 1,
  "source": "EEA Biodiversity Information System for Europe (BISE) — highly important threats to protected species",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Biodiversity Information System for Europe (BISE) / Natura 2000 reporting. 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), Biodiversity Information System for Europe (BISE) (discodata.eea.europa.eu).",
  "disclaimer": "Highly important THREATS reported for Europe's protected species under the Habitats Directive Article 17 assessment, at species / threat grain from the EEA BISE database. Each record carries the EUNIS SPECIES identifier, the coded THREAT/pressure (the standard EU threats-and-pressures code and its label), and the reported QUANTITY/rank (how many assessments flagged it as highly important) VERBATIM. Species grain — the EUNIS id identifies a species, never a person; there is no contact or named-individual field in the source, none is selected or emitted, and a person-key guard runs on every record.",
  "observed_at": "2026-09-25T17:34:06Z"
}
```

### Pricing

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

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

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `threatCode` | string | — | Optional EU threats-and-pressures code to filter (e.g. A02, F01). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per species-threat. Representative example (values as reported):

```json
{
  "record_id": "8:A26",
  "species_eunis_id": "8",
  "threat_code": "A26",
  "threat_label": "Agricultural activities generating diffuse pollution to surface or ground waters",
  "rank": 4,
  "source": "EEA Biodiversity Information System for Europe (BISE) — highly important threats to protected species",
  "observed_at": "2026-08-30T00: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 highly-important threat to a species. Identity: `record_id` and `species_eunis_id` (the EUNIS species identifier, joinable to species dictionaries). Threat: `threat_code` (the EU threats-and-pressures code), `threat_label` (its standard label), and `rank` (the reported quantity/importance). 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 BISE highly-important-threats table (filtered to your optional `threatCode`), ordered by the species identifier, and flattens each row to one record — carrying every coded 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 **6,761 rows** across protected species and threat codes. Because each record carries the `species_eunis_id`, the `threat_code`, and the `rank`, segmenting by species or threat type is straightforward. Pull one threat code, or the whole table to seed a biodiversity warehouse; join `species_eunis_id` to a species dictionary for scientific names.

### Working with the data

The threats are a diagnostic layer, and the fields make them actionable. Because every record pairs a species with a `threat_code` and a `rank`, an analyst can find the threats most often flagged as highly important across all species in one group-by, rank the threats facing a single species, and — joined to the site-level negative-impact cell — connect species-level threats to the sites where the same pressures are recorded.

### The threats-and-pressures vocabulary

The `threat_code` comes from the EU's standard list of threats and pressures — the same controlled vocabulary used across the Habitats Directive reporting, with codes grouped by driver: agriculture (the A-codes), forestry, urbanisation, pollution, natural-system modification, climate change, and so on. Because the vocabulary is standardised across every reporting country and shared with the habitats and sites reporting, a threat such as "agricultural activities generating diffuse pollution" is coded identically for a species in Spain and one in Finland — so cross-country and cross-species comparison needs no translation layer, and the `threat_label` carried on every record makes the code human-readable without a lookup. Grouping the whole table by the leading letter of the code gives an instant picture of which broad drivers dominate the threats to Europe's protected species, and filtering to a single code isolates every species for which that pressure was flagged as highly important.

### A note on identifiers

The `species_eunis_id` is the EUNIS identifier for a species — a stable key in the EEA's biodiversity information system, a species and never a person. It is the join key you use to attach scientific and common names from a species dictionary, and to line these threats up against the conservation-status and site cells that use the same identifier. Because the id is stable across the reporting, building a complete per-species picture needs no fuzzy matching.

### Cost guidance

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

### Honest limitations

- **As reported.** Threats and ranks are as filed by member states for the Habitats Directive assessment; this actor reformats, it does not audit or recompute.
- **Species id, not name.** The record carries the EUNIS species identifier; join it to a species dictionary for scientific and common names.
- **Highly important only.** This table holds the threats flagged as highly important, not every reported threat.
- **Acknowledge the EEA**, and note there is **no person data** of any kind.

### Differentiation

It is the SPECIES-level threat grain, a distinct source table from the live **eu-protected-site-negative-impact-records** (site-level threats and pressures) — this cell records threats per species, not per site. Its specific job is the **BISE highly-important species threats**.

### The NexGen Signal family

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

- [EU Water Abstraction Records — EEA](https://apify.com/nexgensignal/eu-water-abstraction-records)
- [EU Renewable Freshwater Resource Records — EEA](https://apify.com/nexgensignal/eu-renewable-freshwater-resource-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)
- [EU Historical Flood Event Records — EEA](https://apify.com/nexgensignal/eu-historical-flood-event-records)
- [EU Protected Site Positive Impact Records — EEA](https://apify.com/nexgensignal/eu-protected-site-positive-impact-records)

*Source: European Environment Agency (EEA), Biodiversity Information System for Europe (BISE) (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. Species grain; the EUNIS id identifies a species, not a person; no contact or named-individual field is selected or emitted, no natural-person data of any kind. Reported classifications as filed, not an assessment.*

# Actor input Schema

## `threatCode` (type: `string`):

Optional EU threats-and-pressures code to filter (e.g. A02, F01).

## `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-species-threat-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-species-threat-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-species-threat-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-species-threat-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/dusakDkF2TbzGYGfQ/builds/coEjLazDWgD1CP18d/openapi.json