Delete Recording
Recordings
Delete Recording
Delete an appointment’s recording, removing both the stored file and the database record.
DELETE
Delete Recording
Overview
Deletes the recording stored for a specific appointment. The recording is located byappointment_id. The stored file is removed and the database record is deleted; the deleted record is returned in the response.
Authentication
Bearer JWT token. The calling user is derived from the token.
Path Parameters
The appointment ObjectId whose recording should be deleted. The recording is located by
appointment_id.Response
Indicates whether the recording was deleted successfully.
The deleted recording record.
Additional fields (for example
merged_recording, replaced_recording, duration_seconds, __v) may appear on the returned object. Treat any field not documented here as opaque.Example Request
Example Response
Success (200)
Error Responses
401 Unauthorized
400 No Recording On File
400 Storage Delete Failed
The
Unauthorized response uses the message field; handler-level errors use the error field. If there is no recording on file for the appointment, the request currently fails with a 400 error rather than a clean 404, so confirm a recording exists (via GET /recordings/{appointmentId}) before deleting. Storage-delete failures also surface as a 400 with the raw storage error message.Behavior Notes
- Lookup by appointment: The recording is located by
appointment_id. - File then record: The stored file is removed before the database record is deleted; the deleted record is returned in
data. - Confirm first: Deleting when no recording exists returns a
400error, so verify existence beforehand.