SDMX Python API Docs | dltHub

Build a SDMX-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

The SDMX REST API retrieves data or metadata, with parameters not validated before execution. The latest documentation is available at https://sdmx1.readthedocs.io/en/latest/api.html. The API supports two ways to specify items to retrieve. The REST API base URL is https://{provider-domain}/rest and Most SDMX REST services are public and do not require authentication..

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


What data can I load from SDMX?

Here are some of the endpoints you can load from SDMX:

ResourceEndpointMethodData selectorDescription
data{service_root}/data/{flowRef}/{key}GETdataSets (SDMX-JSON messages: observations are inside dataSets and series)Retrieve time series/data for a dataflow (use key to filter series).
dataflow{service_root}/dataflow/{flowId} or /dataflowGETstructure or dataflows (metadata structure varies by provider; client returns MaintainableArtefact objects)List dataflows or get a specific dataflow definition.
datastructure{service_root}/datastructure/{dsdId} or /datastructureGETstructures / dataStructures (DSD definitions returned as structure objects)Retrieve Data Structure Definitions (DSDs).
codelist{service_root}/codelist/{agency}/{id}/{version} or /codelistGETcodelists (code lists returned inside structure metadata)Retrieve codelists used by structures.
categoryscheme{service_root}/categoryschemeGETcategorySchemes (category scheme metadata)Retrieve category schemes.
agency{service_root}/agencyGETagencies (list of agencies/providers)Retrieve list of agencies/providers.

How do I authenticate with the SDMX API?

The SDMX-REST standard and common providers expose public endpoints; requests are plain HTTP(S) GETs. If a provider requires authentication, it will be provider-specific (API key or HTTP auth) and must be documented by that provider.

1. Get your credentials

Check the specific SDMX provider (e.g. Eurostat, IMF, World Bank) documentation or portal for credentials; most do not require credentials. If required, obtain API key or credentials from the provider’s developer portal and add to dlt secrets as directed.

2. Add them to .dlt/secrets.toml

[sources.sdmx_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 SDMX 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 sdmx_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline sdmx_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 data and dataflow from the SDMX 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 sdmx_source(null=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{provider-domain}/rest", "auth": { "type": "none", "null": null, }, }, "resources": [ {"name": "data", "endpoint": {"path": "data/{flowRef}/{key}", "data_selector": "dataSets"}}, {"name": "dataflow", "endpoint": {"path": "dataflow/{flowId}", "data_selector": "structure or dataflows"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="sdmx_pipeline", destination="duckdb", dataset_name="sdmx_data", ) load_info = pipeline.run(sdmx_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("sdmx_pipeline").dataset() sessions_df = data.data.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM sdmx_data.data LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("sdmx_pipeline").dataset() data.data.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 SDMX 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 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 SDMX?

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