Create session
Creates a new deliberation session owned by the authenticated user.
If prompt is omitted, a facilitation prompt is auto-generated server-side
from the topic, goal, context, and critical fields (with a fallback to a basic prompt).
Returns the created session with a join_url for sharing with participants.
Authorizations
API key authentication. Pass your key as a Bearer token.
Keys use the format hm_live_<32 hex chars>.
Generate keys from your Harmonica dashboard settings.
Body
Request body for creating a new session.
Session topic / title
What the session aims to achieve
Background context for participants (e.g. SESSION.md from a prior session)
Critical question or constraint
Custom facilitation prompt. If omitted, a prompt is auto-generated server-side from the topic, goal, context, and critical fields. Falls back to a basic facilitation prompt if generation fails.
ID of a template to use
Attach the new session to a project (workspace) at create time. Requires editor access to the project.
HAR-1582 - participants for a chain template's first step. Only meaningful when template_id resolves to a chain template; ignored otherwise.
Four of the live chain templates declare roles and an assignment strategy (Delphi panel, Governance Meeting, Many-to-Many Readiness, Example Mapping) and cannot bootstrap without a roster; for those, omitting it returns chain.status "roster_incomplete" on an otherwise successful create. The other seven declare no roles and start with an empty roster.
Pre-session questions shown to participants before facilitation begins
Enable cross-pollination of ideas between participant threads
Enable AI-emitted Polls and ratings widgets (SingleSelect, MultiSelect, RatingScale, RankingList) during the session. When true, the facilitator may call widget tools mid-conversation to present interactive inputs instead of plain text questions.
Who can see aggregated session results.
host(default) — only the session owner can see results.participants— anyone who completed the session can see what others said (drives the end-of-chat "See what others said" link).public— anyone with the session URL can see results without participating. MCP / harmonica-chat callers typically passparticipantssince programmatic and Telegram-distributed sessions usually want distributed visibility.
public, participants, host Distribution channels for the session (e.g. Telegram groups)
Response
Session created
Session object returned after creation. Extends SessionListItem with a join URL.
active Direct URL for participants to join the session
Outcome of chain bootstrap. Present only when template_id named a chain template. Any status other than started or resumed means the session was created and is real but is NOT running as a chain, so treat this field as the authoritative signal rather than assuming a 201 implies a running chain. The most common degraded status is roster_incomplete, because several chain templates declare roles and cannot start without a roster.