event_id.
What you can do
- Create and manage events with details like name, dates, timezone, venue, and capacity
- Clone events to duplicate an existing event’s configuration as a starting point
- Manage custom fields to capture event-specific data beyond the standard fields
- Generate badges with unique QR codes for registrant check-in
- Access event questions configured on registration forms
- View event websites and pages associated with each event
Related resources
| Resource | Relationship |
|---|---|
| Registrants | People registered for the event |
| Sessions | Agenda items within the event |
| Speakers | Presenters at the event |
| Sponsors | Organizations supporting the event |
| Packages | Pricing tiers for event registration |
| Discount Codes | Promotional pricing for the event |
| Event Fields | Custom field definitions on the event |
| Event Badges | Badge templates and generation |
| Event Folders | Organizational folders in the Swoogo dashboard |
Key concepts
Event scoping — Nearly all API calls require anevent_id parameter. When listing registrants, sessions, or other sub-resources, you are always listing them within the context of a specific event.
Custom fields — Events support custom fields that extend the standard data model. Use the Event Fields endpoints to manage field definitions, and include custom field values when creating or updating events.
Cloning — The clone endpoint duplicates an event’s configuration (settings, fields, pages) without copying registrant data. This is useful for recurring events or templates.
URL vs domain — The url field returns the event’s slug (e.g., my-conference), which forms the path on the Swoogo-hosted registration page. The domain field returns the custom domain configured for the event’s website (e.g., events.mycompany.com), if one has been set. Use domain when you need the fully qualified custom URL rather than just the slug.