Express.js Python API Docs | dltHub

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

Last updated:

Express is a fast, unopinionated, minimalist web framework for Node.js. The REST API base URL is None (self‑hosted; base URL is defined by the deployment, e.g., http://localhost:3000) and Authentication is custom; developers add middleware such as JWT, sessions, or cookies..

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


What data can I load from Express.js?

Here are some of the endpoints you can load from Express.js:

ResourceEndpointMethodData selectorDescription
root/GETReturns a simple hello world string
search/searchGETReturns a top‑level JSON array of results
status/statusGETReturns a JSON object with service status
user/user/:idGETReturns a JSON object representing a user
profile/profileGETReturns a JSON object with profile information

How do I authenticate with the Express.js API?

Express does not enforce any authentication mechanism; developers typically add middleware that checks headers such as Authorization: Bearer or reads session cookies.

1. Get your credentials

Not applicable – Express does not issue API credentials; authentication is implemented by the application developer.

2. Add them to .dlt/secrets.toml

[sources.express_js_source]

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 Express.js 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 express_js_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline express_js_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 search and user from the Express.js 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 express_js_source(=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "None (self‑hosted; base URL is defined by the deployment, e.g., http://localhost:3000)", "auth": { "type": "", "": , }, }, "resources": [ {"name": "search", "endpoint": {"path": "search"}}, {"name": "user", "endpoint": {"path": "user/:id"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="express_js_pipeline", destination="duckdb", dataset_name="express_js_data", ) load_info = pipeline.run(express_js_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("express_js_pipeline").dataset() sessions_df = data.search.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM express_js_data.search LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("express_js_pipeline").dataset() data.search.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 Express.js 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.


Troubleshooting

Authentication Errors

  • 401 Unauthorized – Returned when custom auth middleware rejects a request.
  • 403 Forbidden – Returned when the authenticated user lacks required permissions.

Not Found Errors

  • 404 Not Found – Returned when a route does not match any defined endpoint.

Server Errors

  • 500 Internal Server Error – Returned when an uncaught exception occurs in a route handler.

Pagination

  • Express does not provide built‑in pagination; developers implement it manually (e.g., ?page=2&limit=20).

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.


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 Express.js?

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