Recordings
Get a short-lived link to listen to a call's recording, delete it, and know how long recordings are kept.
A call is recorded unless its character's recording is off: both voices, in one stereo WAV file (the person on the left, the AI on the right, 16 kHz). The face's video is never recorded.
The recording on a call
GET /v1/calls/{call_id} carries the recording's state:
{ "status": "ready", "seconds": 94, "bytes": 6016044, "deleted_unix": null }status | What it means |
|---|---|
pending | The call is on, or has just ended and its file is being finished |
ready | It can be listened to |
none | Nothing was said: the call never connected |
off | The character's recording was off for this call |
deleted | It was deleted, by you or when its time was up |
To turn recording off for a character, set its record field to false; it is true unless you switch it off.
Get a link to listen
/v1/calls/{call_id}/recording{
"url": "https://api.daxov.com/recordings/call_2Gx7Mb9KpQ4sVn1ZrT6e.1793301000.k3Jx9Q…",
"expires_unix": 1793301000,
"seconds": 94,
"bytes": 6016044
}The link plays the WAV (audio/wav) without a key: the link itself is the permission. It works for 15 minutes, takes byte ranges so a player can seek, and is never cached. Nothing in it can be guessed or changed. Ask for a new link each time someone presses play, rather than storing one.
curl https://api.daxov.com/v1/calls/call_2Gx7Mb9KpQ4sVn1ZrT6e/recording \
-H "Authorization: Bearer $ACME_SECRET_KEY"Refusals
| Status | Code | Why |
|---|---|---|
| 409 | recording_not_ready | The call is still going, or its file is being finished. Try again in a few seconds |
| 404 | no_recording | The recording is none, off or deleted; the message says which |
| 404 | not_found | No such call in your key's env (a live call for a test key, or the other way round) |
| 503 | recording_unavailable | The recording can't be reached right now. Try again in a minute |
A link that has expired, or was changed, answers 404 not_found; one whose recording has been deleted since answers 404 no_recording, at once.
Delete a recording
/v1/calls/{call_id}/recordingDeletes the recording's files. Links to it stop working at once. It answers { "ok": true, "call_id": "call_…" }, also for a call without a recording, or one already deleted. A call of your key's other env is 404, and nothing is deleted.
While the call is still going, or its file is still being finished, it is 409 call_running: end the call first, then try again in a few seconds.
How long recordings are kept
Each organization keeps its recordings for a set number of days: 30 unless we've changed it for you (1 to 3,650). Older ones are deleted by themselves, every hour. Ask us to change your organization's number.
When a recording is ready
The recording.ready webhook is sent once per call, when its recording is final:
{
"id": "evt_…",
"type": "recording.ready",
"created_unix": 1793300110,
"data": {
"call_id": "call_2Gx7Mb9KpQ4sVn1ZrT6e",
"character_id": "chr_4fT9kQ2mXw7LbN3pZs8V",
"source": "api",
"env": "live",
"metadata": { "ticket": 7 },
"seconds": 94,
"bytes": 6016044,
"created_unix": 1793300000,
"settled_unix": 1793300100,
"ready_unix": 1793300110
}
}It never carries a link, since links expire: ask for one when you need it. See Webhooks.