File meetings and Magicasts into a folder
POST/folder.addContents
File up to 100 meetings and Magicasts into a folder in one call. Every
folder member can then read them with meeting.info,
meeting.transcript,
magicast.info, and the related endpoints.
Filing an item that is already in the folder succeeds and changes nothing.
Access: Organization and Personal. Personal tokens need the admin role
on the folder: a viewer gets 403 access_denied, and a folder the token's
owner does not belong to returns 404 folder_not_found. Organization
tokens can change every folder in the account. Personal tokens can only file items the
token's owner can view. Organization tokens can file meetings from any roam
in the account and Magicasts owned by the account. Any other item fails
the whole call with 404 meeting_not_found or magicast_not_found, and
nothing is filed.
Required scope: folders:write
OpenAPI Spec: chat-v1.json
Request
Responses
- 200
- 400
- 401
- 403
- 404
- 405
- 500
Items filed
Bad request. Common causes:
- Missing or invalid
id(missing_parameter/invalid_parameter) - Neither
meetingIdsnormagicastIdsgiven (missing_parameter) - More than 100 items in total, or an ID that is not a UUID (
invalid_parameter/invalid_arguments) - Malformed JSON body or an unknown field (
invalid_json)
Presented invalid authentication credentials.
Forbidden. Common causes:
- Token is missing
folders:write(missing_scope) - Personal token whose owner is a viewer, not an admin, of the folder (
access_denied)
Not found. Common causes:
- Folder not found, or not visible to the caller (
folder_not_found) - A meeting or Magicast that does not exist or that the caller cannot file (
meeting_not_foundwithparam: meetingIds,magicast_not_foundwithparam: magicastIds)
An unsupported method was requested.
An internal error occurred.