# EU Industrial ETS Linkage Records — EEA IED (`nexgensignal/eu-industrial-ets-linkage-records`) Actor

Keyless pay-per-record EEA IED installation-to-EU-ETS identifier crosswalk — identifiers verbatim + installation identity. No person data. EEA acknowledge. GOLD $0.05 ladder.

- **URL**: https://apify.com/nexgensignal/eu-industrial-ets-linkage-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 ets linkage 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 Industrial ETS Linkage Records — EEA IED

**Keyless. Pay per record. The bridge between the EU's industrial-emissions register and its carbon market — installation by installation.**

This actor turns the **European Environment Agency (EEA) Industrial Emissions Directive (IED) registry** into clean, per-linkage records — the join between each IED production installation and its **EU Emissions Trading System (ETS)** identifier. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per installation-to-ETS link: the installation id and its EU-ETS identifier, plus the installation's facility name, country, and main IED activity. Identifier-linkage grain, structured for engineering use, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Two of the EU's biggest environmental datasets — the IED industrial-installation register and the EU ETS carbon market — describe overlapping sets of facilities, but under different identifier schemes. The IED registry records which installations carry an ETS identifier, and this actor extracts exactly that crosswalk: it reads the installation-to-ETS-identifier table and joins each row to the installation's identity, delivering the installation id, the ETS identifier, and the installation's facility name (an organisation, suppressed where the source flags the name confidential), its country, main IED Annex I activity, and status. It is the key that lets a downstream system connect IED emissions data to ETS allowances and prices. Identifiers are carried **verbatim**. You are billed only for records actually delivered.

### Who buys this and for what job

- **Carbon-market, compliance, and emissions-analytics teams** joining IED facility emissions to EU-ETS accounts and allowances.
- **ESG and industrial-intelligence products** building a single facility view across the two registers.
- **Researchers and data teams** who need the IED↔ETS crosswalk without scraping two systems and matching by hand.
- **Data engineers** who want the linkage 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. This is a registry linkage as published — not a verification of any installation's ETS status.

### Installation grain — no person data

The unit of every record is an installation and its ETS identifier — an organisation, never a person. The installation name is a facility name (a company plant), and it is suppressed where the source marks it confidential. There is no operator, contact, or responsible-person field in the linkage, and none is emitted; a person-key guard runs on every record as a backstop.

### Sample output

![Sample output — EU Industrial ETS Linkage Records — EEA IED](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-industrial-ets-linkage-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:EE-KL-0011",
  "installation_id": "8",
  "ets_identifier": "EE-KL-0011",
  "installation_name": "Silpower AS, Sillamäe soojuselektrijaam",
  "country_code": "EE",
  "ied_annex_i_main_activity": "1.1",
  "installation_status": "functional",
  "reporting_year": "2017",
  "control_file_id": "15",
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Industrial Emissions Directive (IED) registry — installation-to-EU-ETS identifier linkage. 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), Industrial Emissions Directive (IED) registry.",
  "disclaimer": "Installation-to-EU-ETS identifier linkage records at identifier-linkage grain, from the EEA IED registry. Each record joins an IED production installation to its EU Emissions Trading System (ETS) identifier, with the installation's FACILITY name (an organisation, suppressed where the source flags the name confidential), country, and main IED activity. Installation/organisation grain — no natural-person data. Identifiers carried VERBATIM as published; a registry linkage, not a verification.",
  "observed_at": "2026-09-25T17:33:05Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `ets_linkage_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 to filter (e.g. DE, FR, IT). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per linkage. Real example (values as published):

```json
{
  "record_id": "8:EE-KL-0011",
  "installation_id": "8",
  "ets_identifier": "EE-KL-0011",
  "installation_name": "Silpower AS, Sillamäe soojuselektrijaam",
  "country_code": "EE",
  "ied_annex_i_main_activity": "1.1",
  "installation_status": "functional",
  "reporting_year": "2022",
  "control_file_id": "55",
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Installation-to-EU-ETS identifier linkage records ... no natural-person data ...",
  "observed_at": "2026-08-22T00:00:00Z"
}
```

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

### Field reference

Each record is one linkage. Keys: `record_id` (installation id + ETS id), `installation_id`, and `ets_identifier`. Installation identity: `installation_name` (facility/org, confidentiality-suppressed), `country_code`, `ied_annex_i_main_activity`, `installation_status`, and `reporting_year`. Provenance: `control_file_id`, `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 installation-to-ETS-identifier table, enriches each row with the installation's identity (suppressing the facility name where the source marks it confidential), applies your optional `countryCode` filter, and flattens each linkage to one record — carrying the identifiers **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 linkage table holds on the order of **36,000+ installation-to-ETS links**. Because each record carries the `country_code` and `ied_annex_i_main_activity`, segmenting the crosswalk by country or activity sector is straightforward. Pull one country, or the whole table to seed a master crosswalk.

### Working with the linkage

The linkage is a join key, and that is its whole value. Because every record pairs the IED `installation_id` with the `ets_identifier`, a downstream system can attach EU-ETS allowance, surrender, and price data to IED facility emissions in a single join — the crosswalk that otherwise takes fuzzy name-and-address matching across two registers. The `installation_name`, `country_code`, and `ied_annex_i_main_activity` give a human-readable anchor for QA, and because the identifiers are carried verbatim, the linkage stays stable across pulls. Where an installation's name is confidential, the link still resolves on the identifiers even though the name is withheld.

### Installation enrichment and confidentiality

Each linkage row in the source carries only an internal installation id; on its own that id is opaque. This actor enriches every record from the IED installation register, adding the installation's facility name, country, main IED Annex I activity, status, and reporting year, so a buyer sees which real facility each row refers to without running a second query. The enrichment is done in bounded, cached batches so a large pull stays efficient. One rule is enforced throughout: where the source flags an installation's name as confidential, the name is suppressed and only the non-name identity (country, activity, status) is carried — the linkage still resolves on the identifiers, but a withheld name is never revealed. This keeps the records both useful and faithful to the source's own confidentiality decisions.

### Cost guidance

One `ets_linkage_record` per delivered link: cost = links delivered × your plan's per-record price. Scope with `countryCode` to keep runs bounded. The whole table is ~36,000 links; 1,000 links is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **A linkage, not a verification.** These are the registry's own installation↔ETS joins, carried verbatim.
- **Name may be withheld.** Where the source marks the installation name confidential, it is suppressed; the identifiers still resolve.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

It is distinct from the fleet's **eu-industrial-emissions-records** (IED facility *emissions* to air and water) — this cell carries the **IED↔EU-ETS identifier crosswalk**, a different table serving a different job: connecting the two registers. It is the ETS-linkage member of a five-cell EEA industrial/water family (stricter-permit conditions, BAT conclusions, offsite transfers, pesticide monitoring).

### The NexGen Signal family

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

- [EU Industrial BAT Conclusion Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-bat-conclusion-records)
- [EU Stricter Permit Condition Records — EEA IED](https://apify.com/nexgensignal/eu-stricter-permit-condition-records)
- [EU Offsite Pollutant Transfer Records — EEA E-PRTR](https://apify.com/nexgensignal/eu-offsite-pollutant-transfer-records)
- [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU GHG Inventory Records — EEA](https://apify.com/nexgensignal/eu-ghg-inventory-records)

*Source: European Environment Agency (EEA), Industrial Emissions Directive (IED) registry (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. Identifier-linkage grain; installation (facility/organisation) identity only, name suppressed where confidential; no natural-person data of any kind. A registry linkage as published, not a verification.*

# Actor input Schema

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

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

## `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-industrial-ets-linkage-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-industrial-ets-linkage-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-industrial-ets-linkage-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-industrial-ets-linkage-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/43Oj5UNcrDTfBUE5P/builds/T1VDQMdskOk1rHDGP/openapi.json