Skip to main content

Eventzilla Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow data flow that sends data to an Eventzilla destination.
eventzilla_api.png

Eventzilla

Create an Eventzilla Destination​

  1. Click the + icon on the Nexset that will be sent to the Eventzilla destination, and select the Send to Destination option from the menu.

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

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

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

Configure Using a Template​

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 setup easy and efficient.

  • To configure this destination using a template, 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.
  • No additional URL parameters are required for this endpoint. The request body is sent as a JSON payload to https://www.eventzillaapi.net/api/v2/checkout/create.
  • 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
  • The request payload is sent as JSON to https://www.eventzillaapi.net/api/v2/checkout/fillorder.
  • 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.
  • The request payload is sent as JSON to https://www.eventzillaapi.net/api/v2/events using the HTTP POST method.
  • A successful response returns the newly created event object, including the event ID assigned by Eventzilla.

For the full list of required and optional event creation fields, refer to the Eventzilla Developer documentation.

Update Event

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.

Configure Manually​

Eventzilla destinations can be manually configured to send data to any valid Eventzilla API v2 endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Eventzilla API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, 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. Common methods for Eventzilla write operations are:

    • POST: For creating new resources (events, checkout sessions, orders)
    • PUT: For updating existing resources (events, transactions, attendee check-in)
    • DELETE: For cancelling or removing resources (events, transactions)

Data Format​

  1. Select the format in which the Nexset data will be sent to the Eventzilla API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The Eventzilla API v2 accepts JSON as the request body format for all write operations.

API Endpoint URL​

  1. Enter the URL of the Eventzilla API endpoint to which you want to send the Nexset data in the URL field. All Eventzilla API v2 endpoints use the base URL https://www.eventzillaapi.net/api/v2/. For update and delete operations, include the resource ID at the end of the URL. For example:
    • https://www.eventzillaapi.net/api/v2/events — Create a new event (POST)
    • https://www.eventzillaapi.net/api/v2/events/{event_id} — Update or delete an event (PUT/DELETE)
    • https://www.eventzillaapi.net/api/v2/checkout/create — Create a checkout session (POST)
    • https://www.eventzillaapi.net/api/v2/checkout/fillorder — Complete an order (POST)
    • https://www.eventzillaapi.net/api/v2/transactions/{transaction_id} — Update or delete a transaction (PUT/DELETE)
    • https://www.eventzillaapi.net/api/v2/events/{event_id}/attendees/{attendee_id}/checkin — Check in an attendee (PUT)

Replace path parameters such as {'{event_id}'} and {'{transaction_id}'} with the actual numeric identifiers when entering the URL manually. These IDs can be retrieved using the corresponding Eventzilla data source endpoints in Nexla.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, 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.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Eventzilla destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

Response Webhook​

Optional

Nexla can automatically send the response received from the Eventzilla API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call — for example, to capture newly created event IDs or confirm completed checkout sessions.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Eventzilla API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Eventzilla API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Eventzilla API using the current settings.

Save & Activate the Destination​

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