Copernicus Climate Data Store Python API Docs | dltHub

Build a Copernicus Climate Data Store-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

The Copernicus Climate Data Store (CDS) provides a service for programmatic access to climate data, often utilized via the cdsapi Python client library. The REST API base URL is https://cds.climate.copernicus.eu/api and requests require an API key and URL to be configured in the client, often via a local configuration file or environment variables..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Copernicus Climate Data Store data in under 10 minutes.


What data can I load from Copernicus Climate Data Store?

Here are some of the endpoints you can load from Copernicus Climate Data Store:

ResourceEndpointMethodData selectorDescription
processes/api/retrieve/v1/processesGETprocessesList of the available processes (datasets).
process_details/api/retrieve/v1/processes/{process_id}GETDescription of a specific process.
jobs/api/retrieve/v1/jobsGETjobsList of submitted jobs.
job_status/api/retrieve/v1/jobs/{job_id}GETStatus of a specific job.
job_results/api/retrieve/v1/jobs/{job_id}/resultsGETResults of a specific job.

How do I authenticate with the Copernicus Climate Data Store API?

Authentication is handled by providing a Personal Access Token and API URL, typically stored in a ~/.cdsapirc configuration file. The credentials (key and url) are passed to the API client during initialization.

1. Get your credentials

  1. Navigate to the Copernicus Climate Data Store portal at https://cds.climate.copernicus.eu and sign in to your account. 2. Go to your user profile page at https://cds.climate.copernicus.eu/profile. 3. Locate the 'API key' section under your profile settings to view your personal access token.

2. Add them to .dlt/secrets.toml

[sources.copernicus_climate_data_store_source] api_url = "https://cds.climate.copernicus.eu/api" api_key = "your_personal_access_token_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.


How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

uv run dlthub ai toolkit install rest-api-pipeline

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Copernicus Climate Data Store API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

uv run python copernicus_climate_data_store_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline copernicus_climate_data_store_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset copernicus_climate_data_store_data The duckdb destination used duckdb:/copernicus_climate_data_store.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.


Python pipeline example

This example loads collections and datasets from the Copernicus Climate Data Store API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def copernicus_climate_data_store_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://cds.climate.copernicus.eu/api", "auth": {"type": "api_key", "api_key": api_key, "name": "key"}, }, "resources": [ {"name": "processes", "endpoint": {"path": "api/retrieve/v1/processes"}}, {"name": "jobs", "endpoint": {"path": "api/retrieve/v1/jobs"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="copernicus_climate_data_store_pipeline", destination="duckdb", dataset_name="copernicus_climate_data_store_data", ) load_info = pipeline.run(copernicus_climate_data_store_source()) print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.


How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("copernicus_climate_data_store_pipeline").dataset() sessions_df = data.processes.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM copernicus_climate_data_store_data.processes LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("copernicus_climate_data_store_pipeline").dataset() data.processes.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.


What destinations can I load Copernicus Climate Data Store data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Copernicus Climate Data Store?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines