Get recording artifacts
Returns short-lived signed URLs for a recording’s video and transcript files. Either URL is null when that artifact is not available.
API key authentication. Send your key in the Authorization header as: api-key <your-api-key>.
In: header
Path Parameters
The workspace slug — the {slug} segment of your Clarify workspace URL.
The unique ID of the meeting.
The unique ID of the recording.
Query Parameters
When true, suppresses in-app and Slack notifications for this mutation.
Response Body
application/json
curl -X POST "https://example.com/workspaces/string/meetings/string/recordings/string/artifacts"{ "data": { "videoUrl": "https://storage.clarify.ai/recordings/acme/2f7a9c1e-4b6d-4e8a-9c0f-1d3b5e7a9c62/video.mp4?signature=...", "transcriptionUrl": "https://storage.clarify.ai/recordings/acme/2f7a9c1e-4b6d-4e8a-9c0f-1d3b5e7a9c62/transcript.json?signature=..." }}Stream a live transcript
Opens a server-sent events stream of the meeting transcript while it is being captured, limited to 60 opens per minute per workspace. The stream sends a start frame, one utterance frame per spoken turn carrying a resume id, a heartbeat comment every 20 seconds, an end frame with a reason when capture stops, then a final __stream_complete event. Resume after a disconnect by passing the last id as the after query param with its producerId, or omit producerId to follow the live notetaker bot, else the newest live session, else the earliest session.
Start a recording media upload
Creates a pending recording on the meeting and returns a presigned S3 POST policy for uploading an audio or video file directly to storage. Uploaded media is stored for playback and is not transcribed. Optionally include a transcript in the same request so one recording carries both video and transcript. Submit the file to the returned policy, then confirm the upload. Pass `recordingId` to overwrite a completed manual-upload recording instead of creating a new one.