Profisee Python API Docs | dltHub

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

Last updated:

Profisee is a master data management platform that provides a REST API for programmatic access to platform data and operations. The REST API base URL is https://<instance_url>/rest and supports both API Key authentication via x-API-key header and OAuth 2.0 bearer token 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 Profisee data in under 10 minutes.


What data can I load from Profisee?

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

ResourceEndpointMethodData selectorDescription
entitiesapi/v1/entitiesGETRetrieves a list of available master data entities
entity_recordsapi/v1/entities/{entityName}/recordsGETRetrieves records for a specific entity
entity_metadataapi/v1/entities/{entityName}/metadataGETRetrieves metadata definitions for a specific entity
record_detailsapi/v1/entities/{entityName}/records/{recordId}GETRetrieves details for a specific master data record
entity_data_qualityapi/v1/entities/{entityName}/dataqualityGETRetrieves data quality issues for a specified entity

How do I authenticate with the Profisee API?

Profisee supports two main authentication methods: an API Key (sent via the x-API-key header) or OAuth 2.0 (Bearer token). For API Key authentication, include the 'x-API-key' header; for OAuth 2.0, include the 'Authorization' header with a 'Bearer ' value.

1. Get your credentials

To obtain credentials for the Profisee REST API, navigate to the 'Accounts and Teams' section within 'Profisee FastApp Studio'. Depending on your organization's security configuration, you may retrieve a Client ID for simple header-based authentication, or you may need to configure an OAuth2 application (client) in your identity provider (e.g., Microsoft Entra ID) to obtain a Client ID and Client Secret for the OAuth2 client_credentials flow.

2. Add them to .dlt/secrets.toml

[sources.profisee_source] profisee_base_url = "https://your-instance.profisee.com/profisee/rest/v1" profisee_client_id = "your_client_id_here" profisee_client_secret = "your_client_secret_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 harness:

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:

dlthub 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 Profisee 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 profisee_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline profisee_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 /api/v1/entities and /api/v1/entities/{entityName}/records from the Profisee 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 profisee_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://<instance_url>/rest", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "entity_records", "endpoint": {"path": "api/v1/entities/{entityName}/records", "data_selector": "items"}}, {"name": "entities", "endpoint": {"path": "api/v1/entities"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="profisee_pipeline", destination="duckdb", dataset_name="profisee_data", ) load_info = pipeline.run(profisee_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("profisee_pipeline").dataset() sessions_df = data.entity_records.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM profisee_data.entity_records LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("profisee_pipeline").dataset() data.entity_records.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 Profisee 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.
dlthub ai toolkit data-exploration install dlthub ai toolkit dlthub-platform install

Was this page helpful?

Community Hub

Need more dlt context for Profisee?

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

Available Pipelines