Langflow Python API Docs | dltHub

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

Last updated:

The Langflow API provides endpoints to run flows, manage builds, and handle webhooks. Key endpoints include POST /v1/run/{flow_id} to execute flows and POST /v1/webhook/{flow_id} to trigger flows via webhook. The API also supports file uploads and management. The REST API base URL is http://localhost:7860/api and Most endpoints require an API key provided via the x-api-key header or as an api_key query parameter..

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


What data can I load from Langflow?

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

ResourceEndpointMethodData selectorDescription
all/api/v1/allGETReturn all available Langflow component types
version/api/v1/versionGETReturn Langflow API version
config/api/v1/configGETReturn deployment configuration (requires API key)
flows/api/v1/flows/GETList flows (top‑level array)
flow/api/v1/flows/{flow_id}GETGet a single flow by ID
flows_basic_examples/api/v1/flows/basic_examples/GETList example flows (top‑level array)
projects/api/v1/projects/GETList projects (top‑level array)
project/api/v1/projects/{project_id}GETRead a project (object with nested flows)
api_keys/api/v1/api_key/GETapi_keysList API keys for the current user
health_check/health_checkGETHealth check for DB/chat connectivity
monitor_messages/api/v1/monitor/messagesGETList messages (supports filters/pagination)
starter_projects/api/v1/starter-projects/GETReturn list of starter/project templates

How do I authenticate with the Langflow API?

Langflow accepts a Langflow API key in the x-api-key request header or as the api_key query parameter for authenticated endpoints (versions 1.5+). Some deployments use Authorization: Bearer plus organization headers.

1. Get your credentials

  1. Open your Langflow deployment UI (or admin console). 2) Go to Settings/Profile or the API Keys section (Docs: GET/POST /api/v1/api_key/). 3) Use POST /api/v1/api_key/ (or the UI "Generate token" / "Create API key") to create a new API key. 4) Copy and store the returned api_key securely (the UI or POST response shows the key once). 5) Use the key in x-api-key header or ?api_key= query param.

2. Add them to .dlt/secrets.toml

[sources.langflow_source] api_key = "your_langflow_api_key_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 Langflow 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 langflow_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline langflow_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 flows and run from the Langflow 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 langflow_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "http://localhost:7860/api", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "flows", "endpoint": {"path": "api/v1/flows/"}}, {"name": "run", "endpoint": {"path": "api/v1/run/{flow_id}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="langflow_pipeline", destination="duckdb", dataset_name="langflow_data", ) load_info = pipeline.run(langflow_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("langflow_pipeline").dataset() sessions_df = data.flows.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM langflow_data.flows LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("langflow_pipeline").dataset() data.flows.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 Langflow 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 Langflow?

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