Skip to main content
GET
List Folders

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Team-scoped API key. Send a bearer access token for one of these identities. The permissions and resource restrictions below also apply.
Permissions joined by + are all required; or separates alternatives. Full-access keys still cannot call endpoints marked unsupported. Team keys must allow every team checked by the request. OAuth access depends on the user’s roles and resource access.

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

teamId
string
required

The ID of the team.

itemType
enum<string>
required

The non-folder item type of folders to list. Required — folders are scoped per type, and FOLDER_ITEM_TYPE_UNSPECIFIED and FOLDER_ITEM_TYPE_FOLDER are rejected.

Available options:
FOLDER_ITEM_TYPE_UNSPECIFIED,
FOLDER_ITEM_TYPE_FOLDER,
FOLDER_ITEM_TYPE_WORKFLOW,
FOLDER_ITEM_TYPE_GUIDANCE,
FOLDER_ITEM_TYPE_FORM
parentFolderId
string

Optional. When set, return only the direct children of this folder. When unset, return all folders of the given type for the team (a flat list; use parent_folder_id to reconstruct the tree).

pageSize
integer<int32>

Maximum number of results to return. Default is 1000, maximum is 2000. When neither page_size nor page_token is set, all results are returned.

pageToken
string

Token for pagination. Leave empty for the first request.

Response

200 - application/json

Success

data
Folder · object[]

The folders. Use parent_folder_id to reconstruct the tree.

nextPageToken
string | null

Token for retrieving the next page of results. Empty if no more results.