Eventzilla Integration Guide
Overview
This guide explains how to connect Bridged with Eventzilla to read event content including event details, attendee data, ticket information, and transaction records. The integration supports reading this data for activation, qualification, and nurture playbooks where event context is needed.
Eventzilla is an event management platform that provides a REST API for accessing events, tickets, attendees, and transactions. The API is organized around RESTful, resource-oriented URLs using JSON format .
Primary Use Case: Read Event Content
For Bridged's event experience integrations, the primary use case is reading event-related data, including:
Data Type | Use in Bridged |
|---|---|
Event details | Context for event-specific conversations |
Attendee data | Personalize outreach and qualification |
Ticket information | Registration and ticket type data |
Transaction records | Payment and registration confirmation |
Prerequisites
Before starting, ensure you have:
An Eventzilla account with API access enabled
Your API Key (generated from Settings → App Management)
Note: The API base URL is https://www.eventzillaapi.net/api/v2. All requests require an x-api-key header for authentication .
Connection Methods
Method | Best for | Setup complexity |
|---|---|---|
API Key (Direct REST API - Preferred) | Automated data pulls | Low |
Webhook (via automation platforms) | Real-time event triggers | Medium |
Manual Export (CSV) | One-time or backup data pulls | Low |
Recommendation: Use direct API Key authentication for automated syncs. The API uses simple header-based authentication .
Step 1: Obtain Your API Key
Log in to your Eventzilla account
Navigate to Settings → App Management
Click Generate API Key
Copy the displayed API key value
⚠️ Important: Store the API key securely. You will need it for all API requests.
Step 2: Configure Bridged to Connect to Eventzilla
Log in to your Bridged dashboard
Navigate to the Integrations section. If you do not see this section, contact
support@bridged.mediaClick Eventzilla → Connect Account
Enter the following credentials:
Field | Description |
|---|---|
API Key | Your Eventzilla API key |
API Base URL |
|
Click Connect
API Request Example
To verify your token works, test with the list events endpoint :
bash
curl -X GET "https://www.eventzillaapi.net/api/v2/events" \
-H "x-api-key: YOUR_API_KEY"Step 3: Available API Endpoints
Based on Eventzilla's REST API documentation, the following endpoints are available for reading event data :
Endpoint | Method | Description |
|---|---|---|
| GET | Retrieve a list of live events |
| GET | Get details for a specific event |
| GET | List tickets associated with an event |
| GET | List transactions (registrations/payments) for an event |
| GET | Retrieve attendees for an event |
Step 4: Alternative - Webhook via Automation Platforms
For real-time event triggers, Eventzilla can be connected to automation platforms that support webhook actions:
Option A: Make.com
Create a Make.com account
Add an Eventzilla module as the trigger
Select a trigger event (e.g., "Watch Attendees", "Watch Transactions")
Connect your Eventzilla account using API Key
Set the action to Webhook pointing to Bridged:
URL:
https://gateway.bridged.media/webhooks/eventzilla
Option B: Pipedream
Create a Pipedream account
Create a workflow with Eventzilla trigger (e.g., "New Event Created")
Connect your Eventzilla account
Add an HTTP request action to send data to Bridged webhook endpoint
Step 5: Alternative - Manual CSV Export
If automated sync is not required, Eventzilla supports manual exports:
Export Attendee Data
Log in to your Exhibitor Profile
Locate the event and click "Manage leads"
Click "Export leads" button
Download CSV file
Export Waiting List Data
Navigate to Registration → Approval/Waiting List
Click "Export Waiting List" button
Download CSV file containing attendee details
Bulk sync limit: Each bulk operation is limited to 50 records per request.
Step 6: Configure Sync Settings
Setting | Options | Description |
|---|---|---|
Data objects | Events, Attendees, Tickets, Transactions | Which event data to read |
Sync frequency | Hourly, Daily, Weekly | How often to refresh data |
Sync method | API Direct, Webhook, Manual CSV | Preferred data access method |
Common Use Cases
Playbook | How Event Data Is Used |
|---|---|
Activation | Read attendee list to trigger pre-event reminders via WhatsApp |
Qualification Agent | Read attendee registration data and ticket types for lead scoring |
Nurture & Conversion | Read event details and transaction data for post-event follow-up |
Example Conversation Powered by Eventzilla Data
When an attendee asks "What events are coming up?", Bridged:
Reads event data from Eventzilla API (
/eventsendpoint)Filters by upcoming dates
Returns event information conversationally
Rate Limiting & Performance
Rate limits are in place to ensure optimal performance and security
Bulk operations: Maximum 50 records per request
API uses industry-standard security protocols and encryption
Security & Permissions
Eventzilla uses API Key authentication via
x-api-keyheaderAPI keys are generated in Settings → App Management
All API calls should be made over TLS 1.2+
You can revoke access by regenerating your API key
Troubleshooting
Issue | Likely cause | Solution |
|---|---|---|
Connection fails (401) | Invalid API key | Regenerate API key in Settings → App Management |
No data returned | Wrong endpoint or event ID | Verify endpoint URL and event ID |
Export button not visible | No scans performed | Perform at least one scan before export appears |
Rate limiting | Too many requests | Reduce sync frequency |
Webhook not received | Automation platform configuration | Verify webhook URL and authentication |
Support
For integration support, contact your Bridged account manager or email support@bridged.media.
For Eventzilla-specific questions:
Developer Documentation: https://developer.eventzilla.net/docs/
Eventzilla Website: https://www.eventzilla.net
Support: Contact via Eventzilla platform