DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS /// DOCS
API·CONCEPTS·MODULES OVERVIEW

Modules overview

The v1 API surface is organized by module. Each one corresponds to a workspace concept and exposes a small set of endpoints under /api/public/v1/. The list below covers everything the API will eventually surface — modules marked (coming soon) are planned but not yet shipped.

Tables

The substrate. Tables hold structured data; every other module ultimately ties back to a table.

Endpoints: /tables, /tables/{id}.

Records

Rows inside a table. Records are typed against the parent table's column schema and are how you read and write actual data.

Endpoints: /tables/{id}/records, /tables/{id}/records/{id}.

Pages

Rich documents inside the workspace. Useful for syndicating help docs, status pages, or any long-form content.

Endpoints: /pages, /pages/{id}.

Skills

Reusable capabilities (prompts, routines, integration calls). The API surfaces skill metadata — name, description, scope — so external automation can decide which to invoke.

Endpoints: /skills, /skills/{id}.

Tasks

The unit of work. Filter by status, project_id, or assignee.

Endpoints: /tasks, /tasks/{id}.

Projects (coming soon)

Project containers — collections of tasks, tables, and pages scoped to a single initiative. Read access lands first; write access follows.

Planned endpoints: /projects, /projects/{id}.

Custom Fields (coming soon)

The schema layer underneath tables — column definitions, formula fields, reference fields, AI-generated fields. The API will let you inspect and (eventually) mutate column schemas without going through the UI.

Planned endpoints: /tables/{id}/columns, /tables/{id}/columns/{id}.

Routines (coming soon)

Code-execution pipelines that chain functions and produce side effects. The API will expose trigger and status endpoints so external systems can kick off and observe routine runs.

Planned endpoints: /routines, /routines/{id}/runs.

Onniebots (coming soon)

Autonomous agents owned by the workspace. The API will surface bot configuration and run history.

Planned endpoints: /bots, /bots/{id}.

Workspace metadata (implicit)

Every endpoint scopes to the workspace the key belongs to — no explicit workspace ID in the URL. Member directories, billing, and settings are not exposed through v1.