Google Home
# Google Home Local API This is an unofficial documentation of the local API used by the Home app to communicate with GH devices. [GitHub Repo](https://github.com/rithvikvibhu/GHLocalApi) [](https://github.com/rithvikvibhu/GHLocalApi/stargazers) [](https://github.com/rithvikvibhu/GHLocalApi/blob/master/LICENSE.md) ## Getting Started Requests must be made over HTTPS, port 8443, so the base URL for these endpoints is: `https:// :8443/setup/` Get the IP of Google Home from the Google Home app (Device Settings -> End of the list) or from your router. GET requests are simple, in the browser kind. POST requests need to set the header (when there's a body): `content-type: application/json` ## Authentication Since June 2019, most requests (with exceptions like `/setup/eureka_info`) need a local authorization token. There are 3 kinds of tokens involved here: ### Local Authorization Token This token must be sent in all requests in the header `cast-local-authorization-token`. It is short-lived (~1 day) and may change unexpectedly (with a sync, change in homegraph, etc.) ##### Get this token - With access to an android device, [get this token directly by either method](https://gist.github.com/rithvikvibhu/1a0f4937af957ef6a78453e3be482c1f). - Without a device, or to integrate it with a script, use an access token to get the homegraph and extract the token. To get an access token, read the next section. Check the example section for more info. ### Access Token This is a standard google oauth2 access token. It is in the form `ya29.***`. This gives access to the Google Home Foyer API. These expire in an hour. Use this to get the homegraph (and then the local authorization token above). ##### Get this token To get this access token, either a Google account username/password or a Google Master Token is needed. More info in the gis
Description supplied by the publisher; it is a claim, not verified evidence.
- Name
- apisguru:google.home
- Listed in
- APIs.guru
- Publisher
- google.home
- Latest version
- 2.0
- Published
- 2021-06-21
- Evidence
- Listed only, not analyzed yet
What a full analysis of Google Home checks
Not checked yet. About 60 tools are analyzed every hour; each check links to its source when it runs:
- Publisher identity: not checked yet
- Repository ownership: not checked yet
- Organization verification: not checked yet
- Artifact provenance: not checked yet
- Source availability: not checked yet
- Version evidence: not checked yet
- Known vulnerabilities: not checked yet
- Install scripts: not checked yet
- Maintenance: not checked yet
- License: not checked yet
Before you install it
- Open the repository and confirm the account is the one you expect: look-alike names are common.
- Read what it asks for: files, accounts, network access and credentials it needs.
- Prefer a version from a verified publisher when one exists.