Skip to main content

Eventzilla Data Source

The Eventzilla connector enables you to ingest event, attendee, ticket, transaction, and user data from your Eventzilla account into Nexla. Follow the instructions below to create a new data flow that ingests data from an Eventzilla source in Nexla.
eventzilla_api.png

Eventzilla

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Eventzilla connector tile from the list of available 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.

  3. In Nexla, Eventzilla data sources can be created using pre-built endpoint templates, which expedite source setup for common Eventzilla API endpoints. Each template is designed specifically for the corresponding Eventzilla endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Eventzilla sources can also be configured manually, allowing you to ingest data from Eventzilla endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

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.

Endpoint Settings​

  • 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.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Eventzilla data sources can be manually configured to ingest data from any valid Eventzilla API v2 endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Eventzilla sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom request parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Eventzilla API from the Method pulldown menu. For retrieving data from Eventzilla, use:

    • GET: For retrieving events, attendees, tickets, transactions, users, and categories.

API Endpoint URL​

  1. Enter the URL of the Eventzilla API endpoint from which this source will fetch data in the Set API URL field. All Eventzilla API v2 endpoints use the base URL https://www.eventzillaapi.net/api/v2/. For example:
    • https://www.eventzillaapi.net/api/v2/events — List all events
    • https://www.eventzillaapi.net/api/v2/events/{event_id}/attendees — List attendees for a specific event
    • https://www.eventzillaapi.net/api/v2/categories — List all event categories

Replace path parameters such as {'{event_id}'} with the actual numeric event ID when entering the URL manually. Ensure the URL uses HTTPS, as the Eventzilla API does not support unencrypted HTTP connections.

Date/Time Macros (API URL)​

Optional

Optionally, the API URL can be customized using macros—all macros added to the API URL will be converted into values when Nexla executes the API call. Macros are dynamic placeholders that allow you to create flexible API endpoints that can adapt to different time periods or data requirements.

Date/time macros are particularly useful when querying Eventzilla endpoints that accept date-range parameters, allowing you to automate time-windowed data ingestion without manually updating the URL on each run.

  1. To add a macro, type { at the appropriate position in the API URL (within the Set API URL field), and select the desired macro from the dropdown list.

    • {now} – The current datetime
    • {now-1} – The datetime one time unit before the current datetime
    • {now+1} – The datetime one time unit after the current datetime
    • custom – Datetime macros can reference any number of time units before or after the current datetime—for example, enter (now-4) to indicate the datetime four time units before the current datetime

  2. Select the format that will be applied to datetime macros from the Date Format for Date/Time Macro pulldown menu. This format will be applied to the base datetime value of the macro—i.e., the value of {now} in {now-1}.

  3. Select the datetime unit that will be used to perform mathematical operations in the included macro(s) from the Time Unit for Operations pulldown menu—for example, for the macro {now-1}, when Day is selected, {now-1} will be converted to the datetime one day before the current datetime.

Lookup-Based Macros (API URL)​

Optional

Column values from existing lookups can also be included as macros in the API URL. Lookup-based macros allow you to reference data from previously configured data sources or lookups, enabling dynamic API endpoints that can adapt based on existing data.

Lookup-based macros are particularly useful for Eventzilla sources where you need to parameterize requests with event IDs, attendee IDs, or other identifiers retrieved from a prior Nexla data source.

  1. To include a lookup column value macro, select the relevant lookup from the Add Lookups to Supported Macros pulldown menu.

  2. Type { at the appropriate position in the API URL, and select the lookup column-based macro from the dropdown list. Lookup-based macros are automatically populated into the macro list when a lookup is selected in the Add Lookups to Supported Macros pulldown menu.

Path to Data​

Optional

If only a subset of the data returned by the Eventzilla API endpoint is needed, you can designate which part of the response should be included in the Nexsets produced from this source. Most Eventzilla API responses return records nested within a named array.

For example, the List Event Attendees endpoint returns a JSON response in which attendee records are nested inside an attendees array. By entering $.attendees[*] as the path to data, each attendee object is treated as a separate record in the resulting Nexset.

Path to Data is essential for most Eventzilla API responses, which wrap record arrays inside a named key (such as events, attendees, tickets, or transactions). Without specifying the correct path, Nexla will treat the entire response as a single record rather than extracting individual items.

  • To specify which data should be treated as relevant in responses from this source, enter the path to the relevant data in the Set Path to Data in Response field.

    • For responses in JSON format, enter the JSON path that points to the object or array that should be treated as relevant data. JSON paths use dot notation (e.g., $.attendees[*] to access the attendees array, or $.events[*] to access the events array).
    Common Eventzilla Path to Data values:
    • $.events[*] — For List Events responses
    • $.attendees[*] — For List Event Attendees and Get Attendee Check-in Status responses
    • $.tickets[*] — For List Event Tickets responses
    • $.transactions[*] — For List Event Transactions responses
    • $.categories[*] — For List Categories responses
    • $.dates[*] — For List Event Dates responses
    • $ — For single-object responses (Get Event Details, Get Attendee, Get Transaction, Get User, Prepare Checkout)
Autogenerate Path Suggestions​

Nexla can also autogenerate data path suggestions based on the response from the API endpoint. These suggested paths can be used as-is or modified to exactly suit your needs.

  • To use this feature, click the Test button next to the Set API URL field to fetch a sample response from the API endpoint. Suggested data paths generated based on the content & format of the response will be displayed in the Suggestions box below the Set Path to Data in Response field.

  • Click on a suggestion to automatically populate the Set Path to Data in Response field with the corresponding path. The populated path can be modified directly within the field if further customization is needed.

Metadata​

If metadata is included in the response but is located outside of the defined path to relevant data, you can configure Nexla to include this data as common metadata in each record. Eventzilla API responses often include top-level metadata such as total record counts alongside the data array.

For example, if the List Events response contains a top-level total_records field alongside the events array, and the path to data is set to $.events[*], you can specify a metadata path to include the total_records value with each event record for context.

Metadata paths are useful for preserving contextual information from Eventzilla API responses, such as total counts or pagination data, that applies to all records in the response.

  • To specify the location of metadata that should be included with each record, enter the path to the relevant metadata in the Path to Metadata in Response field.

    • For responses in JSON format, enter the JSON path to the object or array that contains the metadata.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this source, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    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.

Endpoint Testing​

After configuring all settings for the selected endpoint, Nexla can retrieve a sample of the data that will be fetched according to the current configuration. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Save & Activate the Source​

  1. Once all of the relevant steps in the above sections have been completed, 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.