List Recordings
list_recordingsList recorded meetings from Kontur.Talk, newest first. Filter by title, paginate with limit and offset, and choose fields to include participant details or keep rows compact.
Instructions
Recordings, newest first. Default row: recording_id, title, created_date (ISO-8601, local zone, to the second), created_by, duration, participants_count, participants (≤6; full list via get_recording), status, has_audio. There is no date window here — the recordings endpoint has no date filter, so narrow with query and limit instead. Returns {recordings, count, has_more, next_offset} — the API gives no grand total, so has_more is the only end signal. A requested field the API did not send is simply missing from the row: that means "not in this payload", not "no data at all".
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | page size. | |
| query | No | title search (substring, case-insensitive). | |
| fields | No | row fields to return; omitted → the default set above. description is available here, and so are the bulky comments_count, frame_size, preview_image and qualities blobs. | |
| offset | No | how many to skip (newest first). | |
| participant_fields | No | fields of each participant; omitted → firstname, surname, patronymic, because participants are what inflate a page (measured on meetings at limit=30: 12.4 KB with names, 45.0 KB carrying department/post/ login too). Ask for department, post, login or any other enum value as needed. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |