Load Data Europa data to DuckDB

data.europa.eu provides various REST APIs to manage, search, and access metadata for European open datasets following DCAT-AP standards. Everything needed to build a working Data Europa → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.

---

Build your Data Europa to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Data Europa to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Data Europa API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.

---

Data Europa API at a glance

These values come from the Data Europa API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Data Europa API?

Requests to restricted API endpoints require a Bearer token in the 'Authorization' header, which is obtained by exchanging client credentials via the 'https://data.europa.eu/auth/middleware/login/service' endpoint.

1. Get your credentials

Data.europa.eu uses a middleware for access control to restricted API endpoints (such as Registry and Store). To obtain an access token, you must have a service account associated with a catalogue. You obtain a JWT Bearer token by sending a POST request to the authentication endpoint using your service account's client ID and client secret: \n\ncurl --location 'https://data.europa.eu/auth/middleware/login/service' \\n--header 'Accept: application/json' \\n--header 'Content-Type: application/json' \\n--data '{\n "client_id": "YOUR_CLIENT_ID",\n "client_secret": "YOUR_CLIENT_SECRET"\n}'\n\nThe response will contain an "access_token" field, which you then pass in the Authorization header of subsequent requests as "Authorization: Bearer <ACCESS_TOKEN>". There is no public user dashboard for self-service API key generation; credentials for service accounts are typically provisioned through administrative contact with the data portal operators.

2. Add them to .dlt/secrets.toml

Copy
[sources.data_europa_source]
credentials = "REPLACE_ME"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.

---

What Data Europa data can I load into DuckDB?

These are the Data Europa endpoints dlt can load into DuckDB:

---

How do I load only new Data Europa records?

The Data Europa API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "datasets", "endpoint": {
    "path": "api/hub/search/datasets",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "initial_value": "2024-01-01T00:00:00Z"},
}}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.

---

What does the generated Data Europa pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading datasets and data from the Data Europa API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def data_europa_source(credentials=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://data.europa.eu/api/hub/",
            "auth": {"type": "bearer", "token": credentials},
        },
        "resources": [
            {"name": "datasets", "endpoint": {"path": "api/hub/search/datasets"}},
            {"name": "catalogues", "endpoint": {"path": "api/hub/search/catalogs"}}
        ],
    }
    yield from rest_api_resources(config)


def load_data_europa_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="data_europa_pipeline",
        destination="duckdb",
        dataset_name="data_europa_data",
    )
    load_info = pipeline.run(data_europa_source())
    print(load_info)


if __name__ == "__main__":
    load_data_europa_to_duckdb()

Run it with python data_europa_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.

---

How do I query Data Europa data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("data_europa_pipeline").dataset()
df = data.datasets.df()
print(df.head())

SQL:

Copy
SELECT * FROM data_europa_data.datasets LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Data Europa to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

• Deploy & schedule — run the pipeline as a managed job with automatic retries.
• Monitor — observable job queues, alerting, and load metrics for every run.
• Transform — promote raw Data Europa loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Data Europa data to?

dlt loads into any of these — only the destination argument changes:

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.

---

Next steps

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack