Safe Browsing API v4 Python API Docs | dltHub

Build a Safe Browsing API v4-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Google Safe Browsing API v4 enables client applications to check web resources against Google's lists of unsafe web resources for malware or phishing threats. The REST API base URL is https://safebrowsing.googleapis.com and all requests require an API key passed as a URL 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 add "dlt[hub]" and start loading Safe Browsing API v4 data in under 10 minutes.


What data can I load from Safe Browsing API v4?

Here are some of the endpoints you can load from Safe Browsing API v4:

ResourceEndpointMethodData selectorDescription
threat_listsv4/threatListsGETthreatListsLists the Safe Browsing threat lists available for download.
threat_matchesv4/threatMatches
POSTmatchesFinds the threat entries that match the Safe Browsing lists.
full_hashesv4/fullHashes
POSTmatchesFinds the full hashes that match the requested hash prefixes.
threat_list_updatesv4/threatListUpdates
POSTFetches the most recent threat list updates.

How do I authenticate with the Safe Browsing API v4 API?

Authentication is performed by passing an API key as a query parameter named 'key' in the request URL. No specific HTTP headers are required for authentication beyond standard content-type headers.

1. Get your credentials

  1. Sign in to the Google Cloud Console. 2. Select or create a project. 3. Navigate to APIs & Services > Library. 4. Search for 'Safe Browsing API' and click Enable. 5. Navigate to APIs & Services > Credentials. 6. Click 'Create Credentials' and select 'API Key'. 7. Copy the generated key.

2. Add them to .dlt/secrets.toml

[sources.safe_browsing_api_v4_source] api_key = "YOUR_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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 Safe Browsing API v4 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:

uv run python safe_browsing_api_v4_pipeline.py

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

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

Inspect your pipeline and data:

uv run dlthub 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 threatMatches

and threatListUpdates
from the Safe Browsing API v4 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 safe_browsing_api_v4_source(key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://safebrowsing.googleapis.com", "auth": {"type": "api_key", "api_key": key, "name": "key"}, }, "resources": [ {"name": "threat_lists", "endpoint": {"path": "v4/threatLists", "data_selector": "threatLists"}}, {"name": "threat_matches", "endpoint": {"path": "v4/threatMatches:find", "data_selector": "matches"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="safe_browsing_api_v4_pipeline", destination="duckdb", dataset_name="safe_browsing_api_v4_data", ) load_info = pipeline.run(safe_browsing_api_v4_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("safe_browsing_api_v4_pipeline").dataset() sessions_df = data.threat_lists.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM safe_browsing_api_v4_data.threat_lists LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("safe_browsing_api_v4_pipeline").dataset() data.threat_lists.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 Safe Browsing API v4 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 harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Safe Browsing API v4?

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

Available Pipelines