Nest · OAuth Scopes

Nest OAuth Scopes

OAuth 2.0 searched

Nest publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Nest API on a user’s behalf.

Tokens are issued from https://www.googleapis.com/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyHardwareSmart HomeIoTHome AutomationThermostatGoogleDevice Access

Scopes: 1 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://nestservices.google.com/partnerconnections/{project-id}/auth

Token URL
https://www.googleapis.com/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
https://www.googleapis.com/auth/sdm.service	Single coarse-grained scope granting the Smart Device Management API access to view, control, and manage the Nest devices the user has authorized for the Device Access project. Per-device and per-trait consent is chosen by the end user in the Partner Connections Manager flow rather than through additional OAuth scopes.	authorizationCode

📄 Provider scope reference: https://developers.google.com/nest/device-access/authorize

Source

OAuth Scopes

generated: '2026-07-20'
method: searched
source: https://developers.google.com/nest/device-access/authorize
docs: https://developers.google.com/nest/device-access/authorize
schemes:
  - name: GoogleOAuth2
    source: https://developers.google.com/nest/device-access/authorize
    flows:
      - flow: authorizationCode
        authorizationUrl: https://nestservices.google.com/partnerconnections/{project-id}/auth
        tokenUrl: https://www.googleapis.com/token
scopes:
  - scope: https://www.googleapis.com/auth/sdm.service
    description: >-
      Single coarse-grained scope granting the Smart Device Management API access
      to view, control, and manage the Nest devices the user has authorized for
      the Device Access project. Per-device and per-trait consent is chosen by the
      end user in the Partner Connections Manager flow rather than through
      additional OAuth scopes.
    flows: [authorizationCode]
    sources: [https://developers.google.com/nest/device-access/authorize]
notes: >-
  The SDM API exposes exactly one OAuth scope. Granular authorization is expressed
  through the device/trait selections the user makes at consent time, not through
  a scope hierarchy.