Restart playback
Rate limit: Per command · Burst: 20 · Refill: 20 req/s
Restart active playback from the beginning. Playback must be playing or paused.
A 202 response confirms that the platform accepted the request, not that playback restarted. A successful restart emits no webhook. If no playback is active, the platform does not dispatch a restart and emits playback.failed with reason: "no_active_playback".
Use Idempotency-Key to retry safely. Operation-Id correlates the request and any playback.failed webhook; it does not make this command idempotent.
See Playback lifecycle events for complete payload schemas and examples.
Authentication
Send Authorization: Bearer <app_uuid>:<api_key> using an active API key. See Authentication for details.
Path parameters
Session identifier.
Headers
Optional key for safely retrying mutating requests. An explicitly empty header is treated like omission and does not enable replay protection. See Idempotency for details.
optional client-supplied lowercase RFC-4122 v4 UUID returned as operation_uuid; platform generates one when omitted; correlation metadata distinct from Idempotency-Key.
Request
Response headers
Server-owned W3C Trace Context for correlating this response with support and observability data. It is present on successful and error responses. A valid incoming traceparent is linked to, but never becomes, the server-owned trace identifier.
Response
Optional. Set to true on idempotent terminal commands when the session was already in a terminal state at the time the request was received. Absent otherwise.