- Building an internal dashboard that lists recent meetings for NGO staff
- Pulling recordings into a transcription or summarisation pipeline
- Archiving recordings to long-term storage before they expire
- Auditing meeting activity for compliance reporting
How recordings are stored
When a meeting ends, the recording is automatically uploaded to secure cloud storage. Access, metadata, and retention are managed by the platform. After the configured retention period, recordings are automatically removed.Accessing recordings
All recordings endpoints require authentication. Include your Bearer token in theAuthorization header on every request.
Access to recordings is restricted to users with
org_admin permissions. Requests from users without this permission will be rejected with a 403 Forbidden response.Listing recordings
Retrieve a list of all available recordings for your organization. Endpoint:GET /recordings
Authentication: Bearer token required — see Authentication.
Response
An array of recording objects.
Example
Downloading a recording
Use theurl field from the listing response to download a recording. The download URL also requires authentication.
Error responses
| Status code | Cause |
|---|---|
401 Unauthorized | The Bearer token is missing or invalid. |
403 Forbidden | The token is valid but the user does not have org_admin permissions. |
404 Not Found | The requested recording does not exist or has been deleted. |
500 Internal Server Error | An unexpected error occurred in the recordings backend. |