Eventbrite is a global self-service ticketing and event platform for creating, promoting, and managing events of any size. Organizers build event pages, define multiple ticket types, manage registrations, process payments, and access real-time analytics, while its marketplace exposes events to millions of attendees. The connector ingests event, attendee, order, and ticketing data for analytics and CRM.
Power end-to-end data operations for your Eventbrite API with Nexla. Our bi-directional Eventbrite connector is purpose-built for Eventbrite, 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 Eventbrite or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Eventbrite 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 Eventbrite, you need an active Eventbrite account and an API key generated from the Eventbrite Developer Portal. Eventbrite authenticates API requests using a Bearer token—your API key is passed in the Authorization request header as Bearer <your_api_key> on every call.
Eventbrite issues API keys through the Developer Links section of your Account Settings. Each key is tied to an application record that you create in the portal.
Click your profile icon in the top-right corner, then select Account Settings from the dropdown menu.
In the left-hand navigation, scroll to the Developer Links section and click API Keys.
Click Create API Key (or Get a Key if you have not created one before).
Fill in the required application details:
Application Name: Enter a descriptive name for the integration (e.g., "Nexla Integration").
Application URL: Enter the URL of the application or system that will use the key (e.g., your organization's Nexla instance URL or your company website).
OAuth Redirect URI: Enter the redirect URI that Eventbrite will use after an OAuth authorization flow. For a server-side integration with Nexla, you can enter your Nexla instance URL.
Description (optional): Enter a brief description of how the key will be used.
Accept Eventbrite's API Terms of Service, then submit the form.
Eventbrite will send a confirmation email when your API key is approved. Once approved, return to Account Settings > Developer Links > API Keys to find your API Key (also referred to as your Private Token or OAuth Token).
Copy the API key value and store it securely—it will be required when creating the credential in Nexla.
Treat your Eventbrite API key like a password. Anyone who has access to it can make API calls on behalf of your Eventbrite account. Store it in a secrets manager or secure vault and avoid sharing it in plain text.
Important
Eventbrite may require some time to approve newly created API key applications. If you do not receive an approval email within a few business days, check the API Keys section of your Account Settings or contact Eventbrite support. Additional details are available in the Eventbrite Help Center.
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.
Enter your Eventbrite API key in the API Key field. This key authenticates every request Nexla sends to the Eventbrite API on your behalf. Nexla passes the key as a Bearer token in the Authorization header of each request (i.e., Authorization: Bearer <your_api_key>). You can verify that the key is valid before saving by confirming that it was copied correctly from the Developer Links > API Keys section of your Eventbrite Account Settings.
The API key value is stored securely and will not be displayed again after the credential is saved. If you need to update the key in the future, you can edit the credential and enter a new value.
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 Eventbrite connector tile, 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.
Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Eventbrite endpoints. 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.
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.
Eventbrite data sources can also be manually configured to ingest data from any valid Eventbrite API 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 Eventbrite API v3 endpoints follow the base URL format https://www.eventbriteapi.com/v3/—for example, https://www.eventbriteapi.com/v3/users/me/organizations/ to list organizations or https://www.eventbriteapi.com/v3/events/{'{event_id}'}/attendees/ to list attendees for an event. Eventbrite list responses wrap records in a named array alongside a pagination object, so set Path to Data accordingly—for example, $.events[*], $.attendees[*], $.orders[*], $.organizations[*], $.ticket_classes[*], or $ for single-record responses. Pagination metadata (object_count, page_count, page_size, continuation) is available at $.pagination if you want to include it as record metadata. The Authorization header is applied automatically using the API key from the credential—do not add it manually.
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 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.
Click the + icon on the Nexset that will be sent to the Eventbrite destination, and select the Send to Destination option from the menu. 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.
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Eventbrite endpoints. 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.
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.
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.
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.
:::
Eventbrite destinations can also be manually configured to send data to any valid Eventbrite API endpoint. 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.
Eventbrite's API uses POST for both create and update operations—not PUT or PATCH—and DELETE for removing resources such as ticket classes. All endpoints use the base URL https://www.eventbriteapi.com/v3/ and accept JSON (application/json) request bodies—for example, https://www.eventbriteapi.com/v3/events/{'{event_id}'}/publish/ to publish a draft event or https://www.eventbriteapi.com/v3/webhooks/ to register a webhook. The Authorization and Content-Type: application/json headers are applied automatically based on the credential and selected data format.
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 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.
