Google BigQuery Python API Docs | dltHub
Build a Google BigQuery-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Google BigQuery is a serverless, highly scalable, and cost-effective multi-cloud data warehouse that provides a REST API for data analysis and management. The REST API base URL is https://bigquery.googleapis.com/bigquery/v2 and all requests require a Bearer token in the Authorization header.
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 Google BigQuery data in under 10 minutes.
What data can I load from Google BigQuery?
Here are some of the endpoints you can load from Google BigQuery:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| datasets | /bigquery/v2/projects/{projectId}/datasets | GET | datasets | Lists all datasets in the specified project. |
| tables | /bigquery/v2/projects/{projectId}/datasets/{datasetId}/tables | GET | tables | Lists all tables in the specified dataset. |
| projects | /bigquery/v2/projects | GET | projects | Lists all projects to which the user has been granted any project role. |
| routines | /bigquery/v2/projects/{projectId}/datasets/{datasetId}/routines | GET | routines | Lists all routines in the specified dataset. |
| tabledata | /bigquery/v2/projects/{projectId}/datasets/{datasetId}/tables/{tableId}/data | GET | rows | List the content of a table in rows. |
How do I authenticate with the Google BigQuery API?
Google BigQuery API uses OAuth 2.0. Requests must include an 'Authorization' header with the value 'Bearer {access_token}', where the access token is obtained via Google's OAuth 2.0 authentication flow or Application Default Credentials.
1. Get your credentials
Google BigQuery does not use API keys for authentication. Instead, use a Service Account. 1. Go to the Google Cloud Console. 2. Navigate to IAM & Admin > Service Accounts. 3. Click Create Service Account, assign it a name and the necessary roles (e.g., BigQuery Data Viewer or BigQuery User). 4. After creation, click on the service account, go to the Keys tab, select Add Key > Create new key, and choose JSON. 5. Download the JSON key file. 6. Set the GOOGLE_APPLICATION_CREDENTIALS environment variable to the path of this JSON file on your machine.
2. Add them to .dlt/secrets.toml
[sources.google_bigquery_source] credentials_path = "/path/to/your/service_account.json"
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 Google BigQuery 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 google_bigquery_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline google_bigquery_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset google_bigquery_data The duckdb destination used duckdb:/google_bigquery.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 /datasets and /jobs from the Google BigQuery 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_bigquery_source(credentials=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://bigquery.googleapis.com/bigquery/v2", "auth": {"type": "bearer", "token": credentials}, }, "resources": [ {"name": "datasets", "endpoint": {"path": "projects/{projectId}/datasets", "data_selector": "datasets"}}, {"name": "tables", "endpoint": {"path": "projects/{projectId}/datasets/{datasetId}/tables", "data_selector": "tables"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="google_bigquery_pipeline", destination="duckdb", dataset_name="google_bigquery_data", ) load_info = pipeline.run(google_bigquery_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_bigquery_pipeline").dataset() sessions_df = data.tables.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM google_bigquery_data.tables LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("google_bigquery_pipeline").dataset() data.tables.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 BigQuery data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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 Google BigQuery?
Request dlt skills, commands, AGENT.md files, and AI-native context.
Available Pipelines
Google BigQuery to DuckDB
Google BigQuery is a serverless, highly scalable, and cost-effective multi-cloud data warehouse that provides a REST API for data analysis and management
Destination: DuckDB
Google BigQuery to Microsoft Fabric
Google BigQuery is a serverless, highly scalable, and cost-effective multi-cloud data warehouse that provides a REST API for data analysis and management
Destination: Microsoft Fabric