Skip to main content
POST
Create Folder

Authentication and permissions

Token requirements: User-based token (OAuth) or Organization-scoped API key or Workspace-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. Workspace keys must allow every workspace 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.

Body

application/json
teamId
string
required

The ID of the workspace.

name
string
required

The name of the folder.

itemType
enum<string>
required

The non-folder item type this folder can contain. 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 | null

Optional parent folder. Unset creates the folder at the root. The parent must be of the same item_type.

scopedId
string | null

Portable identity: folder_ followed by 22 alphanumeric characters. Omit or leave empty to generate an ID; unique among live folders in the workspace.

Response

200 - application/json

Success

data
data · object

The created folder.