Skip to main content
POST
Create session

Authorizations

Authorization
string
header
required

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

application/json

Request body for creating a new session.

topic
string
required

Session topic / title

goal
string
required

What the session aims to achieve

context
string

Background context for participants (e.g. SESSION.md from a prior session)

critical
string

Critical question or constraint

prompt
string

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.

template_id
string

ID of a template to use

project_id
string

Attach the new session to a project (workspace) at create time. Requires editor access to the project.

roster
object[]

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.

questions
object[]

Pre-session questions shown to participants before facilitation begins

cross_pollination
boolean
default:false

Enable cross-pollination of ideas between participant threads

widgets_enabled
boolean
default:false

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.

results_visibility
enum<string>
default:host

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 pass participants since programmatic and Telegram-distributed sessions usually want distributed visibility.
Available options:
public,
participants,
host
distribution
object[]

Distribution channels for the session (e.g. Telegram groups)

Response

Session created

Session object returned after creation. Extends SessionListItem with a join URL.

id
string<uuid>
required
topic
string
required
goal
string
required
status
enum<string>
required
Available options:
active
participant_count
integer
required
created_at
string<date-time>
required
updated_at
string<date-time>
required
join_url
string<uri>
required

Direct URL for participants to join the session

chain
object

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.