Skip to main content
GET
Get Recordings by Appointment

Overview

Returns the recording(s) stored for a specific appointment. Recordings are looked up by appointment_id, so the path value is an appointment ObjectId, not a recording id. The caller must be the appointment’s owning doctor. Because only one recording may exist per appointment, the returned data array contains zero or one recording in practice.
The path value is an appointment ObjectId. The endpoint returns the recordings whose appointment_id matches it.

Authentication

string
required
Bearer JWT token. The calling user is derived from the token.

Path Parameters

string
required
The appointment ObjectId. Recordings are looked up by appointment_id; the caller must be the appointment’s owning doctor.

Response

boolean
required
Indicates whether the request succeeded.
array
Array of recording objects for the appointment (0 or 1 element in practice).
Additional fields (for example merged_recording, replaced_recording, __v) may appear on the recording object. Treat any field not documented here as opaque.

Example Request

Example Response

Success (200) - Recording Present
Success (200) - No Recording On File

Error Responses

401 Unauthorized
403 Forbidden (not the owning doctor)
404 Appointment Not Found
The Unauthorized response uses the message field, whereas handler-level errors use the error field. Unexpected server errors return 400 { "success": false, "error": "<message>" }.

Behavior Notes

  • Lookup by appointment: Recordings are located by appointment_id; the path value is an appointment id.
  • Empty array only for existing appointments: If the appointment exists but has no recording, data is []. If the appointment does not exist, the endpoint returns 404 Appointment not found (not an empty array).
  • Ownership: Only the appointment’s owning doctor may read its recordings; otherwise the request returns 403 Forbidden.
  • At most one recording: Because uploads are limited to one recording per appointment, data holds 0 or 1 element.