Stadia Maps Python API Docs | dltHub

Stadia Maps is a mapping and location services API providing geocoding, routing, elevation, and map‑matching. The REST API base URL is https://api.stadiamaps.com and All requests require an API key passed as a query parameter or Authorization header..

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 Stadia Maps data in under 10 minutes.

---

What data can I load from Stadia Maps?

Here are some of the endpoints you can load from Stadia Maps:

---

How do I authenticate with the Stadia Maps API?

Authentication is performed with an API key. Include it as the query parameter api_key=YOUR_API_KEY or set the header Authorization: Stadia-Auth YOUR_API_KEY.

1. Get your credentials

1. Sign in to the Stadia Maps client dashboard (https://stadiamaps.com/).
2. Navigate to Manage Properties.
3. Open Authentication Configuration for the desired property.
4. Click Generate new API key (or view an existing one).
5. Copy the displayed API key and store it securely; it will be used as the api_key value in dlt.

2. Add them to .dlt/secrets.toml

Copy
[sources.stadia_maps_source]
api_key = "your_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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
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:

Copy
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 Stadia Maps 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:

Copy
python stadia_maps_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline stadia_maps_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 elevation and map_match from the Stadia Maps API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

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

@dlt.source
def stadia_maps_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.stadiamaps.com",
            "auth": {
                "type": "api_key",
                "api_key": api_key,
            },
        },
        "resources": [
            {"name": "elevation", "endpoint": {"path": "elevation/v1", "data_selector": "height"}},
            {"name": "map_match", "endpoint": {"path": "map_match/v1", "data_selector": "routes"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="stadia_maps_pipeline",
        destination="duckdb",
        dataset_name="stadia_maps_data",
    )
    load_info = pipeline.run(stadia_maps_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):

Copy
import dlt

data = dlt.pipeline("stadia_maps_pipeline").dataset()
sessions_df = data.elevation.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM stadia_maps_data.elevation LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("stadia_maps_pipeline").dataset()
data.elevation.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 Stadia Maps data to?

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

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

---

Troubleshooting

Authentication errors

• 401 Unauthorized – Returned when the api_key is missing, malformed, or revoked. Ensure the API key is correct and included as a query parameter (api_key=YOUR_KEY) or in the Authorization: Stadia-Auth YOUR_KEY header.

Rate limiting

• 429 Too Many Requests – Indicates the request quota has been exceeded. The response includes a Retry-After header specifying when to retry. Reduce request frequency or request a higher quota from the dashboard.

Pagination

• Many list endpoints (e.g., /geocode/v1/search) support pagination via limit and offset query parameters. If a response includes a next URL, continue fetching until no next link is present.

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack