Creditreform Python API Docs | dltHub

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

Last updated:

Creditreform provides various REST API and web service interfaces for integrating credit management, collection, and economic data services into business processes. The REST API base URL is The base URL is configured per customer/integration environment, often provided as a 'Webservice URL' or 'Keycloak Server-URL' during onboarding. and requests require OAuth-based authentication, typically involving a Client ID and Client Secret via a Keycloak server..

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


What data can I load from Creditreform?

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

ResourceEndpointMethodData selectorDescription
collection_cases/collection-api/v1/casesGETRetrieves a list of collection cases.
collection_debtors/collection-api/v1/debtorsGETRetrieves a list of collection debtors.
collection_events/collection-api/v1/eventsGETRetrieves a list of collection events.
credit_reports/credit-reportsGETRetrieves commercial credit information reports.
monitoring_alerts/monitoring/alertsGETRetrieves monitoring notifications.

How do I authenticate with the Creditreform API?

Authentication is typically handled via a Keycloak server using Client ID and Client Secret credentials, as noted in third-party integration documentation. Access is provided by Creditreform upon request.

1. Get your credentials

Creditreform’s official API page does not describe a self-service API-key dashboard. To obtain access, contact your responsible Creditreform regional office or use the contact form on the Creditreform API page and request access to the API platform/Collection API. Creditreform states that testing is possible through the same contact process. After approval and provisioning, use the credentials and environment details supplied by Creditreform or shown in its developer portal; do not assume that a generic API key can be generated independently. For some Creditreform integrations, credentials are provisioned as a client ID and client secret by Creditreform rather than created by the customer.

2. Add them to .dlt/secrets.toml

[sources.creditreform_source] client_id = "your_creditreform_client_id" client_secret = "your_creditreform_client_secret" # Add the base URL/token URL supplied by Creditreform if required by the integration: # base_url = "https://your-creditreform-api-base-url" # token_url = "https://your-creditreform-auth-server/token"

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 Creditreform 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 creditreform_pipeline.py

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

Pipeline creditreform_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset creditreform_data The duckdb destination used duckdb:/creditreform.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 Collection API and CrediCONNECT from the Creditreform 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 creditreform_source(client_id=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "The base URL is configured per customer/integration environment, often provided as a 'Webservice URL' or 'Keycloak Server-URL' during onboarding.", "auth": {"type": "api_key", "api_key": client_id, "name": "client_secret"}, }, "resources": [ {"name": "collection_cases", "endpoint": {"path": "collection-api/v1/cases"}}, {"name": "credit_reports", "endpoint": {"path": "credit-reports"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="creditreform_pipeline", destination="duckdb", dataset_name="creditreform_data", ) load_info = pipeline.run(creditreform_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("creditreform_pipeline").dataset() sessions_df = data.collection_cases.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM creditreform_data.collection_cases LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("creditreform_pipeline").dataset() data.collection_cases.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 Creditreform 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 Creditreform?

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