Sonos · Authentication Profile

Sonos Authentication

Authentication

The Sonos Control API authenticates third-party integrations with OAuth 2.0 (RFC 6749) using the authorization code grant. The integration redirects the user to the Sonos login service, receives an authorization code, then exchanges it for an access token and refresh token. Access tokens are sent as a Bearer token on every Control API request to api.ws.sonos.com. Confirmed live: the authorize and token endpoints return HTTP 400 to unparameterised requests (present), and api.ws.sonos.com/control/api/v1/households returns 401 without a token.

Sonos secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode flow(s).

CompanyConsumerAudioMusicSmart HomeIoTStreamingSpeakersHome AutomationVoice
Methods: oauth2 Schemes: 1 OAuth flows: authorizationCode API key in:

Security Schemes

SonosOAuth oauth2
· flows: authorizationCode

Source

Authentication Profile

sonos-authentication.yml Raw ↑
generated: '2026-07-21'
method: searched
source: https://docs.sonos.com/docs/authorize
description: >-
  The Sonos Control API authenticates third-party integrations with OAuth 2.0
  (RFC 6749) using the authorization code grant. The integration redirects the
  user to the Sonos login service, receives an authorization code, then
  exchanges it for an access token and refresh token. Access tokens are sent as
  a Bearer token on every Control API request to api.ws.sonos.com. Confirmed
  live: the authorize and token endpoints return HTTP 400 to unparameterised
  requests (present), and api.ws.sonos.com/control/api/v1/households returns 401
  without a token.
summary:
  types:
  - oauth2
  oauth2_flows:
  - authorizationCode
  token_delivery: bearer-header
schemes:
- name: SonosOAuth
  type: oauth2
  description: >-
    OAuth 2.0 authorization code grant. Single scope: playback-control-all.
    Access tokens are short-lived and refreshed with the refresh token via the
    token endpoint.
  flows:
  - flow: authorizationCode
    authorizationUrl: https://api.sonos.com/login/v3/oauth
    tokenUrl: https://api.sonos.com/login/v3/oauth/access
    refreshUrl: https://api.sonos.com/login/v3/oauth/access
    scopes:
    - scope: playback-control-all
      description: Control access to a household's Sonos players and groups.
  sources:
  - https://docs.sonos.com/docs/authorize
  - https://docs.sonos.com/reference/create-authorization-code
  - https://docs.sonos.com/reference/createtoken
  - https://docs.sonos.com/reference/refreshtoken

Work with this as data

Every security artifact here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for security posture

4 MCP tools reach this
  • find_securityBrowse and filter every security artifact in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This security artifact
curl "https://apis.io/api/v1/security/sonos-authentication"
All security posture
curl "https://apis.io/api/v1/security?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.