HomeGraph API Python API Docs | dltHub
Build a HomeGraph API-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
The HomeGraph API is a REST API for managing smart home devices, enabling cloud-to-cloud communication. It includes methods for syncing devices and reporting state. The API is used for integrating with Google Assistant. The REST API base URL is https://homegraph.googleapis.com and All requests require a Bearer token obtained via OAuth 2.0 with the HomeGraph scope..
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 HomeGraph API data in under 10 minutes.
What data can I load from HomeGraph API?
Here are some of the endpoints you can load from HomeGraph API:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| devices_sync | /v1/devices:sync | POST | payload.devices | Synchronizes devices; response contains a list of device objects. |
| devices_query | /v1/devices:query | POST | payload.devices | Queries the current state of devices; response maps device IDs to state objects. |
| devices_report_state | /v1/devices:reportStateAndNotification | POST | requestId | Reports state changes and optional notifications. |
| devices_request_sync | /v1/devices:requestSync | POST | (none) | Requests Home Graph to re‑sync all devices for a user. |
| devices_get | /v1/devices | GET | devices | Retrieves a list of devices (if available). |
How do I authenticate with the HomeGraph API API?
Include an Authorization header with value 'Bearer {access_token}'. The token is obtained via the Google OAuth 2.0 flow with the HomeGraph scope.
1. Get your credentials
- Open the Google Cloud Console (console.cloud.google.com).\n2. Create or select a project.\n3. Enable the "Home Graph API" in the APIs & Services library.\n4. Navigate to "Credentials" and create an OAuth 2.0 Client ID (or a service‑account key if using a service account).\n5. Configure the OAuth consent screen and add the scope https://www.googleapis.com/auth/homegraph.\n6. Download the client secret JSON (or service‑account JSON).\n7. Use the client ID/secret to request an access token via Google's OAuth 2.0 token endpoint; the resulting Bearer token is used in API calls.
2. Add them to .dlt/secrets.toml
[sources.homegraph_api_source] token = "your_oauth_token_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 HomeGraph 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 homegraph_api_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline homegraph_api_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset homegraph_api_data The duckdb destination used duckdb:/homegraph_api.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline homegraph_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 devices_sync and devices_query from the HomeGraph 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 homegraph_api_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://homegraph.googleapis.com", "auth": { "type": "bearer", "token": access_token, }, }, "resources": [ {"name": "devices_sync", "endpoint": {"path": "v1/devices:sync", "data_selector": "payload.devices"}}, {"name": "devices_query", "endpoint": {"path": "v1/devices:query", "data_selector": "payload.devices"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="homegraph_api_pipeline", destination="duckdb", dataset_name="homegraph_api_data", ) load_info = pipeline.run(homegraph_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("homegraph_api_pipeline").dataset() sessions_df = data.devices_sync.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM homegraph_api_data.devices_sync LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("homegraph_api_pipeline").dataset() data.devices_sync.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 HomeGraph 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 HomeGraph API?
Request dlt skills, commands, AGENT.md files, and AI-native context.