Eventogy Partner API
Connect your systems to Eventogy
The Eventogy Partner API is a server-to-server API for integrating your own systems (CRM, BI, scheduling, data platforms) with your Eventogy account. It is separate from the Eventogy web application: it has its own base path, its own OAuth 2.0 client-credentials credentials and its own bearer tokens.
What you can reach
| Family | Examples | Scope |
|---|---|---|
| Core | events, agendas (+ elements, tracks), attendees, registrations | Event content + tenant-wide people |
| Content | forms (+ questions, options), pages (+ blocks), emails (+ blocks, batches), compilations, meetings, content, locations, Q&A categories, mobile pages | Per event |
| Attendee data | attendee tags, attendee note questions (+ options) | Per event |
| Theming & reports | event styles, palettes (+ components), report configs | Tenant-wide / per event |
| Accounts & access | users, stakeholders, roles, teams, event stakeholders | Tenant-wide / per event |
| Configuration | settings, app settings (+ setting data) | Tenant-wide / per event |
| Activity & engagement | activities, attendee activities, host-app activities, likes | Tenant-wide / per event |
| Reference tables | status types, input types, languages, event types, … (read-only lookups) | Tenant-wide |
The core hierarchy: an event owns its content (agendas, forms, pages, emails, …); an agenda has elements and tracks. Attendees are tenant-wide people; a registration links an attendee to an event (that's where status/approval live). Every resource shares the same envelope, pagination, and incremental-sync model — described once under Conventions.
Privileged data. Accounts, configuration, and activity resources expose internal-facing data. Credentials are never exposed or writable (
password/remember_token/secret fields are always stripped),settingsis limited to the public tier, and theactivitiesaudit log leaves out the history of settings and of login artefacts (password resets, magic links) — but grant write access to these families deliberately. See the note in the Resource Reference.