Google Cloud Platform Setup

Access to the SDM API is provided through Google Cloud. To enable the API and authorize a Google account with a supported Google Nest device, you'll need a Google Cloud project.

You can use an existing Google Cloud project or create a new one. If you don't have a project, or are not familiar with Google Cloud, we recommend you go through the Quick Start Guide first. It guides you through all the steps necessary to get started with Device Access.

Go to the Quick Start Guide

To learn more about creating projects and Google Cloud in general, we recommend the following resources:

Enable the API

The API Library listed in Google Cloud for Device Access is Smart Device Management API. Before you can use Device Access you must enable this API in your project.

Enable Smart Device Management API on the API Enablement page.

OAuth 2.0 Client ID

The SDM API uses Google OAuth for user authorization. In order to complete the authorization process, you need to generate OAuth credentials in the form of an OAuth 2.0 Client ID.

Get an OAuth 2.0 Client ID on the Credentials page.

Unverified apps

The SDM API uses a restricted scope, which means that any apps that use this scope during authorization will be "unverified" unless OAuth API Verification is completed. When using Device Access for personal use, OAuth API Verification is not required.

You may see a "Google hasn't verified this app" screen during the authorization process, which appears if the sdm.service scope is not configured on your OAuth consent screen in Google Cloud. This screen can be bypassed by clicking the Advanced option and then clicking Go to Project Name (unsafe).

See Unverified app screen for more information.


Google Cloud provides metrics, such as usage and latency, for the SDM API. They are released as part of the Smart Device Management API, alongside the other APIs and Services metrics provided on Google Cloud.

If your Google Cloud project has the Smart Device Management API enabled, view your metrics on the Metrics page for the API.

See Monitoring API Usage for more information.