Enfusion Python API Docs | dltHub

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

Last updated:

Enfusion is an investment management platform offering a Python API for retrieving report data as pandas DataFrames. The REST API base URL is https://your-enfusion-report-url.com and authentication is handled by passing credentials to the EnfusionAPI client constructor, which manages the session for data retrieval..

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


What data can I load from Enfusion?

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

ResourceEndpointMethodData selectorDescription
N/AN/AN/AN/AEnfusion does not publish a public REST API or developer portal.
N/AN/AN/AN/AAccess is gated behind client-specific agreements and web applications.
N/AN/AN/AN/ANo endpoints, pagination, or incremental loading mechanisms are documented.
N/AN/AN/AN/AThe Enfusion Script API is for internal game engine use, not REST integration.
N/AN/AN/AN/ANo public API specification exists for the investment management platform.

How do I authenticate with the Enfusion API?

The Enfusion API supports authentication via a user-defined set of credentials including admin username, admin password, username, and password, typically used to initialize the client session.

1. Get your credentials

Enfusion's proprietary API does not typically utilize a self-serve developer dashboard for API key generation. Instead, access is managed directly through the Enfusion platform. To use the API, you generally obtain your web service URL by navigating to 'My Reports' within the Enfusion software, right-clicking on the desired report, and selecting 'Copy Web Service URL'. If explicit authentication is required for your integration, you must use your standard Enfusion administrative or user credentials (username and password) within your API client configuration.

2. Add them to .dlt/secrets.toml

[sources.enfusion_source] enfusion_user_name = "your_username" enfusion_password = "your_password" enfusion_admin_user_name = "your_admin_username" enfusion_admin_password = "your_admin_password"

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 Enfusion 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 enfusion_pipeline.py

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

Pipeline enfusion_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset enfusion_data The duckdb destination used duckdb:/enfusion.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 reports and reconciliation from the Enfusion 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 enfusion_source(admin_user_name_admin_password_user_name_password=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://your-enfusion-report-url.com", "auth": {"type": "bearer", "token": admin_user_name_admin_password_user_name_password}, }, "resources": [ ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="enfusion_pipeline", destination="duckdb", dataset_name="enfusion_data", ) load_info = pipeline.run(enfusion_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("enfusion_pipeline").dataset() sessions_df = data.none.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM enfusion_data.none LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("enfusion_pipeline").dataset() data.none.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 Enfusion 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 Enfusion?

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