Register a participant for a Livestorm session via API
domain: developers.livestorm.co · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Get the target session ID (from a session list or right after creating it).
POST to https://api.livestorm.co/v1/sessions/{id}/people with a data object describing the registrant (email plus any custom fields array).
For high-volume imports, use POST /sessions/{id}/people/bulk instead, which runs as an async job.
Handle 402 (contact allowance reached) and 422 (unprocessable entity) as distinct failure modes from 401/403 auth errors.
Confirm registration by watching for the people.registered webhook or polling GET /sessions/{id}/people.
Known gotchas
A 402 response means the workspace's active-contacts allowance is exhausted, not a validation error — retries won't help until the plan is upgraded.
Bulk registration is job-based and asynchronous; the 201 response only confirms the job was accepted, not that every registrant was created — track completion via the job.ended webhook.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?