Eventbrite

Connect & Ingest data from Eventbrite

Eventbrite is an event management and ticketing platform that allows organizers to create, promote, and sell tickets to events. The Sling Eventbrite connector extracts data from the Eventbrite REST API v3, supporting organizations, events, attendees, orders, ticket classes, venues, categories, and formats.

CLI Pro Required: APIs require a CLI Pro token or Platform Plan.

Setup

The following credentials and inputs are accepted:

Secrets:

• private_token (required) -> Your Eventbrite Private OAuth Token

Inputs:

• anchor_date (optional) -> The starting date for historical data extraction (default: 1 year ago). Format: YYYY-MM-DDTHH:MM:SSZ

Getting Your Private Token

1. Log in to your Eventbrite account

2. Go to API Keys in the Eventbrite Platform

3. Create a new API Key if you don't have one

4. Copy your Private token from the API key details

Important: Use your Private token (OAuth token), not the API key or public token. The Private token provides authenticated access to your Eventbrite data.

Using sling conns

Here are examples of setting a connection named EVENTBRITE. We must provide the type=api property:

sling conns set EVENTBRITE type=api spec=eventbrite secrets='{ private_token: your_private_token_here }'

Environment Variable

export EVENTBRITE='{ type: api, spec: eventbrite, secrets: { private_token: "your_private_token_here" } }'

Sling Env File YAML

See here to learn more about the sling env.yaml file.

connections:
  EVENTBRITE:
    type: api
    spec: eventbrite
    secrets:
      private_token: "your_private_token_here"

With anchor date for historical data:

connections:
  EVENTBRITE:
    type: api
    spec: eventbrite
    secrets:
      private_token: "your_private_token_here"
    inputs:
      anchor_date: "2023-01-01T00:00:00Z"

Replication

Here's an example replication configuration to sync Eventbrite data to a PostgreSQL database:

source: EVENTBRITE
target: MY_POSTGRES

defaults:
  mode: full-refresh
  object: eventbrite.{stream_name}

streams:
  # Core data
  organizations:
  events:
    mode: incremental
    primary_key: [id]
    update_key: changed
  attendees:
    mode: incremental
    primary_key: [id]
    update_key: changed
  orders:
    mode: incremental
    primary_key: [id]
    update_key: changed

  # Reference data
  ticket_classes:
  venues:
  categories:
  formats:

Endpoints

Core Data

Endpoint	Description	Incremental
organizations	Organizations for the authenticated user	No
events	All events for each organization	Yes
attendees	Attendees for each event	Yes
orders	Orders for each organization	Yes

Event Details

Endpoint	Description	Incremental
ticket_classes	Ticket classes (types) for each event	No
venues	Venues for each organization	No

Reference Data

Endpoint	Description	Incremental
categories	All event categories	No
formats	All event formats (conference, seminar, etc.)	No

To discover available endpoints:

sling conns discover EVENTBRITE

Incremental Sync

The Eventbrite connector uses the changed timestamp for incremental sync on supported endpoints:

• First run: Fetches all records from anchor_date (default: 1 year ago) to present

• Subsequent runs: Only fetches records changed after the last sync

Supported Incremental Endpoints

• events — Tracks the changed field to detect new and modified events

• attendees — Uses changed_since parameter to filter by last sync time

• orders — Uses changed_since parameter to filter by last sync time

Parent-Child Relationships

The connector uses queue-based iteration to handle parent-child relationships:

• Organizations → feeds events, orders, and venues

• Events → feeds attendees and ticket_classes

This means organizations are always fetched first, followed by their dependent endpoints.

Pagination

Eventbrite uses continuation-based pagination. The connector handles this automatically:

• Each response includes a pagination.continuation token

• The connector stops when pagination.has_more_items is false

• Default page size is 50 records per request

Rate Limiting

The Eventbrite API enforces rate limits:

• The connector uses a default rate of 5 requests per second

• Concurrent requests are limited to 3 for child endpoints

• Automatically retries with exponential backoff on 429 (rate limit) responses

• Retries with linear backoff on 5xx server errors

If you are facing issues connecting, please reach out to us at [email protected], on discord or open a Github Issue here.