Configurator Python API Docs | dltHub

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

Last updated:

Configio API is a REST service providing programmatic access to manage and retrieve data from the Configio Database. The REST API base URL is https://api.configio.com and all requests require an 'X-Token' header, with optional HMAC signature auth for advanced accounts..

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


What data can I load from Configurator?

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

ResourceEndpointMethodData selectorDescription
configurator_models/fscmRestApi/resources/version/configuratorModelsGETitemsRetrieves a list of all configurator models.
resources/resourceGETRetrieves a list of all resources across spaces.
extended_resources/space/{space_id}/unit/{unit_id}/resourceGETLists extended resources for a specific unit.
configurator_model_detail/fscmRestApi/resources/version/configuratorModels/{id}GETRetrieves details for a specific configurator model.
extended_resource_detail/space/{space_id}/unit/{unit_id}/resource/{resource_id}GETRetrieves details for a specific extended resource.

How do I authenticate with the Configurator API?

All API requests require a header named "X-Token" with the API token assigned to you. If advanced authentication is enabled, an Authorization header of "ApiAuth" is required (containing an MD5/HMACSHA256 signature).

1. Get your credentials

Most Configurator-style APIs follow a centralized dashboard workflow: log in to your provider's developer portal or admin console (e.g., 'Settings' or 'Projects' sections), navigate to 'REST API' or 'Developer' settings, and click 'New Token' or 'Generate API Key'. Note that these keys are typically displayed only once upon creation, so ensure you store them securely in a password manager or secrets manager immediately. For some services, you may be required to sign a specific agreement (like a Catalogue or Integration agreement) within the portal before the key generation option becomes available.

2. Add them to .dlt/secrets.toml

[sources.configurator_source] api_key = "your_generated_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 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 Configurator 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 configurator_pipeline.py

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

Pipeline configurator_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset configurator_data The duckdb destination used duckdb:/configurator.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 configurators and models from the Configurator 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 configurator_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.configio.com", "auth": {"type": "bearer", "token": api_token}, }, "resources": [ {"name": "configurator_models", "endpoint": {"path": "fscmRestApi/resources/version/configuratorModels", "data_selector": "items"}}, {"name": "resources", "endpoint": {"path": "resource"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="configurator_pipeline", destination="duckdb", dataset_name="configurator_data", ) load_info = pipeline.run(configurator_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("configurator_pipeline").dataset() sessions_df = data.configurator_models.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM configurator_data.configurator_models LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("configurator_pipeline").dataset() data.configurator_models.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 Configurator 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 Configurator?

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