Debian Packages Python API Docs | dltHub

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

Last updated:

Debian Sources is an API that exposes Debian source package metadata, listings, search, file contents and other package-related information in JSON form. The REST API base URL is https://sources.debian.org/api/ and No authentication required; public read-only API..

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


What data can I load from Debian Packages?

Here are some of the endpoints you can load from Debian Packages:

ResourceEndpointMethodData selectorDescription
listapi/listGETpackagesReturns listing of all packages.
prefixapi/prefix/{prefix}GETpackagesPackages filtered by prefix.
searchapi/search/{query}GETresultsSearch for packages.
src_package_versionsapi/src/{packagename}/GETversionsReturns package versions.
src_file_listingapi/src/{packagename}/{version}/{path}GETfilesList folders and files in a folder.
src_file_infoapi/src/{packagename}/{version}/{path/to/file}GETGet information about a file (including the raw_url).
info_packageapi/info/package/{packagename}/{version}GETPackage metadata and metrics.
sha256api/sha256/?checksum=...&package=...GETmatchesReturns matches for file search by checksum.
ctagapi/ctag/?ctag=...&package=...GETReturns tag search results.
pingapi/ping/GETService status and last update timestamp.

How do I authenticate with the Debian Packages API?

No authentication is required as this is a public read-only API. Responses are JSON and pretty-printed by default, unless the X-Requested-With header is set to XmlHttpRequest for compact output.

1. Get your credentials

No authentication is required for this public read-only API.

2. Add them to .dlt/secrets.toml

[sources.debian_packages_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 Debian Packages 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 debian_packages_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline debian_packages_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 list and search from the Debian Packages 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 debian_packages_source(=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://sources.debian.org/api/", "auth": { "type": "none", "": , }, }, "resources": [ {"name": "list", "endpoint": {"path": "api/list", "data_selector": "packages"}}, {"name": "search", "endpoint": {"path": "api/search/{query}", "data_selector": "results"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="debian_packages_pipeline", destination="duckdb", dataset_name="debian_packages_data", ) load_info = pipeline.run(debian_packages_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("debian_packages_pipeline").dataset() sessions_df = data.list.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM debian_packages_data.list LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("debian_packages_pipeline").dataset() data.list.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 Debian Packages 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

API Errors

The Debian Packages API uses standard HTTP error codes to indicate issues. Common errors include:

  • 404 Not Found: Returned when a requested resource does not exist.
  • 400 Bad Request: Indicates that the request was malformed or invalid.
  • 500 Internal Server Error: May be returned for server-side issues.

Since the API is public and read-only, there are no authentication-related errors.

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 Debian Packages?

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