Waymark / Routes / developers.livestorm.co Work with custom registration fields via the Livestorm API
domain: developers.livestorm.co · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Fetch the event's fields array (under attributes.fields on the event resource) to see each field's id, type, and whether it's required. Build a custom registration form client-side using that field list instead of Livestorm's hosted registration page. Submit registrants via POST /sessions/{id}/people with a fields array of {id, value} pairs matching the event's field ids. Manage custom attributes beyond the 14 default fields from workspace settings, then reference them by id in the fields array. Read submitted values back from registrant_detail.fields in the people.registered webhook payload or a people list call. Known gotchas Field ids for custom attributes are workspace-specific — hardcoding only email/first_name/last_name covers just the built-in required fields. Required fields vary per event; omitting a required custom field on registration returns a 422 rather than silently succeeding.
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