Skip to main content

Overview

Meeting materials (attachments, background images, avatars, and so on) use a “presigned direct upload” model:
The file itself doesn’t go through the SDK; the SDK only issues URLs and maintains resource records.

Upload

1. Get an upload URL

PresignedPutObjectType values: The returned key is the resource key of this file; you use it for both registering and downloading later.

2. Upload the file directly

3. Register the resource

ResourceCreateReq also has a parentId field for putting the resource into a folder.

Download

First get a signed download URL, then download it yourself:
Provide one of the two parameters.

Query the resource list

Filters supported by ResourceListReq: parentId (folder), meetingId, resName (fuzzy name match), resType. In the returned ResourceInfo, isFolder set to true means this is a folder node; you can use its id as the parentId for querying the next level.