Stop recording
Rate limit: Per command · Burst: 20 · Refill: 20 req/s
Stop the Recording identified by recording_uuid.
The 202 Accepted response confirms that the command was admitted. It does not confirm that the recording has stopped or that the final audio is available.
Later lifecycle outcomes:
recording.endedis emitted immediately after the recording file is closed. It carriesrecording_uuid, the signed publicmedia_url, theoperation_uuidof the originating recording-create request, andduration.- A
media_urlrequest started at that boundary may briefly remain on the growing-recording path while finalization completes. - A
recording.failedevent is not always final. If a later stop command is accepted, the same recording also emitsrecording.ended.
The signed media_url carried by recording.ended expires 24 hours after
that event is emitted by default.
After internal finalization it supports HTTP Range requests.
See Recording 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.
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.