Skip to main content
This API organizes your personal view of applications and databases. It doesn’t change the resource or create a configuration shared with other people.

Scope and reading

Use a Bearer token. Personal organization is returned in GET /v1/users/me, in the response.resource_organization field. An API key needs account:read to read the profile and account:write to change personal organization. Folders and favorites only accept these resource types: 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

Send one or more fields:
folder_id is the personal folder’s ID. The response contains the updated folder in response.

Delete a folder

Deleting removes the folder and its organization links; it doesn’t delete the applications or databases.

Put a resource in a folder

Parameters: The body can contain the resource’s position within the folder:
If the resource is already in another personal folder, this operation moves it to the indicated folder. The response returns the updated organization in response. To remove just the folder link:

Favorite and unfavorite a resource

To favorite:
The body can contain the favorite’s position:
To unfavorite:
Favorite and folder are independent preferences: a resource can be in both. Both operations return the updated organization in response and are safe to repeat.

Activity

Creating, editing or deleting a folder, moving a resource, and favoriting or unfavoriting generates an activity. The dashboard and workflows use the same API; API key calls made through the CLI, MCP, or the extension also enter the history. The client doesn’t send origin or author_id: those fields are set by the API.