Boards

A board is a named configuration unit (brd_...) with draft/publish revisions. Embeds load a board by id + publishable key (hosted config / Hosted posts) or use a local/BYO adapter with an optional board id.

Embed-only

There is no public /b/... board URL for anonymous visitors. Put the widget inside your authenticated product and pass host-asserted user.

Lifecycle

1. Create a board (dashboard, secret API, or MCP create_board).
2. Edit draft config, toggles, empty state, branding, without moving live clients (revisions).
3. Publish so publishable clients load the new revision.
4. Embed with boardId + publishable key (Hosted) or pass a FeedbackAdapter (BYO).

Hosted inbox

Hosted boards include a dashboard inbox for status changes, archive, and merge. You remain responsible for Hosted content (plain text). Status vocabulary: open | planned | in_progress | shipped | declined.

Cancel Hosted freezes writes immediately, allows dashboard JSON export for 30 days, then deletes Hosted posts and votes. State that on billing and privacy surfaces you control.

Management surfaces

• Secret API / MCP: create, draft, publish, list, get, usage. MCP never accepts post title/body.
• Dashboard-only: API key mint/revoke, webhooks, board delete, branding UI extras, billing, Hosted inbox operations beyond what MCP exposes. Call list_capabilities when unsure.

Related: Configuration · Modes · Statuses · API overview · Pricing