API Keys API Python API Docs | dltHub

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

Last updated:

Google API Keys API documentation is available at https://cloud.google.com/api-keys/docs/reference/rest. API keys manage access to Google Cloud services. Use them to restrict access by IP or application. The REST API base URL is https://apikeys.googleapis.com and all requests require an OAuth 2.0 Bearer token with appropriate IAM permissions.

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


What data can I load from API Keys API?

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

ResourceEndpointMethodData selectorDescription
projects_locations_keys_listv2/{parent=projects//locations/}/keysGETkeysLists the API keys owned by a project (key string not included).
projects_locations_keys_getv2/{name=projects//locations//keys/*}GETGets the metadata for an API key (single Key object).
keys_lookupKeyv2/keys:lookupKeyGETFinds the parent project and resource name for a given API key string.
projects_locations_keys_getKeyStringv2/{name=projects//locations//keys/*}/keyStringGETkeyStringReturns the key string for an API key.
operations_getv2/{name=operations/*}GETGets the latest state of a long‑running operation.

How do I authenticate with the API Keys API API?

Uses Google Cloud IAM OAuth 2.0 bearer tokens (Cloud OAuth access tokens). Requests must include Authorization: Bearer <ACCESS_TOKEN>. Some methods also require specific IAM permissions on resources.

1. Get your credentials

  1. Open Google Cloud Console → APIs & Services → Credentials.
  2. Click Create CredentialsOAuth 2.0 Client ID (or create a service account and generate an access token).
  3. Grant the required IAM roles (e.g., roles/apikeys.admin or roles/apikeys.viewer) or ensure the token includes the https://www.googleapis.com/auth/cloud-platform scope.
  4. Use the OAuth flow or service‑account key to obtain an access token and include it in the request header as Authorization: Bearer <ACCESS_TOKEN>.

2. Add them to .dlt/secrets.toml

[sources.api_keys_api_source] token = "YOUR_OAUTH2_ACCESS_TOKEN"

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 API Keys 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 api_keys_api_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline api_keys_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 projects_locations_keys_list and projects_locations_keys_get from the API Keys 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 api_keys_api_source(token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://apikeys.googleapis.com", "auth": { "type": "bearer", "token": token, }, }, "resources": [ {"name": "projects_locations_keys", "endpoint": {"path": "v2/{parent=projects/*/locations/*}/keys", "data_selector": "keys"}}, {"name": "projects_locations_keys_get", "endpoint": {"path": "v2/{name=projects/*/locations/*/keys/*}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="api_keys_api_pipeline", destination="duckdb", dataset_name="api_keys_api_data", ) load_info = pipeline.run(api_keys_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("api_keys_api_pipeline").dataset() sessions_df = data.projects_locations_keys.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM api_keys_api_data.projects_locations_keys LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("api_keys_api_pipeline").dataset() data.projects_locations_keys.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 API Keys 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 API Keys API?

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