Google SERP API Python API Docs | dltHub

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

Last updated:

The Google SERP API allows developers to extract structured Google search results automatically. It uses a credit-based system and supports various SERP features. HasData's API provides real-time data with 100% accuracy. The REST API base URL is https://api.hasdata.com and all requests require an x-api-key header (API key).

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 Google SERP API data in under 10 minutes.


What data can I load from Google SERP API?

Here are some of the endpoints you can load from Google SERP API:

ResourceEndpointMethodData selectorDescription
google_serp/scrape/google/serp?q={q}&...GETorganicResultsMain SERP endpoint; returns parsed SERP features (organicResults, ads, knowledge graph, local results, etc.).
google_serp_images/scrape/google/serp?search_type=images&q={q}GETimagesResultsImage search results (when search_type=image).
google_serp_news/scrape/google/serp?search_type=news&q={q}GETnewsResultsNews search results (when search_type=news).
google_serp_videos/scrape/google/serp?search_type=videos&q={q}GETonlineVideosVideo results (when search_type=videos).
google_serp_local/scrape/google/serp?engine=google_maps&q={q}&location={location}GETlocalResultsLocal/Maps result sets (local pack, maps).
google_serp_batch/scrape/batchPOST(varies)Batch scraping endpoint (used for bulk requests).

How do I authenticate with the Google SERP API API?

HasData uses a simple API key placed in the request header named x-api-key. Include this header on every request: x-api-key: .

1. Get your credentials

  1. Sign in to https://app.hasdata.com (or create an account). 2) Open Account Settings → API keys. 3) Copy your API key and store it in your secrets.toml as api_key = "...". 4) Use the key in the x-api-key header for all requests.

2. Add them to .dlt/secrets.toml

[sources.google_serp_api_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 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 Google SERP API 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 google_serp_api_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline google_serp_api_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 google_serp and google_serp_images from the Google SERP API 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 google_serp_api_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.hasdata.com", "auth": { "type": "api_key", "api_key": api_key, }, }, "resources": [ {"name": "google_serp", "endpoint": {"path": "scrape/google/serp", "data_selector": "organicResults"}}, {"name": "google_serp_images", "endpoint": {"path": "scrape/google/serp", "data_selector": "imagesResults"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="google_serp_api_pipeline", destination="duckdb", dataset_name="google_serp_api_data", ) load_info = pipeline.run(google_serp_api_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("google_serp_api_pipeline").dataset() sessions_df = data.google_serp.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM google_serp_api_data.google_serp LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("google_serp_api_pipeline").dataset() data.google_serp.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 Google SERP API 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 Google SERP API?

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