meeting_recordings

Count meeting recordings per folder

Count accessible meeting recordings for each requested folder.

The response is a JSON map of folder UUID to count. Submit 1 to 100 folder IDs; an absent folder has no accessible recordings. This intentionally does not distinguish an empty folder from one that is foreign or restricted.

post/public-api/v1/meeting_recordings/counts

Request

Base URL
/ (relative, and the document’s source URL is not known)
URL
/public-api/v1/meeting_recordings/counts
Auth
HTTP bearer and API key in header x-tenant-code

Request body

folder_idsstring[] required

Folder IDs to count video records for. 1 to 100 UUIDs; each must be a valid UUID (bad values return 422 from request validation).

Example request

{
  "folder_ids": [
    "c0a80121-0000-4000-8000-000000000001"
  ]
}

Response

A map of accessible folder IDs to their meeting-recording counts.

VideoFolderCountResponse required

Map of folder ID → count of video records visible to the caller.

Counts are scoped to the caller's tenant and access rights. Folders with no accessible records are omitted, so an absent folder ID means zero — empty, foreign-tenant and permission-restricted folders are indistinguishable by design.

Example response

{
  "c0a80121-0000-4000-8000-000000000001": 42
}

Changes

No recorded changes to this operation across all 1 revision of this API.