Delete recordings in a batch

post

https://api.emaktalk.com/api/v2/call_records/recordings/batch_delete

Deletes up to 100 recordings by id, each with the single delete's effects, and answers a result per id in the order sent.

Effect: for each recording, the single delete's: it stops playing at once, links handed out before included; its transcript is hidden; its analyses are kept; it can be restored until its purge_at.

Response: { data: [...] }, one result per id: deleted, already_deleted, not_found, not_deletable, try_again or failed. One recording's outcome never fails the others.

Notes:

Not atomic: each recording is deleted on its own. try_again: nothing changed for that recording; send it again. failed: its outcome could not be confirmed, or the change was left unfinished; read its call record.
To delete a call's audio, send all of its recordings' ids.
The same callers as the single delete may batch delete; anyone else is refused before anything is deleted.

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

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

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).

Body Params

The recordings to delete, by id: 1 to 100 distinct recording ids (a recording's id). To delete a call's audio, send every one of its recordings' ids.

recording_ids

array of uuids, unique

required

length between 1 and 100

recording_ids*

Responses

Language

Credentials

Bearer

Loading…

Response

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

application/json

200A result per recording id, in the order sent.

404 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.

409 recording_not_deletable, details.reason shared_storage: deleting recordings isn't available on this deployment, so the whole request is refused before anything is deleted; retrying won't help.

413 request_too_large: the body is too large.

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

500Something failed on our side (internal), and nothing was handed over. Quote request_id when you report it.

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.