Concepts
Object types in Capacities are represented as structures in the API. Every object has a structureId that identifies which type it belongs to.
Retrieve structures for the token's space via GET /space/structures (or capacities.space.structures() in the TypeScript SDK).
Each entry in the structures array includes:
| Field | Description |
|---|---|
id | Structure id — use as structureId when creating objects |
title | Singular display name (e.g. "Book") |
pluralName | Plural display name (e.g. "Books") |
propertyDefinitions | Fields on objects of this type; label fields include labelSet (see Properties) |
labelColor | Color for this type in the UI |
collections | Collections of this structure |
Not every basic structure supports every API operation. At the moment, the following structures are supported via the standard CRUD endpoints:
All content in Capacities is identified by UUIDs.
GET /user/spaces / GET /space.GET /object?id=… or copy an object reference from the app (⋯ menu → Copy object reference). The last segment of a reference URL is the object id:
capacities://SPACE_ID/OBJECT_ID
collections on GET /space/structures, or on objects in the collections array.properties and blocks on objects; listed on each structure's propertyDefinitions from GET /space/structures, or in the app under that property's definition settings.GET /object; required for patch/delete/position operations.Built-in Capacities types use fixed structureId strings:
| Object type | structureId |
|---|---|
| Space | RootSpace |
| Object type | RootStructure |
| Collection | RootDatabase |
| Query | RootQuery |
| Page | RootPage |
| Image | MediaImage |
MediaPDF | |
| Audio | MediaAudio |
| Weblink | MediaWebResource |
| File | MediaFile |
| Tweet | MediaTweet |
| AI Chat | RootAIChat |
| Table | RootSimpleTable |
| Daily note | RootDailyNote |
| Tag | RootTag |
| Task | RootTask |
Custom object types you create in Capacities have their own structureId (a UUID). Look them up via GET /space/structures.
Create a ticket on our feedback board. - Let us know if you have an idea for a feature, improvement or think there is something missing.
Request additions to the documentation. - If your questions are not getting answered, let us know and we will extend the documentation.