Eventbrite Data Source

The Eventbrite connector enables you to ingest event, attendee, order, ticket, and organizational data from your Eventbrite account into Nexla data flows. Follow the instructions below to create a new data flow that ingests data from an Eventbrite source in Nexla.

Eventbrite

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 Eventbrite connector tile from the list of available connectors. Then, select the credential that will be used to connect to the Eventbrite account, and click Next; or, create a new Eventbrite credential for use in this flow.

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

   Eventbrite sources can also be configured manually, allowing you to ingest data from Eventbrite 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 Eventbrite endpoints. Each template is designed specifically for the corresponding Eventbrite API 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 User Organizations

Returns a list of all Eventbrite organizations associated with the authenticated user account. Use this endpoint to discover which organization IDs are available before querying events, orders, members, or venues that belong to a specific organization.

• This endpoint requires no additional parameters. Once selected, Nexla will automatically retrieve all organizations linked to the API key in your credential.
• The response is paginated. Nexla handles pagination automatically, fetching up to 50 records per page and continuing until all organizations have been retrieved.

The organization IDs returned by this endpoint are required as input parameters for several other Eventbrite endpoints, such as List Organization Events, List Organization Orders, List Organization Members, and List Venues. Run this endpoint first if you do not already know your organization IDs.

List Organization Events

Returns a paginated list of all events belonging to the specified organization. This endpoint is useful for building event catalogs, monitoring event status, synchronizing event data to CRMs or data warehouses, and populating dashboards that track event performance across your organization.

• Enter the unique identifier of the organization whose events you want to retrieve in the Organization ID field.

  • To find your Organization ID, use the List User Organizations endpoint. The ID is the numeric identifier returned in each organization record (e.g., 12345678).
• Nexla retrieves events in pages of up to 50 records and continues fetching additional pages automatically until all events for the organization have been ingested.

This endpoint returns all events for the organization regardless of status (draft, live, completed, cancelled). Filter or transform the resulting Nexset as needed to isolate events in a particular status.

List Event Attendees

Returns a paginated list of all attendees registered for the specified event, including profile information, order details, ticket class, check-in status, and custom question responses. This endpoint is commonly used to build attendee rosters, populate CRM contact records, analyze registration trends, and drive post-event communications.

• Enter the unique identifier of the event whose attendees you want to retrieve in the Event ID field.

  • Event IDs can be obtained from the List Organization Events endpoint. The ID appears as the numeric id field in each event record.
  • The Event ID is also visible in the Eventbrite event management UI: navigate to Manage Events, open the event, and look for the numeric ID in the page URL (e.g., eventbrite.com/myevent-123456789).
• Nexla fetches attendee records in pages of up to 50 and continues automatically until all attendees for the event have been retrieved.

Attendee records include answers to custom registration questions configured for the event. To retrieve the list of questions associated with an event, use the List Event Custom Questions or List Event Canned Questions endpoints.

List Event Categories

Returns a complete list of all standard event categories available on the Eventbrite platform (e.g., Music, Business, Food & Drink, Sports & Fitness). Use this endpoint to enrich event records with human-readable category names, build category-based filters, or populate lookup tables in your data warehouse.

• This endpoint requires no additional parameters. Nexla retrieves the full global list of Eventbrite categories automatically.
• The returned category IDs can be cross-referenced with the category_id field present in event records from the List Organization Events endpoint.

List Event Formats

Returns a complete list of all standard event formats available on the Eventbrite platform (e.g., Conference, Seminar, Class, Concert, Festival). Use this endpoint to enrich event records with format labels or build format-based reporting dimensions.

• This endpoint requires no additional parameters. Nexla retrieves the complete global list of Eventbrite formats automatically.
• Format IDs returned here correspond to the format_id field in event records from the List Organization Events endpoint.

List Organization Orders

Returns a paginated list of all ticket orders placed within the specified organization. Each order record includes purchaser details, ticket quantities, payment status, and associated event information. Use this endpoint for revenue reporting, refund tracking, and financial reconciliation workflows.

• Enter the unique identifier of the organization whose orders you want to retrieve in the Organization ID field.

  • To find your Organization ID, use the List User Organizations endpoint.
• Nexla fetches orders in pages of up to 50 records and continues automatically until all orders for the organization have been retrieved.

For detailed order-level information including refund status and per-order attendee cross-references, use the Retrieve a Single Order by ID endpoint in addition to this list endpoint.

List Organization Members

Returns a paginated list of all members belonging to the specified Eventbrite organization. Use this endpoint to audit team access, synchronize team rosters with HR systems, or build access-control reports.

• Enter the unique identifier of the organization whose members you want to retrieve in the Organization ID field.

  • To find your Organization ID, use the List User Organizations endpoint.
• Nexla fetches member records in pages of up to 50 and continues automatically until all members have been retrieved.

List Organization Roles

Returns the list of roles available within the specified Eventbrite organization. Roles define the permissions that can be assigned to organization members. Use this endpoint to enumerate available roles for access management or compliance reporting.

• Enter the unique identifier of the organization whose roles you want to retrieve in the Organization ID field.

  • To find your Organization ID, use the List User Organizations endpoint.
• This endpoint returns a static (non-paginated) list of roles—all roles are returned in a single response.

List Event Canned Questions

Returns the set of default (canned) registration questions configured for the specified event. Canned questions are Eventbrite's built-in registration form fields (e.g., "First Name", "Last Name", "Email"). Use this endpoint to audit event registration forms or build question-answer mapping tables.

• Enter the unique identifier of the event in the Event ID field.

  • Event IDs can be obtained from the List Organization Events endpoint or from the event URL in the Eventbrite dashboard.
• This endpoint returns a static list—all canned questions for the event are returned in a single response without pagination.

List Event Custom Questions

Returns a paginated list of all custom registration questions that have been added to the specified event's registration form. Custom questions are organizer-defined fields used to collect additional attendee information at checkout. Use this endpoint to document event forms, cross-reference custom question IDs with attendee answer data, or replicate question schemas across events.

• Enter the unique identifier of the event in the Event ID field.

  • Event IDs can be obtained from the List Organization Events endpoint or from the Eventbrite event management dashboard.
• Nexla fetches custom questions in pages of up to 50 and continues automatically until all questions have been retrieved.

Get Ticket Buyer Settings

Retrieves the ticket buyer settings configuration for a specific event, including checkout policies, buyer-facing terms, confirmation settings, and other purchase-experience options. Use this endpoint to audit or replicate ticket buyer configuration across events.

• Enter the unique identifier of the event whose ticket buyer settings you want to retrieve in the Event ID field.

  • Event IDs can be obtained from the List Organization Events endpoint or from the event URL in the Eventbrite dashboard.
• This endpoint returns a single record (not paginated)—all ticket buyer settings for the specified event are returned in one response.

List Ticket Classes

Returns all ticket classes (ticket types) defined for the specified event, including both on-sale and off-sale tickets. Each ticket class record includes pricing, capacity, availability window, quantity sold, and quantity remaining. Use this endpoint to track inventory, analyze revenue mix across ticket tiers, and audit ticket configuration.

• Enter the unique identifier of the event whose ticket classes you want to retrieve in the Event ID field.

  • Event IDs can be obtained from the List Organization Events endpoint or from the Eventbrite event management dashboard.
• Nexla fetches ticket class records in pages of up to 50 and continues automatically until all ticket classes have been retrieved.

To retrieve only ticket classes that are currently available for purchase, use the List Available Ticket Classes endpoint instead.

List Available Ticket Classes

Returns all ticket classes that are currently available for sale for the specified event. This endpoint filters out hidden, expired, or sold-out ticket types, returning only those that a buyer could currently purchase. Use this endpoint to power real-time inventory dashboards or consumer-facing ticket availability displays.

• Enter the unique identifier of the event in the Event ID field.

  • Event IDs can be obtained from the List Organization Events endpoint or from the Eventbrite event management dashboard.
• Nexla fetches available ticket classes in pages of up to 50 and continues automatically until all results have been retrieved.

List Venues

Returns all venue records associated with the specified organization, including venue name, address, capacity, and geographic coordinates. Use this endpoint to build venue directories, enrich event records with location data, or power location-based analytics.

• Enter the unique identifier of the organization whose venues you want to retrieve in the Organization ID field.

  • To find your Organization ID, use the List User Organizations endpoint.
• Nexla fetches venue records in pages of up to 50 and continues automatically until all venues have been retrieved.

Retrieve a Single Event by ID

Retrieves the full detail record for a single Eventbrite event identified by its unique Event ID. This is the most fundamental event read operation and is ideal for point-in-time snapshots, record enrichment, and event-level detail lookup. The response includes all event fields: name, description, start/end times, status, capacity, venue, organizer, ticket classes, and more.

• Enter the unique identifier of the event in the Event Id field.

  • Event IDs can be obtained from the List Organization Events endpoint or from the event URL in the Eventbrite dashboard (e.g., eventbrite.com/myevent-123456789).
• This endpoint returns a single record—the complete JSON representation of the specified event—without pagination.

Retrieve a Single Order by ID

Retrieves the full detail record for a single ticket order identified by its unique Order ID. The response includes buyer information, line items, payment status, refund status, and cross-references to associated attendees and events. Use this endpoint for order-level lookup, refund reconciliation, and attendee cross-referencing.

• Enter the unique identifier of the order in the Order Id field.

  • Order IDs can be obtained from the List Organization Orders endpoint. The ID appears as the numeric id field in each order record.
• This endpoint returns a single record—the complete JSON representation of the specified order—without pagination.

List Organizer Profiles for an Organization

Returns all organizer profiles associated with the specified organization. Organizer profiles represent the public-facing identity used when listing events on the Eventbrite marketplace (name, biography, logo, social links). Use this endpoint to audit organizer branding or synchronize profile data to external systems.

• Enter the unique identifier of the organization in the Organization Id field.

  • To find your Organization ID, use the List User Organizations endpoint.
• Nexla fetches organizer profiles in pages of up to 50 and continues automatically until all profiles have been retrieved.

List Active Webhooks for an Organization

Returns all active webhook endpoints registered for the specified organization. Each record includes the webhook URL, the event actions it subscribes to (e.g., attendee.checked_in, order.placed, event.published), and status information. Use this endpoint to audit webhook registrations or monitor real-time notification configurations.

• Enter the unique identifier of the organization in the Organization Id field.

  • To find your Organization ID, use the List User Organizations endpoint.
• Nexla fetches webhook records in pages of up to 50 and continues automatically until all registered webhooks have been retrieved.

To register a new webhook endpoint, use the Register a New Webhook Endpoint destination endpoint. Webhooks allow you to receive real-time event notifications from Eventbrite without polling the API.

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

Eventbrite data sources can be manually configured to ingest data from any valid Eventbrite API 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 Eventbrite 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 Eventbrite API from the Method pulldown menu. The Eventbrite REST API uses the following methods:

   • GET: For retrieving data from the API (the most common method for data source use cases)
   • POST: For sending data to the API or triggering actions (less common for data source flows)

API Endpoint URL

3. Enter the URL of the Eventbrite API endpoint from which this source will fetch data in the Set API URL field. All Eventbrite API v3 endpoints follow the base URL format https://www.eventbriteapi.com/v3/. For example:

   • https://www.eventbriteapi.com/v3/users/me/organizations/ — List organizations for the authenticated user
   • https://www.eventbriteapi.com/v3/organizations/{'{organization_id}'}/events/ — List events for a specific organization
   • https://www.eventbriteapi.com/v3/events/{'{event_id}'}/attendees/ — List attendees for a specific event

The Eventbrite API Reference is available at the Eventbrite Platform API documentation. Use it to explore all available endpoints and their supported query parameters.

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 filtering Eventbrite endpoints by date ranges—for example, fetching only events or orders created after a specific date.

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 Eventbrite endpoints that require IDs—for example, dynamically substituting organization IDs or event IDs sourced from a previous Nexla data source into the API URL.

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 that will be returned by the API endpoint is needed, you can designate the part(s) of the response that should be included in the Nexset(s) produced from this source by specifying the path to the relevant data within the response.

The Eventbrite API returns JSON responses that typically wrap arrays of records inside a named key. For example, a request to the events endpoint returns a JSON object with an events array containing the event records, along with a pagination object. By specifying the path to the events array, Nexla treats each element of that array as an individual record.

Path to Data is essential when ingesting list responses from Eventbrite. Without specifying the correct path, Nexla may treat the entire response object (including pagination metadata) as a single record rather than parsing individual records from the list.

• 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. Common Eventbrite JSON paths include:

    • $.events[*] — for event list responses
    • $.attendees[*] — for attendee list responses
    • $.orders[*] — for order list responses
    • $.organizations[*] — for organization list responses
    • $.ticket_classes[*] — for ticket class list responses
    • $ — for single-record responses (e.g., Retrieve a Single Event by ID)
  Path to Data Example:

  If the API response is the Eventbrite attendee list endpoint, the response contains a top-level array named attendees. Enter $.attendees[*] as the Path to Data to instruct Nexla to treat each element of that array as a separate attendee record.

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.

Eventbrite list responses include a pagination object at the top level alongside the data array. This pagination object contains fields like object_count, page_count, page_size, and continuation (the pagination cursor). You can capture this context as metadata by specifying its path in the Path to Metadata in Response field.

Including Eventbrite pagination metadata with each record is useful when you want to preserve context about the total result set size alongside individual records—for example, recording how many total attendees an event had as part of each attendee record.

• 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 that contains the metadata. For Eventbrite responses, the pagination metadata is located at $.pagination.

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 Authorization header in this field—Nexla automatically includes it using the API key from the configured Eventbrite credential. Only add headers that are not already handled by the credential configuration.

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