Spamhaus Python API Docs | dltHub

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

Last updated:

Spamhaus offers a REST API for reporting malicious entities and accessing real-time reputation data. Authentication is required to access the API. Use cURL to submit data with a JSON payload. The REST API base URL is https://submit.spamhaus.org/api/ and All requests require a Bearer token for 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 Spamhaus data in under 10 minutes.


What data can I load from Spamhaus?

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

ResourceEndpointMethodData selectorDescription
lookup_threats_typeslookup/threats-typesGETReturns an array of threat type objects
submissions_countsubmissions/countGETReturns the total and matched count of submissions
submissions_listsubmissions/listGETReturns an array of submission objects, supports pagination
limits/api/intel/v1/limitsGETReturns account limits and current usage for the Intelligence API
submissions_add_ipsubmissions/add/ipPOSTSubmits an IP address
submissions_add_domainsubmissions/add/domainPOSTSubmits a domain
submissions_add_urlsubmissions/add/urlPOSTSubmits a URL
submissions_add_emailsubmissions/add/emailPOSTSubmits an email address
login/api/v1/loginPOSTLogs in to the Intelligence API and returns a token

How do I authenticate with the Spamhaus API?

Authentication for the Spamhaus API requires a Bearer token to be included in the Authorization header of all requests. For the Intelligence API, this token is obtained by logging in with a username, password, and realm.

1. Get your credentials

The provided documentation does not contain explicit step-by-step instructions for obtaining API credentials from a dashboard. It indicates that an 'AUTH_TOKEN' is required for the Submit API. For the Intelligence API, a token can be obtained by making a POST request to /api/v1/login with a username, password, and realm 'intel'. It is likely that initial credentials (username/password or API key) would be obtained through the Spamhaus dashboard (submit.spamhaus.org/dashboard/), but specific steps are not detailed in the provided API documentation.

2. Add them to .dlt/secrets.toml

[sources.spamhaus_source] token = "your_auth_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 Spamhaus 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 spamhaus_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline spamhaus_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 submissions_list and lookup_threats_types from the Spamhaus 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 spamhaus_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://submit.spamhaus.org/api/", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "submissions_list", "endpoint": {"path": "submissions/list"}}, {"name": "lookup_threats_types", "endpoint": {"path": "lookup/threats-types"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="spamhaus_pipeline", destination="duckdb", dataset_name="spamhaus_data", ) load_info = pipeline.run(spamhaus_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("spamhaus_pipeline").dataset() sessions_df = data.submissions_list.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM spamhaus_data.submissions_list LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("spamhaus_pipeline").dataset() data.submissions_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 Spamhaus 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 Spamhaus?

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