Fetch the recording resource for a call (redirect, JSON, or status)

Returns the recording asset for the given call in one of four ways depending on the recording's lifecycle state and the requested response mode:

• 302 (default) — recording is ready; Location header carries a 15-minute presigned Sautikit CDN URL. The response body is empty. The client can pass Location directly to <audio src=...> — audio bytes do NOT flow through the API process. The Sautikit URL is the only URL ever surfaced; the raw PBX URL is never exposed.

• 200 — JSON mode: send Accept: application/json or ?format=json and a ready recording is returned as JSON metadata instead of the redirect. url/recording_url carry the same presigned Sautikit URL the 302 would have used (15-minute TTL), alongside size_bytes, duration_seconds, mime/content_type, and expires_at. Prefer this mode from browsers: a cross-origin fetch cannot follow the 302 (the redirect hop fails CORS) — fetch the JSON and hand url to <audio src=...> instead.

• 202 — recording capture is still in progress (status: pending). The client should wait retry_after_seconds before re-polling (also reflected in the Retry-After response header). Error code: recording_not_ready.

• 410 — the asset has been pruned per the workspace's storage-tier retention policy and is permanently unavailable. Error code: recording_unavailable.

• 404 — the call does not exist, belongs to a different workspace, or was never configured for recording. Cross-tenant existence is not leaked. Error code: recording_not_found.

Workspace isolation: call_id must belong to the active workspace; otherwise the endpoint returns 404.

call_id may be the Sautikit call UUID or the PBX session id (HD_…) the same call carries on the wire — a caller that watched the call happen can fetch its recording without looking the UUID up first.

Path Parameters

Query Parameters

Response Body