Eventzilla is an all-in-one cloud event management and registration platform for in-person, virtual, and hybrid events. It covers the full lifecycle — registration forms, multi-tier ticketing, attendee management, QR check-in, automated communications, and analytics — and integrates with Zoom, Salesforce, and Mailchimp. Its REST API exposes events, attendees, tickets, transactions, and checkout workflows.
Power end-to-end data operations for your Eventzilla API with Nexla. Our bi-directional Eventzilla connector is purpose-built for Eventzilla, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Eventzilla or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Eventzilla workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
To connect Nexla to Eventzilla, you need an active Eventzilla account and an API key. Eventzilla's API uses key-based authentication, where the key is passed as a request header (x-api-key) with every API call. The API is accessible only over HTTPS.
Eventzilla API keys are managed through your account's App Management settings. Each key is scoped to your organization and authenticates all API requests made on your behalf.
Navigate to Settings > App Management in your account dashboard.
Click Create New Application (or the equivalent button for adding a new API key).
Enter a name for the application or integration (for example, "Nexla Integration") to help identify its purpose later.
Click Save or Generate Key to create the application and generate an API key.
Copy the API key value displayed. This is the value you will enter in the API Key Value field when configuring your Nexla credential.
Important
Store your API key in a secure location. Once you leave the page, the full key value may not be displayed again. You can always disable old keys and generate new ones from the same App Management settings page.
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
Eventzilla uses API Key Authentication. Enter your Eventzilla API key in the API Key Value field. This is the key you generated in your Eventzilla account under Settings > App Management. Your API key is sent as a header value (x-api-key) with every request to the Eventzilla API, allowing Nexla to authenticate and retrieve or write data on behalf of your account. The key will be transmitted securely over HTTPS and stored encrypted in Nexla.
Keep your API key confidential. Anyone with access to this key can make API calls to your Eventzilla account. If a key is compromised, disable it immediately from the Eventzilla App Management settings and generate a new one.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Eventzilla connector tile, then select the credential that will be used to connect to the Eventzilla account, and click Next; or, create a new Eventzilla credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Eventzilla endpoints. Each template is designed specifically for the corresponding Eventzilla endpoint, making data source setup easy and efficient. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.
List Events
Retrieves a paginated list of all events in your Eventzilla account, with optional filtering by event status. Use this endpoint to get an overview of your event catalog, monitor event status at scale, or drive downstream processing across multiple events.
Optionally, enter a value in the Status field to filter events by their current status. Accepted values include live, draft, cancelled, and past. Leave this field blank to retrieve events in all statuses.
This endpoint uses offset-based pagination and automatically fetches all pages of results. Each page returns up to 20 events by default.
Event IDs returned by this endpoint are used as required parameters in other endpoints such as List Event Attendees, List Event Tickets, List Event Transactions, Get Event Details, and List Event Dates.
Get Event Details
Returns detailed information for a single event by its unique event ID. Use this endpoint when you need complete event metadata—including description, dates, venue, ticketing configuration, and status—for a specific event.
Enter the unique numeric identifier of the event in the Id field. Event IDs can be retrieved using the List Events endpoint.
The response includes all available event fields as a single JSON object.
To retrieve details for multiple events, use the List Events endpoint to obtain all event IDs, then run individual Get Event Details calls for each event as needed.
List Event Attendees
Returns a paginated list of all attendees registered for a specified event. Use this endpoint to retrieve registration details, contact information, and ticket assignments for all attendees of a given event.
Enter the unique numeric identifier of the event in the Event ID field. This field is required. Event IDs can be obtained using the List Events endpoint.
This endpoint uses offset-based pagination and automatically retrieves all pages of attendee records, with up to 20 attendees per page.
The response includes attendee fields such as:
First and last name
Email address
Ticket type and bar code
Attendance (check-in) status
Custom registration question responses
Associated transaction reference
To retrieve attendees for multiple events, run a separate List Event Attendees source for each event ID.
Get Attendee
Retrieves the full registration details for a single attendee by their attendee ID within a specific event. Use this endpoint when you need comprehensive information about a particular attendee, including all custom field responses and ticket details.
Enter the unique numeric identifier of the event in the Event ID field. This field is required.
Enter the unique numeric identifier of the attendee in the Attendee ID field. This field is required. Attendee IDs can be retrieved using the List Event Attendees endpoint.
The response is a single JSON object containing the complete attendee record.
Get Attendee Check-in Status
Returns a paginated list of attendees for a specific event along with their check-in (attendance) status. Use this endpoint to monitor real-time or post-event attendance, identify no-shows, or export attendance records for reporting purposes.
Enter the unique numeric identifier of the event in the Event Id field. This field is required.
Optionally, enter a value in the Attended Status field to filter results by attendance:
true — Return only attendees who checked in.
false — Return only attendees who did not check in.
Leave blank to return all attendees regardless of check-in status.
This endpoint uses page-based pagination starting from page 1 and retrieves up to 20 attendees per page.
Eventzilla supports on-site check-in via QR code scanning. The attendance status reflected in this endpoint is updated in real time as attendees are checked in.
List Event Tickets
Returns a paginated list of all ticket types configured for a specified event. Use this endpoint to retrieve ticket pricing, availability, and tier configuration for an event, which is useful for reporting, analytics, or downstream ticket management.
Enter the unique numeric identifier of the event in the Event ID field. This field is required. Event IDs can be obtained using the List Events endpoint.
This endpoint uses offset-based pagination and retrieves up to 20 tickets per page.
List Event Transactions
Returns a paginated list of all transactions (registrations/orders) for a specified event. Each transaction record includes payment details, ticket counts, buyer information, and transaction status. Use this endpoint for financial reporting, reconciliation, or monitoring registration activity.
Enter the unique numeric identifier of the event in the Event ID field. This field is required.
This endpoint uses offset-based pagination and retrieves up to 20 transactions per page.
Transaction records include fields such as:
transaction_ref: Order reference number
checkout_id: Unique checkout identifier
transaction_date: Date and time of the transaction
transaction_amount: Total amount charged
transaction_status: One of Confirmed, Pending, Cancelled, or Incomplete
tickets_in_transaction: Number of tickets included in the order
To retrieve all transactions across all events, first run the List Events endpoint to obtain event IDs, then configure a separate List Event Transactions source for each event.
Get Transaction
Returns detailed information for a single transaction using either a checkout ID or an order reference number. Use this endpoint when you need complete details for a specific order, such as for customer support, auditing, or payment reconciliation.
Enter either the checkout ID or the order reference number in the Transaction ID or Reference Number field. This field is required. Both identifiers resolve to the same transaction record in Eventzilla.
The response is a single JSON object with the complete transaction record, including buyer details, ticket breakdown, payment status, and event association.
List Users
Retrieves a list of all users associated with your Eventzilla account. Use this endpoint to audit account membership, synchronize user data with external systems, or review collaborators and organizers on your account.
No additional parameters are required. This endpoint retrieves all users in a single, non-paginated response.
Get User
Retrieves the profile and account details for a single user by their user ID. Use this endpoint when you need complete information about a specific organizer or account collaborator.
Enter the unique numeric identifier of the user in the User ID field. This field is required. User IDs can be obtained from the List Users endpoint.
The response is a single JSON object containing the user's profile data.
List Event Dates
Lists all date/occurrence IDs for a multi-session or recurring event. Use this endpoint when working with events that have multiple scheduled dates, as each occurrence has a unique date ID required by the Prepare Checkout endpoint.
Enter the unique numeric identifier of the event in the Event ID field. This field is required.
The response returns an array of date objects, each containing the date ID and associated scheduling details.
Date IDs returned by this endpoint are required when using the Prepare Checkout endpoint for multi-session events, as each session must be addressed individually.
Prepare Checkout
Returns the payment options, available ticket types, and registration questions needed to prepare a checkout session for a specific event date. Use this endpoint to retrieve the complete checkout configuration before initiating a registration workflow.
Optionally, enter the unique identifier of the event in the Event Id field.
Optionally, enter the unique identifier of the specific event date/occurrence in the Date Id field. Date IDs can be obtained using the List Event Dates endpoint. For single-date events, only one date ID will be available.
The response includes available ticket types with pricing, registration form questions, and supported payment methods for the specified event date.
The data returned by this endpoint is typically used as the input to a Create Checkout destination to programmatically register attendees for an event.
List Categories
Returns a list of all event categories available in Eventzilla. Use this endpoint to retrieve category names and IDs for use in event filtering, reporting, or synchronization with external classification systems.
No additional parameters are required. This endpoint retrieves all categories using offset-based pagination with up to 20 categories per page.
Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Eventzilla data sources can also be manually configured to ingest data from any valid Eventzilla API v2 endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
All Eventzilla API v2 endpoints use the base URL https://www.eventzillaapi.net/api/v2/ and the GET method—for example, https://www.eventzillaapi.net/api/v2/events to list all events, or https://www.eventzillaapi.net/api/v2/events/{'{event_id}'}/attendees to list attendees for a specific event. Replace path parameters such as {'{event_id}'} with the actual numeric ID when entering the URL manually; the API does not support unencrypted HTTP connections.
Most responses wrap records in a named array, so set the path to data accordingly—for example, $.events[*] for List Events, $.attendees[*] for List Event Attendees and Get Attendee Check-in Status, $.tickets[*] for List Event Tickets, $.transactions[*] for List Event Transactions, $.categories[*] for List Categories, $.dates[*] for List Event Dates, or $ for single-object responses such as Get Event Details, Get Attendee, Get Transaction, Get User, and Prepare Checkout. If a response includes top-level metadata (such as a total_records field) outside this path, enter its location in the Path to Metadata in Response field.
You do not need to include the x-api-key authentication header here—this is handled automatically by Nexla based on the Eventzilla credential configured for this flow.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Eventzilla data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.
Click the + icon on the Nexset that will be sent to the Eventzilla destination, and select the Send to Destination option from the menu. Select the Eventzilla connector from the list of available destination connectors, then select the credential that will be used to connect to the Eventzilla account, and click Next; or, create a new Eventzilla credential for use in this flow.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Eventzilla endpoints. Each template is designed specifically for the corresponding Eventzilla endpoint, making destination configuration easy and efficient. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Create Checkout
Creates a new checkout session for an event, reserving selected ticket types. Use this endpoint to programmatically initiate registrations on behalf of attendees — for example, as part of an automated event registration workflow that integrates with an external CRM or ticketing system.
Prepare the Nexset data to include the required checkout fields as defined by the Eventzilla Checkout API. The payload should specify the event ID, selected ticket types, and quantities.
A successful response returns a checkout session ID that should be passed to the Fill Order endpoint to complete the registration by providing buyer and attendee details.
The Create Checkout endpoint reserves tickets but does not complete the registration. Use the Fill Order endpoint as the next step to submit buyer and attendee information and finalize the order.
Fill Order
Completes a checkout order by submitting buyer information and attendee details to process the registration. This is the second step in the two-step checkout flow — use this endpoint after a Create Checkout session has been initiated to finalize event registration.
Prepare the Nexset data to include the required order fields. At minimum, the payload should contain:
The checkout session ID returned by the Create Checkout endpoint
Buyer contact details (name and email address)
Attendee details for each ticket, including any responses to custom registration questions configured for the event
A successful response confirms that the registration has been processed and the transaction has been created in Eventzilla.
For complete information about the required payload structure for buyer and attendee fields, refer to the Eventzilla Developer documentation.
Create Event
Creates a new event in your Eventzilla account. Use this endpoint to programmatically create events from structured data — for example, when generating events in bulk from a spreadsheet or upstream system, or automating event creation as part of a larger data workflow.
Prepare the Nexset data to include all required event fields, such as event title, start and end date/time, timezone, and event type. Optional fields such as description, venue information, and category can also be included.
Updates the details of an existing event, such as its title, dates, description, or status. Use this endpoint when you need to propagate changes to event information from an upstream system into Eventzilla, or to automate event lifecycle management (for example, cancelling events based on external criteria).
Enter the unique numeric identifier of the event to be updated in the Event ID field. This field is required. Event IDs can be retrieved using the List Events data source endpoint.
Prepare the Nexset data to include the event fields that should be updated. Only the fields included in the payload will be modified; all other event fields will remain unchanged.
The request payload is sent as JSON to the event-specific URL using the HTTP PUT method.
Updating an event's status to cancelled will make it inaccessible to new registrations. Confirm the intended change before activating this destination.
Delete Event
Cancels or deletes an existing event from your Eventzilla account. Use this endpoint to remove events programmatically — for example, as part of an automated cleanup workflow or when synchronizing event data with an external system that has removed the event.
Enter the unique numeric identifier of the event to be deleted in the Event ID field. This field is required.
The delete operation is sent as an HTTP DELETE request to the event-specific URL. No request body is required.
Important
Deleting an event is a destructive action and cannot be undone. All associated registrations, attendee data, and transactions for that event will also be affected. Confirm the correct Event ID before activating this destination.
Check In Attendee
Marks an attendee as checked in (attended) for a specific event occurrence. Use this endpoint to programmatically record attendance — for example, when integrating Eventzilla with an external check-in system, badge scanner, or access control solution.
Enter the unique numeric identifier of the event in the Event ID field. This field is required.
Enter the unique numeric identifier of the attendee to be checked in in the Attendee ID field. This field is required. Attendee IDs can be retrieved using the List Event Attendees data source endpoint.
The check-in request is sent as an HTTP PUT to the attendee-specific check-in URL. No request body is required.
Eventzilla's check-in status is updated in real time. Once an attendee is marked as checked in via this endpoint, the change will be reflected immediately in the Eventzilla dashboard and in Get Attendee Check-in Status source queries.
Update Transaction
Updates or modifies an existing transaction — for example, to mark it as confirmed or adjust its status. Use this endpoint when you need to synchronize transaction state between Eventzilla and an external payment processor, order management system, or financial platform.
Enter the unique numeric identifier of the transaction to be updated in the Transaction ID field. This field is required. Transaction IDs can be retrieved using the List Event Transactions or Get Transaction data source endpoints.
Prepare the Nexset data to include the transaction fields that should be updated.
The request payload is sent as JSON to the transaction-specific URL using the HTTP PUT method.
Delete Transaction
Cancels or refunds a transaction (registration) in Eventzilla. Use this endpoint to programmatically process registration cancellations or refunds — for example, when integrating with a customer service platform or automating refund workflows based on external triggers.
Enter the unique numeric identifier of the transaction to be cancelled or refunded in the Transaction ID field. This field is required. Transaction IDs can be retrieved using the List Event Transactions or Get Transaction data source endpoints.
The delete/refund request is sent as an HTTP DELETE to the transaction-specific URL.
Important
Cancelling or refunding a transaction affects the attendee's registration and may trigger automated confirmation or refund emails to the buyer, depending on your Eventzilla account settings. Confirm the correct Transaction ID before activating this destination.
Eventzilla destinations can also be manually configured to send data to any valid Eventzilla API v2 endpoint, including configuring Nexla to automatically send the API response after each call to a new Nexla webhook data source. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
All Eventzilla API v2 endpoints use the base URL https://www.eventzillaapi.net/api/v2/ and accept JSON as the request body format. Use POST to create resources (events, checkout sessions, orders), PUT to update existing resources (events, transactions, attendee check-in), and DELETE to cancel or remove resources (events, transactions). For update and delete operations, include the resource ID at the end of the URL—for example, https://www.eventzillaapi.net/api/v2/events/{'{event_id}'} to update or delete an event, or https://www.eventzillaapi.net/api/v2/events/{'{event_id}'}/attendees/{'{attendee_id}'}/checkin to check in an attendee.
You do not need to include the x-api-key authentication header here—this is handled automatically by Nexla based on the Eventzilla credential configured for this flow.
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Eventzilla endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to Eventzilla until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.
