Delete a recording

delete

https://api.emaktalk.com/api/v2/call_records/{id}/recordings/{recording_id}

Deletes one recording of a call. Takes no body (or an empty JSON object).

Effect, at once and on every surface (this API, our apps, the MCP connector, the older APIs):

The recording stops playing. Links handed out before the deletion stop working too, and no new one is issued.
Its transcript is hidden. The call's analyses are kept, and the call record stays: call records are never deleted.
Until the recording's purge_at (30 days), POST …/undelete restores it. After that, the deletion is permanent, and the transcript is removed for good once no other recording of the call can still play, be restored or is on legal hold. When the audio was already missing from storage at the deletion, it is permanent at once.

Response: 200 with the record as it now stands: the recording deleted, with deleted_at, deleted_by and purge_at.

Notes:

Who may delete: your account's admins and EMAK support; an API key only with the delete_recordings permission (the "Can delete recordings" switch on the API keys page); users never. GET /me says whether you may delete and restore; a record's permissions.delete_recording also needs a recording of the call that is not on legal hold.
A recording on legal hold can't be deleted by anyone until the hold is lifted. A hold never blocks a restore.
A recording kept in older storage, or still being stored, can't be deleted (409 recording_not_deletable, details.reason unsupported_storage or uploading). While any recording made on the same part of the call is deleted, that part's transcript stays hidden.
503 try_again with retry_after_sec 120: the deletion was not finished, and the recording does not play until the same request, sent again after that time, finishes. Any other 503 changed nothing.
To delete many at once, use POST /call_records/recordings/batch_delete.

Logged: deleted in the call's access log, with who did it.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

uuid

required

The call record's id (a record's id).

recording_id

uuid

required

The recording's id: the id of one of the record's recordings.

Query Params

account_id

uuid

The one account to read, by its id (account.id). Only a caller that may choose the account (EMAK support) sends it, and must; everyone else reads the account they belong to. Absent for a caller that must name it: 400 parameter_missing. Empty or not an account id: 400 parameter_invalid. Given twice: 400 parameter_invalid for any caller. Sent by a caller that reads its own account: 403 forbidden. An account that does not exist or is disabled: 404 reference_not_found. Each names account_id in param. The account is named this way only: a request that sends the legacy account header X-Tenant-Domain-Uuid is refused (400 parameter_unknown).

Responses

Language

Credentials

Bearer

Loading…

Response

Click Try It! to start a request and see the response here! Or choose an example:

application/json

200Deleted. The record as it now stands.

400 parameter_invalid: the id or recording_id is not a UUID. parameter_unknown: a parameter this endpoint does not take. parameter_missing: account_id is absent for a caller that must name the account. request_invalid: a body was sent. This request takes none, or an empty JSON object.

404 recording_not_found: the call has no recording with this id. call_record_not_found: no call with this id is in your account. reference_not_found: the account named by account_id does not exist or is disabled.

405This path doesn't answer this method (method_not_allowed); the Allow header lists the ones it does: GET, HEAD on the reads; GET, HEAD, DELETE on a recording; POST on undelete and batch_delete.

413 request_too_large: a body was sent and it is too large. This request takes none.

429Too many requests (rate_limited). Wait retry_after_sec seconds (the Retry-After header), then retry the same request.

500 internal: something failed on our side; quote request_id when you report it. message says what is known: the deletion committed and only the record could not be read back, its outcome is unknown, or nothing was changed. Read the record before retrying.

503A temporary condition (try_again). Wait retry_after_sec seconds (the Retry-After header), then retry. It never means your key is wrong; only a 401 does.