Valhalla Python API Docs | dltHub
Build a Valhalla-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Valhalla's isochrone API computes reachable areas within specified times from a location, returning results as GeoJSON. It uses isochrone? for requests and defaults to line contours for simplicity. The API supports various transport modes and time intervals. The REST API base URL is http://localhost:8002 and no authentication required by default (self‑hosted Valhalla instances).
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 Valhalla data in under 10 minutes.
What data can I load from Valhalla?
Here are some of the endpoints you can load from Valhalla:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| route | route | GET/POST | trip | Turn‑by‑turn routing; response contains a top‑level trip object with legs, shape, maneuvers. |
| isochrone | isochrone | GET/POST | features | Isochrone service; returns GeoJSON contours as a FeatureCollection (features). |
| matrix | sources_to_targets | GET/POST | sources_to_targets (verbose) / distances,durations (concise) | Time‑distance matrix; verbose mode returns sources, targets, and sources_to_targets. |
| status | status | GET | (top‑level object) | Server status; verbose mode returns keys like version, has_tiles, bbox, warnings. |
| map_matching | trace_route (map_match) | POST | (trip/legs/matched_points in trace_attributes) | Map matching service; returns matched points and edges. |
| locate | locate | GET/POST | (response object) | Locate service returning metadata about nodes/edges. |
How do I authenticate with the Valhalla API?
Valhalla is typically self‑hosted and does not enforce authentication out of the box; clients send plain HTTP requests to the service endpoints.
1. Get your credentials
No provider dashboard credentials are required for a default Valhalla installation. If you deploy Valhalla behind a managed service or gateway, obtain API credentials from that gateway according to its administration UI.
2. Add them to .dlt/secrets.toml
[sources.valhalla_isochrone_source] # Valhalla is self‑hosted and requires no built‑in API key by default. If protecting via gateway, put credentials here, e.g.: # api_key = "your_gateway_api_key_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 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 Valhalla 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 valhalla_isochrone_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline valhalla_isochrone_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset valhalla_isochrone_data The duckdb destination used duckdb:/valhalla_isochrone.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline valhalla_isochrone_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 isochrone and route from the Valhalla 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 valhalla_isochrone_source(=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://localhost:8002", "auth": { "type": "none", "": , }, }, "resources": [ {"name": "isochrone", "endpoint": {"path": "isochrone", "data_selector": "features"}}, {"name": "route", "endpoint": {"path": "route", "data_selector": "trip"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="valhalla_isochrone_pipeline", destination="duckdb", dataset_name="valhalla_isochrone_data", ) load_info = pipeline.run(valhalla_isochrone_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("valhalla_isochrone_pipeline").dataset() sessions_df = data.route.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM valhalla_isochrone_data.route LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("valhalla_isochrone_pipeline").dataset() data.route.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 Valhalla 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.
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 Valhalla?
Request dlt skills, commands, AGENT.md files, and AI-native context.