---
title: "play"
method: POST
path: "/groups/{groupId}/playback/play"
tags: ["playback"]
---

# play

`POST /groups/{groupId}/playback/play`

Use the play command in the playback namespace to initiate group playback.

 After a successful play command, if your app is subscribed to the playback namespace, it may first receive a playbackStatus event with PLAYBACK_STATE_BUFFERING before another event with PLAYBACK_STATE_PLAYING. Sonos players will buffer the audio ahead of time when possible, in order to provide the shortest time to play for the user, and to prevent any audio gaps between tracks.

## Response `200`

See the x-muse-error-codes extension for a list of muse errors that generate this response

- Ok — This object represents an empty (default) success. The platform returns an empty object ({}).

## Other responses

- `400` — The given resource/object identifier is invalid
- `401` — A client has not provided authorization credentials to perform a command
- `403` — A client does not have the correct permissions to perform a command
- `404` — See the x-muse-error-codes extension for a list of muse errors that generate this response
- `499` — See the x-muse-error-codes extension for a list of muse errors that generate this response
- `500` — Sonos has experience an unexpected condition it is unable to recover from
- `503` — Player is unable to reach the service.

---

[API](https://skmtc.net/sonos/apis/authorization-api.md) · [All operations](https://skmtc.net/sonos/apis/authorization-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/sonos/authorization-api/versions/243132628620/schema)