Corona Zahlen Python API Docs | dltHub
Build a Corona-to-database pipeline in Python using dlt with automatic cursor support.
Last updated:
Corona-Zahlen API is a public REST API providing COVID‑19 data for Germany aggregated from the Robert Koch Institute. The REST API base URL is https://api.corona-zahlen.org and No authentication required; all endpoints are publicly accessible..
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 pip install "dlt[workspace]" and start loading Corona Zahlen data in under 10 minutes.
What data can I load from Corona Zahlen?
Here are some of the endpoints you can load from Corona Zahlen:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
germany | /germany | GET | Current aggregated data for Germany (cases, deaths, recovered, weekIncidence, etc.) | |
germany_history_cases | /germany/history/cases | GET | data | Time series of total cases per day. |
germany_history_incidence | /germany/history/incidence | GET | data | Time series of week incidence for Germany. |
states | /states | GET | data | Current data per federal state (keyed by state abbreviation). |
states_history | /states/history | GET | data | Historical time series per state. |
districts | /districts | GET | data | Current data per district (keyed by district AGS). |
vaccinations | /vaccinations | GET | data | Vaccination totals per region. |
maps_districts | /map/districts | GET | PNG heatmap image for districts. |
How do I authenticate with the Corona Zahlen API?
No authentication is required. Simply issue GET requests; for JSON responses set the Accept: application/json header. Image endpoints return image/png.
1. Get your credentials
No credentials are needed. The API can be accessed directly without signing up for an API key or token.
2. Add them to .dlt/secrets.toml
[sources.corona_zahlen_source]
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 venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt 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:
dlt ai toolkit rest-api-pipeline install
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 Corona Zahlen 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:
python corona_zahlen_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline corona_zahlen_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset corona_zahlen_data The duckdb destination used duckdb:/corona_zahlen.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline corona_zahlen_pipeline 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 germany and states from the Corona Zahlen 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 corona_zahlen_source(=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.corona-zahlen.org", "auth": { "type": "", "": , }, }, "resources": [ {"name": "germany", "endpoint": {"path": "germany"}}, {"name": "states", "endpoint": {"path": "states", "data_selector": "data"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="corona_zahlen_pipeline", destination="duckdb", dataset_name="corona_zahlen_data", ) load_info = pipeline.run(corona_zahlen_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("corona_zahlen_pipeline").dataset() sessions_df = data.germany.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM corona_zahlen_data.germany LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("corona_zahlen_pipeline").dataset() data.germany.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 Corona Zahlen data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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.
Troubleshooting
Authentication failures
No authentication is required. If a 401/403 response is received, it is likely due to an intervening proxy or corporate firewall requiring its own credentials.
Rate limiting / 429
The public API may enforce rate limits. If a 429 response is encountered, implement exponential backoff and respect any Retry-After header. Cache responses and honor ETag or Last-Modified headers when present.
Response structure and selectors
Most history endpoints return { "data": [ ... ], "meta": { ... } }; use the data key as the selector. Snapshot endpoints like /germany return a top‑level object without a wrapper array.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Corona Zahlen?
Request dlt skills, commands, AGENT.md files, and AI-native context.