Concepts
Two website models, companies, entitlements, and Eventyvo Connect terminology.
Eventyvo Connect
Integrator-facing capabilities: embeds, Connect REST API, and outbound webhooks.
This is separate from the Organizer Dashboard API (GraphQL), which is for first-party Eventyvo apps only and is not a public integrator contract.
Two ways to put Eventyvo on your website
Full guide + per-feature matrix: Two website integration models.
| Model | Intent | Tools |
|---|---|---|
| A — Features only; data stays in Eventyvo | Use cards, agenda, register CTA, catalog, or a hosted event site on your domain — visitors use Eventyvo; you do not pull attendee/payment data into your CMS | Embeds, subwebsite, deep links |
| B — Features + related Eventyvo data | Same public UX and securely use registrations, payments, check-ins, orders already stored in Eventyvo inside your CRM / doors / automation | Server Connect REST + verified webhooks |
| Hybrid | Master data (e.g. registrants) already on your site, but you want an Eventyvo-hosted feature (Lab, QR, badges…) | Mirror into Eventyvo first, then A/B for that feature |
Both models keep Connect keys out of the browser. Model B adds server secrets + HMAC. Every feature guide documents both data situations.
Company & subscription
- Company — your organizer organization (tenant boundary for keys and catalog)
- Customized offer — modules + billing interval (ONE_TIME, MONTHLY, YEARLY)
- Entitlement — active APPROVED subscription unlocks features and API capacity
Connect API key
| Prefix | Use |
|---|---|
ev_live_* | Production |
ev_test_* | Test / sandbox events |
- Auto-issued on buy/renew — update servers when you get rotation notices
- Never expose in browser JavaScript or public repos
- Scoped to your company — Model B returns your related Eventyvo data only
Integration approaches
| Approach | Auth | Model | Use when |
|---|---|---|---|
| Embeds | None on visitor site | A (and A+B visitors) | Event card, agenda, registration CTA, catalog |
| Subwebsite | Organizer setup | A | Full multi-page event site / custom domain |
| Connect REST | X-API-KEY server-side | B | Zapier polling, check-in, floor plans, automation |
| Webhooks | HMAC to your HTTPS URL | B | Real-time registrations, payments, check-ins |
Registration: CTA vs full form
| Surface | What visitors get |
|---|---|
| Registration CTA embed | Compact button → opens Eventyvo-hosted register page |
| Subwebsite Register page | Full hosted registration under your event site / domain |
| Forms module | Builder in dashboard; public form URLs on Eventyvo |
There is no Connect “full checkout iframe” embed today. For Model B, sync your CRM with FORM_SUBMISSION / payment webhooks after submit.
Test mode
Events in TEST mode may watermark embeds and pair with ev_test_* keys. See Sandbox & test mode.