HomeGraph API Python API Docs | dltHub

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

Last updated:

HomeGraph API provides support for accessing and managing first-party and third-party devices stored in Google's Home Graph database. The REST API base URL is https://homegraph.googleapis.com and all requests require a Bearer token obtained via OAuth 2.0 flow using service account credentials.

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 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:

ResourceEndpointMethodData selectorDescription
devices_syncv1/devices
POSTdevicesGets all the devices associated with the given third-party user.
devices_queryv1/devices
POSTGets the current states in Home Graph for the given set of the third-party user's devices.
devices_report_statev1/devices
POSTReports device state and optionally sends device notifications.
devices_request_syncv1/devices
POSTRequests Google to update device metadata for the given user.
agent_usersv1/agentUsers/{agentUserId}DELETEUnlinks the given third-party user from your smart home Action.

How do I authenticate with the HomeGraph API API?

The API requires an OAuth 2.0 access token passed in the Authorization header as a Bearer token. Requests must also include a Content-Type: application/json header.

1. Get your credentials

The HomeGraph API does not use standard API keys for authorization; it requires OAuth 2.0 service account credentials. To obtain these: 1. Navigate to the Google Cloud Console and select your project. 2. Enable the HomeGraph API in the API Library. 3. Navigate to APIs & Services > Credentials. 4. Click 'Create Credentials' and select 'Service account'. 5. Provide a name, skip optional steps, and finish. 6. Once created, click on the service account, navigate to the 'Keys' tab, click 'Add Key' > 'Create new key', and select JSON. 7. The JSON file containing your private key will be downloaded to your machine. Ensure your application uses this file to authenticate with the https://www.googleapis.com/auth/homegraph scope.

2. Add them to .dlt/secrets.toml

[sources.homegraph_api_source] credentials = "REPLACE_ME"

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 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:

uv run 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:

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 devices

and devices
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(credentials=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://homegraph.googleapis.com", "auth": {"type": "bearer", "token": credentials}, }, "resources": [ {"name": "devices_sync", "endpoint": {"path": "v1/devices:sync", "data_selector": "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:

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 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 HomeGraph API?

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