Fragment Python API Docs | dltHub

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

Last updated:

FRAGMENT uses OAuth2 for authentication and offers a GraphQL API for data operations. It provides a ledger API for financial products, ensuring accurate tracking and reconciliation of transactions. The REST API base URL is https://api.onfragment.com/api/v1 and OAuth2 client credentials flow with 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 Fragment data in under 10 minutes.


What data can I load from Fragment?

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

ResourceEndpointMethodData selectorDescription
workspaceapi/v1/accounts/meGETGet current workspace/account info
tasksv1/tasksGETitemsList tasks (supports cursor pagination; items contains records)
schemasv1/schemasGETitemsList schemas
tasks_comments_expandv1/tasks?expand=commentsGETitemsTasks with expanded related comments
statushttps://status.onfragment.comGETAPI status page

How do I authenticate with the Fragment API?

Obtain an OAuth2 access token via the client credentials flow from the workspace‑region auth endpoint; include Authorization: Bearer <access_token> on API requests.

1. Get your credentials

  1. In the Fragment dashboard open Settings → Developers or API Clients. 2) Create a new API Client and note the client_id, client_secret, and region. 3) Use client_id and client_secret to request a token from the region‑specific auth URL (e.g., https://auth.us-west-2.fragment.dev/oauth2/token) with grant_type=client_credentials. 4) Use the returned access_token in the Authorization header for API calls. 5) Rotate or revoke tokens in the dashboard as needed.

2. Add them to .dlt/secrets.toml

[sources.fragment_source] client_id = "your_client_id_here" client_secret = "your_client_secret_here" region = "us-west-2"

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 Fragment 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 fragment_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline fragment_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 tasks and schemas from the Fragment 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 fragment_source(client_id, client_secret, region=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.onfragment.com/api/v1", "auth": { "type": "oauth2_client_credentials", "access_token": client_id, client_secret, region, }, }, "resources": [ {"name": "tasks", "endpoint": {"path": "v1/tasks", "data_selector": "items"}}, {"name": "schemas", "endpoint": {"path": "v1/schemas", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="fragment_pipeline", destination="duckdb", dataset_name="fragment_data", ) load_info = pipeline.run(fragment_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("fragment_pipeline").dataset() sessions_df = data.tasks.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM fragment_data.tasks LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("fragment_pipeline").dataset() data.tasks.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 Fragment 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 Fragment?

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