# EU Open Data Change Feed (`alka-labs/eu-dataset-changes`) Actor

- **URL**: https://apify.com/alka-labs/eu-dataset-changes.md
- **Developed by:** [Igor Lima](https://apify.com/alka-labs) (community)
- **Categories:** Developer tools, AI, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$2.00 / 1,000 changed dataset record returneds

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

## eu-dataset-changes

A change feed for the **EU Open Data Portal**: which datasets moved inside a time window,
newest first.

Search answers *what exists*. This answers the question you have once you already hold a
copy: *what do I have to fetch again?* It is the difference between re-mirroring 1.7 million
datasets every night and fetching the eleven that changed.

### Input

Every field is optional. With no input you get everything modified in the last 7 days.

```json
{
  "since": "2026-09-01",
  "until": "2026-09-16",
  "date_type": "modified",
  "query": "air quality",
  "country": ["be"],
  "catalogue": ["data-gov-be"],
  "categories": ["ENVI"],
  "language": "en",
  "max_results": 50
}
```

| Field | Meaning |
|---|---|
| `since` / `until` | ISO date (`2026-09-01`) or full timestamp. Defaults: 7 days ago → now |
| `date_type` | `modified` (default) or `issued` — changed vs. newly published |
| `query`, `country`, `catalogue`, `categories` | same filters as `eu-open-data-search` |
| `language` | which language to collapse multilingual titles to |
| `max_results` | 1 to 500 |

### Output

Same dataset record as `eu-open-data-search`, plus `changed_at` — the value of whichever
date field you filtered on, so you can store it as your watermark for the next call.

```json
{
  "unit": "eu-dataset-changes",
  "version": "1.0.0",
  "window": { "since": "2026-09-01T00:00:00Z", "until": "2026-09-16T15:34:45Z", "date_type": "modified" },
  "total_matches": 162,
  "returned": 4,
  "datasets": [
    { "id": "...", "title": "Traffic on rivers in Wallonia", "changed_at": "2026-09-08T18:30:35.451Z",
      "country_code": "BE", "licenses": [ { "id": "CC_BY_4_0", "...": "..." } ],
      "attribution_required": "yes", "distribution_count": 4 }
  ]
}
```

**Records come back newest first.** A change feed that is not ordered forces the caller to
buffer the whole window before acting on any of it.

`total_matches` is how many datasets changed in the window; `returned` is how many you
asked for. When they differ, narrow the window or raise `max_results` — do not assume the
list is complete.

`esquema.json` is the contract. If it changes, this is a new version, not a fix.

### Licensing, personal data, rate limiting

Identical to `eu-open-data-search`: portal metadata is CC0 1.0, each dataset keeps its own
licence and carries `attribution_required` (`yes` / `no` / `unknown`), no personal data is
emitted, one request per second, `Retry-After` honoured, official API over plain HTTP.

### Running it

```
python main.py '{"since": "2026-09-01", "country": ["be"]}'   # or pipe JSON on stdin
python conferir.py output.json
python fumaca.py
```

# Actor input Schema

## `since` (type: `string`):

ISO date (2026-09-01) or full timestamp. Defaults to 7 days ago. Use the changed\_at of your last run as the watermark.

## `until` (type: `string`):

ISO date or full timestamp. Defaults to now.

## `date_type` (type: `string`):

modified for datasets that changed, issued for datasets published for the first time.

## `query` (type: `string`):

Optional full-text filter, same syntax as the search unit.

## `country` (type: `array`):

Publishing country, as the portal spells it: lowercase ISO codes such as be, de, fr. Empty means every country.

## `catalogue` (type: `array`):

Catalogue ids such as data-gov-be, govdata, datos-gob-es. Empty means every catalogue.

## `categories` (type: `array`):

EU data theme codes: ENVI, TECH, AGRI, SOCI, EDUC, ECON, ENER, GOVE, HEAL, INTR, JUST, REGI, TRAN.

## `language` (type: `string`):

Which language to collapse the multilingual titles to. Falls back to English, then to whatever the publisher provided.

## `max_results` (type: `integer`):

How many changed datasets to return, 1 to 500. You are charged per record returned.

## Actor input object example

```json
{
  "since": "2026-09-01",
  "date_type": "modified",
  "country": [],
  "catalogue": [],
  "categories": [],
  "language": "en",
  "max_results": 50
}
```

# Actor output Schema

## `datasets` (type: `string`):

The datasets that moved in your window, newest first, each carrying changed\_at as your next watermark.

## `summary` (type: `string`):

The query echoed back, how big the haystack was, how many records you got, and the licence notice. It carries no records, so a stored result explains itself without being paid for twice.

# 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 = {
    "since": "2026-09-01",
    "date_type": "modified",
    "country": [],
    "catalogue": [],
    "categories": [],
    "language": "en",
    "max_results": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("alka-labs/eu-dataset-changes").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 = {
    "since": "2026-09-01",
    "date_type": "modified",
    "country": [],
    "catalogue": [],
    "categories": [],
    "language": "en",
    "max_results": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("alka-labs/eu-dataset-changes").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 '{
  "since": "2026-09-01",
  "date_type": "modified",
  "country": [],
  "catalogue": [],
  "categories": [],
  "language": "en",
  "max_results": 50
}' |
apify call alka-labs/eu-dataset-changes --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,alka-labs/eu-dataset-changes"
        }
    }
}
```

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/0XfmDKpVw2GfXz1mE/builds/iGDX2zjdl9LirOXwc/openapi.json