Scope and reading
Use a Bearer token and the workspace ID in the path. The member’s organization is returned inGET /v1/workspaces/:id, in the
response.resource_organization field.
An API key needs workspaces:read to read the workspace and workspaces:write to change that
workspace’s organization.
Folders and favorites only accept application and database. Folder colors are neutral,
red, orange, yellow, green, blue and purple.
Create a folder
name is required. color and position are optional. The response contains the created folder
in response.
Rename, recolor or reorder a folder
response.
Delete a folder
Put or remove a resource in a folder
resource_type=application or resource_type=database. resource_id identifies the
resource the member can access. The body can contain the position within the folder:
response.
Favorite and unfavorite a resource
response. They can be repeated safely.
Activity
Creating, editing or deleting a folder, moving a resource, and favoriting or unfavoriting generates an activity. This applies to actions in the dashboard and in workflows, as well as API key calls made through the CLI, MCP, or the extension. The client doesn’t sendorigin or
author_id; the API sets those fields.
These folders aren’t Flow groups. Groups organize elements on Flow’s local canvas; they don’t
have a group_id shared with this API and aren’t synced or migrated into folders.