Authentication overview
Same Eventyvo account for app and docs; server-side Connect API keys.
Sign in on docs
Sign in at /auth/login with your Eventyvo account. Connect setup (API keys, webhooks, embed builder) lives entirely on docs.eventyvo.com — Developer portal.
Optional SSO: when EVENTYVO_SHARED_COOKIE_DOMAIN=.eventyvo.com is configured, a session from app.eventyvo.com can carry over. You still manage Connect on docs.
What requires sign-in
- Developer portal — API keys, webhooks, companies/events, Connect notifications
- Embed builder
- Personalized getting started checklist
Public /docs/** guides and /embed/** widgets do not require login.
Two models, two auth stories
| Model | Browser | Your servers |
|---|---|---|
| A — Features; data stays in Eventyvo | Embeds / hosted pages — no Connect key | Not required |
| B — Related Eventyvo data in your stack | Still no Connect key | X-API-KEY + webhook HMAC |
See Two website integration models.
Connect API authentication (Model B)
Server-side only:
X-API-KEY: ev_live_xxxxxxxx
| Prefix | Use |
|---|---|
ev_live_* | Production |
ev_test_* | TEST events / sandbox — Sandbox guide |
Keys are scoped to your company — Model B returns your related Eventyvo data, not other organizers’.
Never call Connect REST from browser JavaScript on your marketing site — use embeds or your backend. Checklist: Security checklist.
The Organizer Dashboard API (GraphQL) is not documented for external integrators and is not part of Connect.