Configuration revisions

Each board has a draft and a published revision. Saving a draft does not change what live publishable clients load. Publishing promotes the draft to the live revision number embeds fetch.

Treat publish as a deliberate release of board settings to production clients.

Draft vs published

  • Draft, safe to edit toggles, empty state, branding, and name.
  • Published, what bsw_*_pub_ clients receive until you publish again.

MCP update_draft never publishes. Use publish_board (or the dashboard / secret API) when you intend clients to move.

Secret API shape

With a server-side secret as Authorization: Bearer against https://feedback.bootstrapware.co:

  • PATCH /api/v1/boards/:id: save draft name + config
  • POST /api/v1/boards/:id with { "action": "publish" }: promote draft

Also available: GET /api/v1/boards, GET /api/v1/boards/:id, GET /api/v1/usage. Do not invent extra management routes.

Publish ≠ live entitlement

Publishing stores config. Live bsw_live_pub_ fetch still needs BYO ($9.99) or Hosted ($19.99). Live Hosted post/vote writes need Hosted ($19.99). Test publishable keys work without a paid plan.

Config fields you typically revise: submissionsEnabled, votingEnabled, showVoteCounts, allowAnonymous, requireAuthorToken, emptyState, optional branding. See Configuration.

Related: Configuration · Boards · API overview · Environments · AGENTS.md