Create folder
Create a new folder. Folders can be nested up to 7 levels.
Folder paths are automatically generated based on hierarchy. Child folder paths include the paths of their parents.
Authorizations
Can be either an Organization API Key or Personal Access Token (PAT).
Include in the Authorization header as: Bearer YOUR_TOKEN
Body
Name of the folder.
ID of the parent folder. Use the List folders endpoint to retrieve folder IDs.
Maximum nesting depth is 7 levels. A 400 error is returned when the limit is reached.
Scope of the folder.
- If no scope is provided and no parent folder exists, defaults to
organization - If no scope is provided but a parent folder exists, inherits the parent folder's scope
- Child folder scope must match the parent folder's scope
organization, restricted ID of the folder owner. Use the List users or List embed users endpoints to retrieve user IDs.
When true, breadcrumbs for this folder and its descendants start at this folder, hiding ancestor folders and the scope crumb (Shared, <name>'s Documents).
This is useful for scoping navigation to a subtree, for example in embed use cases built around a specific contentPath folder.
Response
Folder created successfully
Unique identifier for the folder
Display name of the folder
Full path to the folder
Visibility scope of the folder
organization, restricted ID of the user that owns the folder
Whether breadcrumbs start at this folder

