Cloud Billing Budget API Python API Docs | dltHub
Build a Cloud Billing Budget API-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The Cloud Billing Budget API manages budgets for Google Cloud projects, allowing programmatic creation, updates, and deletion of budgets. It enables monitoring and controlling costs effectively. Essential for cost management in Google Cloud. The REST API base URL is https://billingbudgets.googleapis.com and All requests require OAuth2 Bearer token (Cloud OAuth scopes) 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 Cloud Billing Budget API data in under 10 minutes.
What data can I load from Cloud Billing Budget API?
Here are some of the endpoints you can load from Cloud Billing Budget API:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| budgets | /v1/{parent=billingAccounts/*}/budgets | GET | budgets | Returns a list of budgets for a billing account (ListBudgetsResponse). |
| budget | /v1/{name=billingAccounts//budgets/} | GET | Returns a single Budget resource. | |
| budgets_v1beta1 | /v1beta1/{parent=billingAccounts/*}/budgets | GET | budgets | v1beta1 variant: list budgets (ListBudgetsResponse with budgets field). |
| budget_v1beta1 | /v1beta1/{name=billingAccounts//budgets/} | GET | v1beta1 variant: get a single Budget resource. | |
| billing_accounts_get | https://cloudresourcemanager.googleapis.com/v1/{name=billingAccounts/*} | GET | Related resource lookup; not part of billingbudgets service but commonly used to verify billing account names. |
How do I authenticate with the Cloud Billing Budget API API?
The API uses Google OAuth2 access tokens passed in the Authorization header as: Authorization: Bearer <ACCESS_TOKEN>. Tokens are obtained via OAuth2 flows, service account JWT exchange, or Application Default Credentials.
1. Get your credentials
- In Google Cloud Console enable the Billing Budgets API (billingbudgets.googleapis.com) for your project.
- Create credentials: either (A) Service Account: Console > IAM & Admin > Service Accounts > Create Service Account, grant roles/billing.viewer or billingbudget.viewer, then create and download a JSON key; or (B) OAuth client: Console > APIs & Services > Credentials > Create OAuth client ID for user‑consent flows.
- If using a service account key, obtain an access token by running: gcloud auth activate-service-account --key-file=KEY.json && gcloud auth print-access-token; or use the Google client libraries/ADC which automatically obtain tokens.
- Ensure the token includes one of the required scopes: https://www.googleapis.com/auth/cloud-platform or https://www.googleapis.com/auth/cloud-billing.
2. Add them to .dlt/secrets.toml
[sources.cloud_billing_budget_api_source] access_token = "ya29..." # short-lived OAuth2 access token or use service_account_key_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 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 Cloud Billing Budget 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 cloud_billing_budget_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline cloud_billing_budget_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset cloud_billing_budget_api_data The duckdb destination used duckdb:/cloud_billing_budget_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline cloud_billing_budget_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 budgets and budget from the Cloud Billing Budget 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 cloud_billing_budget_api_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://billingbudgets.googleapis.com", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "budgets", "endpoint": {"path": "v1/{parent=billingAccounts/*}/budgets", "data_selector": "budgets"}}, {"name": "budget", "endpoint": {"path": "v1/{name=billingAccounts/*/budgets/*}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="cloud_billing_budget_api_pipeline", destination="duckdb", dataset_name="cloud_billing_budget_api_data", ) load_info = pipeline.run(cloud_billing_budget_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("cloud_billing_budget_api_pipeline").dataset() sessions_df = data.budgets.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM cloud_billing_budget_api_data.budgets LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("cloud_billing_budget_api_pipeline").dataset() data.budgets.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 Cloud Billing Budget API 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 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 Cloud Billing Budget API?
Request dlt skills, commands, AGENT.md files, and AI-native context.