Sponsor / exhibitor portal

Event sponsors get a tokenized self-serve page for their booth/sponsorship details — no account, the opaque token is the key.

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: GET /event/sponsor-portal/:token.

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: Per-sponsor link from event management.
Who can use it: token-authenticated.
The API behind it: GET /event/sponsor-portal/:token
Where it lives: /sponsor/:token

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.

Sponsor / exhibitor portal

Event sponsors get a tokenized self-serve page for their booth/sponsorship details — no account, the opaque token is the key.

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: GET /event/sponsor-portal/:token.

How to turn it on: Per-sponsor link from event management.
Who can use it: token-authenticated.
The API behind it: GET /event/sponsor-portal/:token
Where it lives: /sponsor/:token