Skip to main content

Eventbrite 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 Eventbrite location.
eventbrite_api.png

Eventbrite

Create an Eventbrite Destination​

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

  2. Select the Eventbrite connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Eventbrite organization, and click Next; or, create a new Eventbrite credential for use in this flow.

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

    Eventbrite destinations can also be configured manually, allowing you to send data to Eventbrite 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 Eventbrite endpoints. Each template is designed specifically for the corresponding Eventbrite 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.

    Update an Existing Event

    Updates the details of an existing Eventbrite event, including its name, description, start and end times, and capacity. Use this endpoint to programmatically apply changes to event records—for example, updating event descriptions from a content management system, adjusting capacity based on venue constraints, or propagating changes across related events in bulk.

    • Enter the unique identifier of the event you want to update in the Event ID field.

      • Event IDs can be obtained from the Eventbrite data source using the List Organization Events or Retrieve a Single Event by ID endpoints, or from the event URL in the Eventbrite dashboard.
    • The request body is sent as a JSON object. Include only the fields you want to update—omitted fields retain their current values. Refer to the Eventbrite Platform API documentation for the full list of updatable event fields and their expected formats.

    Only existing (previously created) events can be updated with this endpoint. To publish a draft event so it becomes publicly visible, use the Publish a Draft Event endpoint after updating.

    Create a Discount Code on an Event

    Creates a new discount code for the specified Eventbrite event. Discount codes allow organizers to offer reduced-price tickets to specific attendees. Use this endpoint to automate discount code generation—for example, creating loyalty codes for returning attendees, promotional codes for marketing campaigns, or bulk codes for corporate clients.

    • Enter the unique identifier of the event to which the discount code will be added in the Event Id field.

      • Event IDs can be obtained from the List Organization Events data source endpoint or from the Eventbrite event management dashboard.

    • The request body must be a JSON object containing the discount code details. Required fields include:

      • code: The discount code string that attendees will enter at checkout (e.g., SUMMER20).
      • type: The discount type — either coded for a standard promo code or access for an access code that unlocks hidden ticket types.
      • percent_off or amount_off: The discount value, expressed as a percentage (e.g., 20 for 20% off) or a fixed currency amount.
    • Additional optional fields such as ticket_ids (to restrict the discount to specific ticket classes), quantity_available (to limit the number of uses), and start_date / end_date (to define a validity window) can also be included in the request body.

    Additional details about discount code fields and supported values are available in the Eventbrite Platform API reference.

    Publish a Draft Event

    Publishes a draft Eventbrite event, making it publicly visible on the Eventbrite marketplace and available for ticket sales. This is a core event lifecycle action used to move events from draft status to live. Use this endpoint to automate event publication workflows—for example, publishing events on a scheduled basis or after all content has been approved in an external system.

    • Enter the unique identifier of the draft event you want to publish in the Event ID field.

      • Event IDs can be obtained from the List Organization Events data source endpoint or from the Eventbrite event management dashboard. Only events in draft status can be published with this endpoint.
    • This endpoint sends a POST request with an empty body to the event's publish URL. No additional fields in the request body are required.

    :::warning Important Publishing an event is irreversible through this endpoint alone. Once published, an event is publicly visible and available for ticket sales. To take a live event offline without cancelling it, use the Unpublish a Live Event endpoint. :::

    Create a New Ticket Class for an Event

    Creates a new ticket class (ticket type) for an existing Eventbrite event. Ticket classes define the different tiers of tickets available for an event, such as General Admission, VIP, Early Bird, or Student pricing. Use this endpoint to programmatically add ticket types to events—for example, when creating events in bulk or when ticket tiers are managed in an external system.

    • Enter the unique identifier of the event to which the ticket class will be added in the Event Id field.

      • Event IDs can be obtained from the List Organization Events data source endpoint or from the Eventbrite event management dashboard.

    • The request body must be a JSON object containing the ticket class details. Required fields include:

      • name: The display name of the ticket class (e.g., General Admission or VIP).
      • free: Set to true for a free ticket class or false for a paid ticket class.
      • quantity_total: The total number of tickets available for this class.
      • cost: For paid ticket classes, the ticket price expressed as a currency object (e.g., "currency": "USD", "value": 2500 for $25.00). Omit this field for free ticket classes.
    • Additional optional fields such as sales_start, sales_end, minimum_quantity, and maximum_quantity can be included to further configure availability windows and purchase limits.

    Additional details about ticket class fields and supported values are available in the Eventbrite Platform API reference.

    Update an Existing Ticket Class

    Updates the configuration of an existing ticket class, including its price, capacity, availability window, and other settings. Use this endpoint to programmatically manage ticket inventory—for example, increasing capacity when a venue upgrades, adjusting prices for dynamic pricing strategies, or extending the sales window for a ticket tier.

    • Enter the unique identifier of the event in the Event Id field and the unique identifier of the ticket class to update in the Ticket Class Id field.

      • Event IDs can be obtained from the List Organization Events data source endpoint.
      • Ticket Class IDs can be obtained from the List Ticket Classes data source endpoint. The ID appears as the numeric id field in each ticket class record.
    • The request body is sent as a JSON object. Include only the fields you want to update. Refer to the Eventbrite Platform API reference for the full list of updatable ticket class fields.

    Create a Custom Registration Question for an Event

    Adds a new custom registration question to an existing Eventbrite event's checkout form. Custom questions enable organizers to collect attendee-specific information beyond standard fields, such as dietary preferences, t-shirt sizes, company names, or session preferences. Use this endpoint to programmatically configure registration forms—for example, when creating events in bulk from a template system.

    • Enter the unique identifier of the event to which the question will be added in the Event Id field.

      • Event IDs can be obtained from the List Organization Events data source endpoint or from the Eventbrite event management dashboard.

    • The request body must be a JSON object containing the question details. Key fields include:

      • type: The question input type (e.g., text, dropdown, checkbox, radio).
      • required: Set to true if attendees must answer this question to complete registration, or false to make it optional.
      • label: The question text displayed to attendees at checkout.
      • choices: For dropdown, checkbox, or radio question types, an array of answer options.

    Additional details about question configuration fields are available in the Eventbrite Platform API overview.

    Cancel a Published Event

    Cancels a published Eventbrite event, triggering Eventbrite's standard cancellation workflow including notifying registered attendees. Cancelling an event is a core event lifecycle management action. Use this endpoint to automate cancellation workflows—for example, when a venue becomes unavailable or when programmatic event management systems need to cancel events based on external triggers.

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

      • Event IDs can be obtained from the List Organization Events data source endpoint or from the Eventbrite event management dashboard. Only published events can be cancelled with this endpoint.
    • This endpoint sends a POST request with no required request body. Eventbrite will handle attendee notifications and refund eligibility according to the event's configured refund policy.

    :::warning Important Cancelling an event notifies all registered attendees and may trigger refund processing. This action cannot be easily undone. Verify that the correct Event ID is specified before sending data to this endpoint. :::

    Unpublish a Live Event

    Takes a live (published) Eventbrite event offline without cancelling it. The event returns to draft status and is no longer visible on the Eventbrite marketplace or available for ticket sales. Use this endpoint when you need to temporarily hide an event for editing or when an event needs to be taken offline without triggering the full cancellation workflow.

    • Enter the unique identifier of the live event you want to unpublish in the Event Id field.

      • Event IDs can be obtained from the List Organization Events data source endpoint or from the Eventbrite event management dashboard. Only currently published (live) events can be unpublished.
    • This endpoint sends a POST request with no required request body.

    Unpublishing an event does not cancel existing ticket orders or notify attendees. Attendees who have already purchased tickets retain their orders. To re-publish the event, use the Publish a Draft Event endpoint.

    Create an Organizer Profile Under an Organization

    Creates a new organizer profile associated with the specified Eventbrite organization. An organizer profile is the public-facing identity displayed on the Eventbrite marketplace when an event is listed (name, biography, logo, website link). Use this endpoint to programmatically set up organizer branding—for example, when onboarding new departments or brands within a large organization.

    • Enter the unique identifier of the organization under which the organizer profile will be created in the Organization Id field.

      • Organization IDs can be obtained using the List User Organizations data source endpoint.

    • The request body must be a JSON object containing the organizer profile details. Key fields include:

      • name: The public display name of the organizer.
      • description: A text description or biography displayed on the organizer's public profile page.
      • website: The organizer's website URL (optional).
      • logo_id: The ID of an uploaded image to use as the organizer's logo (optional).

    Register a New Webhook Endpoint

    Registers a new webhook endpoint with Eventbrite to receive real-time event notifications. Eventbrite can send POST requests to a specified URL whenever defined actions occur—such as when an attendee checks in (attendee.checked_in), a ticket order is placed (order.placed), or an event is published (event.published). Use this endpoint to set up real-time data pipelines that react to Eventbrite activity without polling the API.

    • The request body must be a JSON object containing the webhook registration details. Key fields include:

      • endpoint_url: The URL to which Eventbrite will send POST requests when the subscribed actions occur. This must be a publicly accessible HTTPS URL.
      • actions: A comma-separated string of event action types to subscribe to (e.g., order.placed,attendee.checked_in,event.published). Refer to the Eventbrite Platform API overview for a complete list of supported webhook actions.
      • organization_id: The ID of the organization for which this webhook will be active.
    • To review webhooks already registered for an organization, use the List Active Webhooks for an Organization data source endpoint.

    Webhook endpoints must be publicly accessible over HTTPS. Eventbrite will not deliver notifications to endpoints that are not reachable from the internet or that fail to return a 2xx HTTP status code. Test your endpoint URL before registering it.

    Delete a Ticket Class from an Event

    Deletes a ticket class from an Eventbrite event. This operation removes the ticket type permanently from the event's configuration. Use this endpoint to clean up ticket configurations—for example, removing ticket tiers that were created in error or that are no longer needed before an event goes live.

    • Enter the unique identifier of the event in the Event Id field and the unique identifier of the ticket class to delete in the Ticket Class Id field.

      • Event IDs can be obtained from the List Organization Events data source endpoint.
      • Ticket Class IDs can be obtained from the List Ticket Classes data source endpoint.

    :::warning Important Deleting a ticket class is a permanent action. If attendees have already purchased tickets in the class being deleted, this operation may fail or cause data inconsistencies. Verify ticket class inventory before deleting. Consider using the Update an Existing Ticket Class endpoint to set quantity_total to zero as a safer alternative to deletion. :::

Configure Manually​

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

Using manual configuration, you can also configure Nexla to automatically send the response received from the Eventbrite 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 Eventbrite API from the Method pulldown menu. Common methods used for Eventbrite write operations include:

    • POST: For creating new resources or triggering actions (most common for Eventbrite write operations)
    • DELETE: For removing resources such as ticket classes

Eventbrite's API uses POST for both create and update operations. Update endpoints (e.g., updating an event or ticket class) use POST, not PUT or PATCH. Always refer to the Eventbrite Platform API documentation to confirm the correct method for each endpoint.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Eventbrite API from the Content Format pulldown menu. Eventbrite's API accepts data in JSON format (application/json). Nexla will automatically convert the data to the selected format for each API call.

API Endpoint URL​

  1. Enter the URL of the Eventbrite API endpoint to which you want to send the Nexset data in the URL field. All Eventbrite API v3 endpoints follow the base URL format https://www.eventbriteapi.com/v3/. For update or action operations, include the relevant ID(s) in the URL path. For example:

    • https://www.eventbriteapi.com/v3/events/{'{event_id}'}/ — Update an existing event
    • https://www.eventbriteapi.com/v3/events/{'{event_id}'}/publish/ — Publish a draft event
    • https://www.eventbriteapi.com/v3/events/{'{event_id}'}/ticket_classes/ — Create a ticket class
    • https://www.eventbriteapi.com/v3/organizations/{'{organization_id}'}/organizers/ — Create an organizer profile
    • https://www.eventbriteapi.com/v3/webhooks/ — Register a new webhook

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 Authorization header in this field—Nexla automatically includes it using the API key from the configured Eventbrite credential. The Content-Type: application/json header is also handled automatically when JSON is selected as the data format.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this Eventbrite 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 Eventbrite 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.

  • 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 Eventbrite 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 Eventbrite 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 Eventbrite 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 Eventbrite endpoint, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to the Eventbrite endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.