Google APIs

274 APIs7,055 Endpoints22 Categories

API Catalog(4 of 274)

HomeGraph API

The HomeGraph API is the cloud surface that smart-home device makers use to keep Google Assistant in sync with the state of devices in a user's home. Cloud-to-cloud integrations call HomeGraph to request a fresh device sync after the user adds or removes hardware, push state and notification updates when a device changes (lights turn on, door is unlocked), and query the current state of devices Assistant has cached. The API is paired with the Smart Home action fulfilment pattern: device makers serve their own intent handlers and use HomeGraph to keep Google's home graph in sync.

5 endpoints

SAS Portal API

The Google SAS Portal API administers Spectrum Access System deployments for the CBRS 3.5 GHz radio band, the framework that Google uses to coordinate shared wireless spectrum in the United States. It exposes endpoints to manage customers, deployments, GCP project bindings, legacy organization migration, installer secret generation and validation, and access policies. The portal is used by SAS administrators and CBRS device installers to configure how customer devices are registered with Google's SAS service.

24 endpoints

SAS Portal API (Testing)

The SAS Portal API (Testing) is the Google Spectrum Access System staging surface used for managing CBRS (Citizens Broadband Radio Service) deployments, customers, nodes, devices, and installer workflows. It exposes operations for provisioning customer hierarchies, registering and validating CBSDs, signing devices, and managing deployment-level Google Cloud project bindings. The testing endpoint mirrors production semantics so integrators can exercise SAS workflows safely before promoting them to live spectrum operations.

24 endpoints

Smart Device Management API

The Smart Device Management API gives developers and AI agents programmatic access to a Google account holder's Nest devices and the structures and rooms they belong to. It exposes operations to list devices under a user enterprise, retrieve a device's current traits (such as thermostat setpoints, camera images, and doorbell events), and execute commands like setting a target temperature mode. Authorisation is obtained through Device Access partner enrolment plus a per-user OAuth consent flow, after which devices appear under the authorising user's enterprise.

5 endpoints

Connect Your Agent

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.