Event Data with Eventfrog: Embedding, Import and API Integration Options
Whether you want to display an event calendar on your own website, import event data into an existing system, or create events directly via an interface: Eventfrog offers several ways to use event data. The right option depends on what you want to achieve, what technical setup is already in place, and how automated the process should be.
This article includes:
- a complete overview of all available options
- clear recommendations on when each solution is suitable
- detailed information on iFrame, Public API and Organizer API
Overview:
The 3 Options at a Glance
1) iFrame
Short description: Ready-made embedding of an event calendar or event list on an external website.
- Suitable for the pure display of events
- No technical integration into your own systems
- Very low implementation effort
2) Public API
Short description: Public, read-only API for retrieving events, event groups, categories and locations.
- Suitable for custom displays (website, app, newsletter, screens)
- Full control over presentation, filtering and further processing
- Read-only (no creation or modification of events)
3) Organizer API (read)
Short description: Interface for structured access to your own organiser data.
- Suitable for importing your own events into internal systems
- Typically used for CRM, CMS, reporting or BI integrations
- Focus on stable synchronisation of your own event data
The full API specification can be found here: Eventfrog API Reference
Overall Comparison as a Decision Guide
|
Option |
What is it? |
Typical use case |
Technical know-how |
Data in your own system? |
Design/UX customisation |
|---|---|---|---|---|---|
|
iFrame |
Ready-made embedding of a calendar/list view |
I want to display and manage events on my own website |
Low |
No |
Medium |
|
Public API |
Public API for reading events/locations/categories |
I want to populate an event database or my own CMS and make event data visible externally I operate a regional, supra-regional, geographically or category-specific event platform where I present events |
Yes |
Yes |
High |
|
Organizer API read |
Organizer interface (read access, usually “own data”) |
I want to populate my own event database or CMS I want to transfer newsletter subscribers (according to personalisation settings) to a newsletter tool such as Mailchimp I want to populate a BI tool such as Power BI with demographic data of my buyers, sales and check-in data I want to transfer customer data into a CRM such as HubSpot, Salesforce, Pipedrive or similar I want to reconcile incoming payments in a separate finance/accounting tool I want to track food orders (according to personalisation settings or category sales) for an event and transfer them to a restaurant system |
Yes |
Yes |
High |
Details of the Options
Option 1: Display event data on my website (iFrame)
The iFrame is ideal if:
- events should become visible on the website quickly
- no dedicated development team or development time is available
- it is acceptable that the layout is largely “predefined”
Advantages
- quick to go live
- no data maintenance required in your own system
- minimal maintenance effort
Typical setup
- Retrieve the embed code (iFrame) from the Eventfrog cockpit under “Own calendar”
- Insert the code into your website / CMS
- Optional: set parameters / filters (e.g. only specific categories, organisers or locations)
Option 2: Import event data into my systems (Public API)
The Public API allows you to retrieve event data, for example to:
- build your own event lists on your website (including custom filters / sorting)
- import events into an internal tool (e.g. editorial / marketing)
- generate feeds for screens, newsletters or partners
- enrich events with your own data (tags, campaigns, UTM logic)
Typical setup
- Call the API (e.g. events for a specific time period / region)
- Map the data
- Store it in your own system or display it directly
- Update regularly
Option 3: Read events and data via API (Organizer API – Read)
What is it?
The Organizer API (Read) is the read interface for organisers to transfer their own event, sales and buyer data in a structured way to external systems. It is suitable whenever data should be automatically transferred to your own system, CMS or third-party tool and further processed.
When is the Organizer API (Read) the best choice?
This solution is ideal if:
- your own event database or CMS should be populated
- events should be automatically mirrored in an existing system
- newsletter subscribers (according to personalisation settings) should be transferred to tools such as Mailchimp
- BI tools such as Power BI should be populated with sales, check-in or demographic data
- customer data should be transferred into a CRM such as HubSpot, Salesforce or Pipedrive
- incoming payments should be reconciled with a separate finance or accounting tool
- additional data (e.g. food orders from personalisation fields or category sales) should be transferred into restaurant or event management systems
In short: whenever structured, up-to-date data should be automatically processed further.
Typical setup
- Authentication within the organiser context
- Retrieve your own events, sales or ticket buyer data
- Regular synchronisation with your own system (including delta logic for changes)
