Skip to main content

iPaaS.com <> Eventbrite: Background

Learn about the Eventbrite integration and what it supports.

Introduction to Eventbrite

The Eventbrite integration on iPaaS.com brings your Eventbrite registrations and check-ins TO iPaaS.com, so who registered and who actually attended appears on each person's record in the systems you connect through iPaaS.com that map the attendance fields.

API Version Support

iPaaS.com connects to Eventbrite through the Eventbrite Platform API v3, signed with a private token that you create in your Eventbrite account. The integration was built and tested against the documented production v3 endpoints as of November 10, 2026.

  • Changes reach iPaaS.com through Eventbrite webhooks, which the integration registers in your Eventbrite organization when you turn on its scopes.

  • It works with the orders, attendees and events of one Eventbrite organization per subscription.

Data Flows

The table below shows the data each side exchanges, the direction it moves, and whether past records can be loaded (initialized) when a subscription is set up.

iPaaS.com

Direction

Eventbrite

Allow Initialization?

Customer

←

Attendee and order buyer

✔️

Transaction

←

Order

✔️

Transaction (type Ticket)

←

Event attendance (one person at one event)

✔️

← iPaaS.com captures the record from Eventbrite.

Every flow runs TO iPaaS.com: the integration reads from Eventbrite and never writes orders, attendees or events back to it. Each customer brings its addresses, and each order brings its ticket lines, registration answers and taxes.

Versions and Release Notes

Version

Release Notes

1.0.0 (current)

Initial release: Eventbrite attendees and order buyers TO iPaaS.com as customers, one per email address, with their addresses and their event attendance (events registered for and attended, counts, and the newest of each). Eventbrite orders TO iPaaS.com as transactions with one line per ticket, the ticket's attendance as the line status, each registration answer as a transaction note and each tax as a transaction tax. Each person's attendance at each event as a transaction of type Ticket on their own customer, guests included, with no amounts. Changes arrive within a few minutes through webhooks the integration sets up, and past orders and attendees can be loaded by initialization.

Features by Release

The highlights below list what the Eventbrite integration supports and link to the mapping documentation for each. See the Eventbrite Integration Known Limitations article for what it does not do.

Version 1.0.0 — Initial release

  • Attendees and buyers as customers: every attendee and order buyer becomes an iPaaS.com customer, one per email address, linked by email to a customer iPaaS.com already has (for example from your CRM), with home, work, shipping and billing addresses.

  • Attendance on the customer: the events each person registered for and attended, their counts, the newest of each, and their status at the latest event, as customer custom fields that receiving systems can map.

  • Orders as transactions: each Eventbrite order becomes an iPaaS.com transaction with the event and the order's amounts as Eventbrite reports them, one line per ticket with its attendance, each registration answer as a transaction note, and each tax as a transaction tax.

  • Attendance records: each person's attendance at each event as a transaction of type Ticket on the person's own customer, guests included, with one line per ticket and no amounts, so ticket money is never counted twice.

  • Webhooks: new orders, changed orders, refunds, attendee changes, check-ins and undone check-ins reach iPaaS.com within a few minutes, through webhooks the integration registers for you.

  • Initialization: past orders and attendees, up to 365 days back.

  • Registration answers in mappings: the answer to any custom registration question, readable in a Dynamic Formula mapping with the EventbriteAnswer function.

Related Documents

Did this answer your question?