Member event self-registration

A signed-in member registers themselves for a free, registration-open event from their portal. Idempotent; paid events are directed to checkout (never mints an unpaid order).

If you are building a front end

Your front end calls this over the same-origin `/api/v1` proxy — no backend code to write, no schema to design. Endpoints: POST /api/v1/member/my-account/events/:eventOccurrenceId/register.

Bring any front end — hand-written, or generated with Lovable, v0, Bolt, Claude, or Cursor. You get auth, a multi-tenant database, payments through your own Stripe, and email/SMS without writing or hosting a backend.

How to turn it on: Operator switch portal_member_config.allow_event_registration + member 'events' capability.
Who can use it: member session + capability 'events'.
The API behind it: POST /api/v1/member/my-account/events/:eventOccurrenceId/register
Where it lives: /m/[portalSlug]/events

See it in context

Community & member portal — the full walkthrough, step by step: A branded logged-in home for your customers — courses, events, orders, wallet, coach.

Machine-readable

This page is generated from our published capability catalog. Point your AI assistant at /features.json (or /llms.txt) and it can read every feature, how to enable it, and the endpoints behind it — then build against them.