Ledger Python API Docs | dltHub

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

Last updated:

The Ledger Enterprise API documentation provides guides for creating API users and getting started with API integration. The latest version includes authentication and API key management. For detailed API reference, visit the official documentation. The REST API base URL is https://re.vault.ledger.com/v1/rest and All requests require a JWT Bearer token (Authorization: Bearer ) or API User & API Key headers for operator 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 Ledger data in under 10 minutes.


What data can I load from Ledger?

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

ResourceEndpointMethodData selectorDescription
accounts/accountsGETresultsRetrieve a list of accounts.
transactions/transactions/searchGETresultsSearch and list transactions.
users/usersGETresultsList users in the workspace.
settlements/settlementsGETresultsList settlement records.
requests/requestsGETresultsList request objects.
account/accounts/{account_id}GETRetrieve details for a single account.
transaction/transactions/{transaction_id}GETRetrieve a single transaction by ID.

How do I authenticate with the Ledger API?

Include Authorization: Bearer <jwt> for token auth. For API operator auth, send X-Ledger-API-User: <user> and X-Ledger-API-Key: <key> with each request.

1. Get your credentials

  1. In the Ledger Enterprise UI, open Users and click Invite User → select API Operator. 2. Enter a name and public key, then confirm creation. 3. Open the newly created operator's permissions modal and click Generate API Key to obtain an API Key ID and Secret. 4. Call the /auth/token endpoint (POST) with the API Key ID and Secret to receive a JWT token. 5. Use the returned token in the Authorization: Bearer <token> header for API calls.

2. Add them to .dlt/secrets.toml

[sources.ledger_source] access_token = "your_jwt_token_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 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 Ledger 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 ledger_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline ledger_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 accounts and transactions from the Ledger 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 ledger_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://re.vault.ledger.com/v1/rest", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "accounts", "endpoint": {"path": "accounts", "data_selector": "results"}}, {"name": "transactions", "endpoint": {"path": "transactions/search", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="ledger_pipeline", destination="duckdb", dataset_name="ledger_data", ) load_info = pipeline.run(ledger_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("ledger_pipeline").dataset() sessions_df = data.accounts.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM ledger_data.accounts LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("ledger_pipeline").dataset() data.accounts.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 Ledger 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 Ledger?

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