Restore a deleted recording

post

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

Restores a recording deleted through this API, within 30 days of its deletion (before its purge_at). Takes no body (or an empty JSON object).

Effect: the recording plays again and its transcript reappears, for everyone who may see the call. Links handed out before the deletion work again until they expire. A legal hold placed since the deletion stays.

Response: 200 with the record as it now stands.

Notes:

The same callers as the delete may restore.
A transcript hidden by another deleted recording of the same part of the call stays hidden until that one is restored too.
503 try_again: either nothing changed, or the restore is written and the audio is not back yet (retry_after_sec is then 120). Retry after retry_after_sec either way. Once the audio is back, the retry answers 409 recording_not_deleted: the recording is restored and plays.
500 internal: message says whether the restore committed. Read the record before retrying.
Any other refusal changes nothing.

Logged: restored 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

200Restored. 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 restore 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.