Skip to main content

Eventbrite Installation Instructions

How to install the iPaaS.com Eventbrite integration: the Eventbrite private token, the subscription settings, the event ticket product, the webhook scopes in Inbound Data Flows, and loading past orders and attendees.

This article walks you through installing the Eventbrite integration on iPaaS.com: creating an Eventbrite private token, subscribing, filling in the subscription settings, creating the product your event tickets use, turning on the scopes, loading past orders and attendees, and checking that everything works.

The integration brings Eventbrite orders (registrations) and the people on them TO iPaaS.com. Each person becomes an iPaaS.com customer with a summary of their event attendance, and each person's attendance at each event becomes an attendance record (a transaction of type Ticket, with no amounts) on that person's own customer. The integration never writes orders, attendees or events into Eventbrite, never emails your attendees and never charges anything. The only thing it creates in Eventbrite is its own webhooks.

Before You Begin

You need the following before you start:

  • An Eventbrite organizer account: the account that runs your events.

  • An Eventbrite user who is an owner or admin of that organization: the integration acts as this user, with this user's rights. A user who cannot read the organization's orders or manage its webhooks cannot run the integration.

  • An Eventbrite private token for that user: created in the steps below and saved in the Private Token setting.

  • One iPaaS.com product for event tickets: every ticket line in iPaaS.com names a product by its SKU. See Create the Event Ticket Product below. This step is required.

Use one Eventbrite subscription for each Eventbrite organization. The integration works in exactly one Eventbrite organization, and its webhooks and initialization runs cover the whole organization.

To Create an Eventbrite Private Token

These steps follow Eventbrite's help article Generate an API key and the Authentication section of the Eventbrite API reference.

  1. Sign in to Eventbrite as an owner or admin of the organization that runs your events.

  2. Open Account Settings from the navigation menu.

  3. Under Developer Links, click API Keys.

    • If you do not see API Keys, Eventbrite's help says that your organization's owner or admin must give you the Create webhooks permission.

    The API Keys page in Eventbrite's Account Settings, with Create API Key and the link that shows an API key's values
  4. Click Create API key.

  5. Fill in the form:

    • Application URL: a web address that identifies the requester, for example https://www.ipaas.com.

    • OAuth Redirect URI: leave it blank. The integration does not use OAuth.

    • Application Name: for example iPaaS.com.

    • Description: a short description, for example "iPaaS.com integration for our Eventbrite events."

    • Fill in any other fields the form asks for, such as your name. Eventbrite's help lists Company Name and OAuth Redirect URI as optional.

  6. Click Create Key. Eventbrite's help notes that it emails you when the API key is approved.

  7. On the API Keys page, click Show API key, client secret and tokens next to your API key. In the Eventbrite screens observed when this documentation was written, this link shows the key's values, including the private token. Copy the private token only.

Only the private token goes in the Private Token setting. Do not use the API key, the client secret or the public token shown on the same page.

Keep the private token private: anyone who has it can read your organization's orders and attendees. Eventbrite's API reference advises deleting API keys you no longer need.

Installation Instructions for Integration Setup

  1. In iPaaS.com, in the left navigation, expand Subscriptions Management and click Marketplace.

  2. Click the Eventbrite integration tile.

    The Eventbrite tile in the iPaaS.com marketplace
  3. Click the Subscribe button.

    The Eventbrite integration page in the iPaaS.com marketplace, with the Subscribe button
  4. The Subscription Settings page opens. Fill in the following fields:

    • Name: enter a unique subscription name.

      • Format: [Product Name] - [Environment/Purpose]

      • Example: Eventbrite - Production

    • Versions: select a version from the dropdown.

    • Create Default Mappings: leave checked (recommended). The default mapping collections and translations listed under Default Mapping Collections below are created with the subscription. Uncheck it only if you want to create every mapping yourself.

    • Private Token: paste the private token you copied in To Create an Eventbrite Private Token. Required.

    • Organization Id: leave blank when the token's Eventbrite user belongs to one organization. See Organization Id under Authentication Configuration below.

    • Initialization Days: how far back an initialization run looks. Default: 7. See Additional Configuration Options below.

    • API Url: leave at its default, Eventbrite's own API address. A blank value means the same address.

    • API Throttle Limit, API Throttle Seconds, API Throttle Limit (To iPaaS), API Throttle Seconds (To iPaaS), Concurrent Connections and Concurrent Batch Executions: The subscription's throttle and concurrency fields are iPaaS.com platform settings: they control how iPaaS.com dispatches work, the integration does not read them, and they do not change Eventbrite's own limit. A new Eventbrite subscription shows API Throttle Limit 500, API Throttle Seconds 60, API Throttle Limit (To iPaaS) 500, API Throttle Seconds (To iPaaS) 60, Concurrent Connections 2 and Concurrent Batch Executions 10. Leave them unless iPaaS.com Support advises a change. For details on how these fields behave, see the Subscription Configuration – Edit article in the iPaaS.com Help Center.

    The Subscription Settings of an Eventbrite subscription, with the Private Token, Organization Id, Initialization Days, API Url and throttle fields
  5. Click Apply to save the settings.

After saving, the Webhook API Key field is generated by iPaaS.com so that iPaaS.com can accept webhooks for the subscription (Subscription Configuration – Edit). It needs no action; do not change it.

The integration checks the settings each time it connects to Eventbrite for a transfer: it reads the Eventbrite user of the token, then finds the organization. See Post-Installation Verification below.

Default Mapping Collections

With Create Default Mappings checked, the subscription gets these collections, all TO iPaaS.com:

  • Add/Update Eventbrite Attendee TO iPaaS.com: each Eventbrite attendee and order buyer becomes an iPaaS.com customer, one customer per email address, with the person's attendance in customer custom fields.

  • Add/Update Eventbrite Attendee Address TO iPaaS.com: the addresses on the person's Eventbrite registration, sent with the person.

  • Add/Update Eventbrite Order TO iPaaS.com: each Eventbrite order becomes a transaction of type Order for its buyer.

  • Add/Update Eventbrite Order Ticket TO iPaaS.com: one transaction line per ticket, sent with the order.

  • Add/Update Eventbrite Attendance TO iPaaS.com: each person's attendance at each event becomes a transaction of type Ticket on the person's own customer, with no amounts.

  • Add/Update Eventbrite Attendance Ticket TO iPaaS.com: one line per ticket the person holds for the event, sent with the attendance record.

And these translations:

  • Eventbrite Order State -> iPaaS.com Transaction Status: used by the Order collection's Status.

  • Eventbrite Ticket Attendance -> iPaaS.com Line Status: used by the Status of the Order Ticket and Attendance Ticket collections.

  • Eventbrite Attendance -> iPaaS.com Transaction Status: used by the Attendance collection's Status.

The mappings of each collection are described in Eventbrite to iPaaS.com Attendee Mapping Documentation, Eventbrite to iPaaS.com Order Mapping Documentation and Eventbrite to iPaaS.com Attendance Mapping Documentation.

Authentication Configuration

Eventbrite uses a private token. There is no Authorize button, no OAuth sign-in and nothing to renew: the integration sends the token with every call to Eventbrite.

Private Token

  • Credential Name: Private Token

  • Location: in Eventbrite, Account Settings > Developer Links > API Keys, then Show API key, client secret and tokens next to the API key, then the private token.

  • Description: signs every Eventbrite call in as the Eventbrite user who created the API key. Required.

Organization Id

  • Credential Name: Organization Id

  • Location: not needed when the token's Eventbrite user belongs to one organization. Otherwise, the connection's failure message lists the organizations the token can see (see below).

  • Description: the Eventbrite organization whose orders, attendees and webhooks the integration works with. Optional: fill it in only when the token's Eventbrite user belongs to several organizations.

How to set it:

  • Leave it blank when the token's Eventbrite user belongs to one organization. The integration then uses that organization.

  • Fill it in when the user belongs to several organizations. To find the id, leave Organization Id blank, click Apply, and resend one Eventbrite order from Manual Sync by its order number. The transfer fails with the message "The Private Token can see several Eventbrite organizations: {names and ids}. Put the one that runs your events in the Organization Id setting." Copy the id of the organization that runs your events into Organization Id and click Apply again. If the list is not available to you, your MiSP or iPaaS.com Support can provide it.

  • Do not use the organizer id from an Eventbrite Organizer Profile web address. Eventbrite's API reference states that the organization id is not equal to the organizer id. A value that is not one of the token's organizations fails with "The Organization Id setting ({value}) is not an organization the Private Token can see. Organizations it can see: {names and ids}. Correct the setting, or leave it blank when there is only one."

Important Notes

  • Do not share the private token. Eventbrite's limit of 2,000 calls per hour by default is counted per token (Eventbrite API reference), so everything that uses the same token shares it. Give each iPaaS.com subscription its own API key and private token, and do not use that token in other tools.

  • The token acts as its Eventbrite user. It can do only what that user can do in the organization. Create it as an owner or admin, ideally on a shared owner or admin account rather than a person's own account, so the integration keeps working when someone leaves.

  • If the token's user leaves the organization or loses the owner or admin role, the integration can no longer read the organization's orders and attendees. Create a new API key as another owner or admin and follow Replacing the token for the same organization below.

  • If you delete the API key in Eventbrite, create a new API key and follow Replacing the token for the same organization below.

  • The private token is never written to a log, and it is removed from any Eventbrite message quoted in an error.

Replacing the token for the same organization

To replace the token with a new one for the same organization (for example after the API key was deleted, or after its user left), paste the new private token into Private Token and click Apply, then turn each webhook scope off and on again, and run the initializations over the period since the old key stopped working. The integration matches its webhooks by this subscription, not by the token, but Eventbrite does not say whether a webhook keeps working after the API key that created it is deleted or its user leaves, and a missing webhook fails without an error. To use a token of a different organization, see Changing the organization below.

Changing the organization

Turning a scope off deletes its webhook in the organization the saved settings point to, and turning it on creates the webhook in the organization the saved settings point to. So the order matters:

  1. While the current Private Token and Organization Id are still saved, turn every webhook scope off. This deletes the subscription's webhooks in the current organization.

  2. Change Private Token, Organization Id or both, and click Apply.

  3. Turn the webhook scopes on again. The integration creates one webhook per scope in the new organization.

  4. Changes made in Eventbrite while the scopes were off are not received. Set Initialization Days to cover that period and run the initializations (see Run Initialization From the Subscription).

If the settings were changed first, the integration can no longer remove the webhooks in the previous organization. Records that still arrive from there are skipped, and a user of that organization can delete the leftover webhooks in Eventbrite.

Operational Configuration

Create the Event Ticket Product (required)

Every transaction line in iPaaS.com must name an existing product by its SKU. Eventbrite tickets are not iPaaS.com products, so you choose one product that stands for every event ticket and put its SKU in both ticket collections.

Placeholder value — replace during implementation: the Sku mapping of the Order Ticket and Attendance Ticket collections ships with the instruction text "REPLACE with your event ticket SKU". Replace it with the SKU of the iPaaS.com product you use for event tickets, exactly as it is in iPaaS.com, for example EVENT-TICKET or GA-ADMISSION, or the SKU of an existing product in your iPaaS.com catalog.

  1. In iPaaS.com, create a product for event tickets, for example with SKU EVENT-TICKET or GA-ADMISSION and name Event ticket, or choose an existing product.

  2. Open the collection Add/Update Eventbrite Order Ticket TO iPaaS.com.

  3. Find the Sku mapping and replace "REPLACE with your event ticket SKU" with your product's SKU, exactly as it is in iPaaS.com. Save the mapping.

  4. Open the collection Add/Update Eventbrite Attendance Ticket TO iPaaS.com and make the same change to its Sku mapping. Save the mapping.

Until both are done, every order and every attendance record is refused by iPaaS.com with NFND-1003 ("Product Id: REPLACE with your event ticket SKU does not exist or can not be found."). The people on the order are still sent to iPaaS.com as customers.

The ticket type the attendee bought (for example General Admission or VIP) is kept on each line, in its Description and in the Eventbrite Ticket Class custom field.

Turn On the Scopes in Inbound Data Flows

Changes TO iPaaS.com arrive by Eventbrite webhooks: Eventbrite tells iPaaS.com when something changes. There is no polling. Turn on the scopes in the subscription's Inbound Data Flows section. Turn on these six webhook scopes:

  • order.placed: a new order. The order becomes a transaction with one line per ticket, and the buyer and each attendee are sent as customers first.

  • order.updated: a changed order is sent again.

  • order.refunded: a refunded order is sent again.

  • attendee.updated: an attendee changed in Eventbrite, for example their name, email, answers or address.

  • attendee.checked_in: an attendee checked in at the door.

  • attendee.checked_out: a check-in was undone.

The Inbound Data Flows of an Eventbrite subscription, with the Customer and Transaction webhook scopes and their mapping collections

attendee/registered: turn it on only when order.placed is off, to bring the people of new orders TO iPaaS.com without the orders. It uses the same Eventbrite order event as order.placed. When order.placed is on, each new order already sends its people first, so attendee/registered would send them a second time.

Attendance records need no scope of their own. Every person transfer, whatever started it (a webhook scope, an initialization, an order's people or a Manual Sync), is followed by that person's attendance record for the event, unless no ticket at the event carries the person's email (cancelled and refunded tickets still count, giving a Cancelled or Refunded record), for example a buyer who bought tickets only for others. If you don't want attendance records, turn the Add/Update Eventbrite Attendance TO iPaaS.com collection off.

What turning a webhook scope on does in Eventbrite:

  • Turning a webhook scope on makes the integration create one webhook in your Eventbrite organization for that scope. Turning the scope off deletes that webhook.

  • Do not delete these webhooks in Eventbrite. Without its webhook, a scope receives nothing, and no error tells you so. If one was deleted, turn the scope off and on again in iPaaS.com: the integration creates it again.

  • The Eventbrite API reference names the check-in webhook actions attendee.checked_in and attendee.checked_out (https://www.eventbrite.com/platform/api, Webhooks); in the organization's webhook list observed when this documentation was written, Eventbrite showed them as barcode.checked_in and barcode.un_checked_in. The integration recognizes either name as the same webhook.

  • If iPaaS.com issues the subscription a new webhook key, turn each webhook scope off and on again: turning it off deletes the old webhook, and turning it on creates one with the new key. Changes made in Eventbrite while a scope is off are not received; run the initializations over that period to catch up.

  • The integration only changes webhooks that belong to this subscription. Webhooks you or other tools created in the organization are left alone.

Eventbrite's Manage Webhooks page in Account Settings > Developer Links > Webhooks, with the six webhooks the integration created

Run Initialization From the Subscription

Webhooks bring only the changes made after the scopes are turned on. To bring in orders and attendees from before:

  1. Set Initialization Days to how far back you want to go (up to 365) and click Apply.

  2. In Inbound Data Flows, turn on the transaction/initialize scope and run the initialization from the subscription. Every order changed in that period, in any state, is sent TO iPaaS.com with its people and each person's attendance record.

  3. Turn on the customer/initialize scope and run the initialization from the subscription. Every attendee changed in that period is sent TO iPaaS.com with their attendance record. This catches check-ins that changed the attendee but not the order, and loads people when you do not bring orders TO iPaaS.com.

The initialization scopes create no webhook in Eventbrite. Running an initialization again is safe: an order, customer or attendance record already in iPaaS.com is updated, not duplicated. A large initialization uses many Eventbrite calls, and Eventbrite allows 2,000 calls per hour per private token by default, so run large initializations when few registrations are arriving. When a transfer reaches the hourly limit while it reads records, iPaaS.com holds the transfer and sends it again when Eventbrite's limit resets. If the limit is reached while the subscription is connecting, the transfer is not held: it fails as a connection failure instead. Resend the record from Manual Sync once the hour has passed. If the limit is reached while a webhook scope is being turned on or off, turn the scope off and on again once the hour has passed.

Collect Information From Each Attendee (recommended)

As the Eventbrite API reference describes (https://www.eventbrite.com/platform/api, Attendee object), when an event collects details from the buyer only, every ticket of the order carries the buyer's name and email. Those tickets become one customer (the buyer), registered once for the event and attended when any of the buyer's tickets is checked in. To receive each guest as their own customer, set the event's order form to collect information from each attendee, as described in Eventbrite's help article How to collect information from all event attendees. Set this before registrations open.

The order form is also where you ask for the details the integration can carry, such as an address, a phone number and a job title. The integration can carry only what the order form collects.

Keep Event Registrations Out of Other Order Flows

Eventbrite orders and attendance records are iPaaS.com transactions, so other subscriptions in your company whose transaction collections send transactions FROM iPaaS.com (for example an accounting, ERP, store or point-of-sale system) may pick them up. On each such collection that must not receive event registrations, add the Eventbrite exclusion condition to its filter, as described in Eventbrite to iPaaS.com Order Mapping Documentation. Subscribers should validate this behavior in a staging environment before relying on it in production.

Additional Configuration Options

  • Initialization Days

    • Purpose: how far back the transaction/initialize and customer/initialize runs look, in days.

    • Default Value: 7

    • Range/Format: a whole number from 1 to 365. A value above 365 is treated as 365. A blank, zero, negative or non-numeric value uses 7. It applies only when you run an initialization.

  • API Url

    • Purpose: the address of the Eventbrite API. Eventbrite's API reference gives a single base address for every call, so leave the default.

    • Default Value: Eventbrite's own API address.

    • Range/Format: an http or https web address. A blank value uses the default. A value that is not a web address stops the integration from connecting.

Post-Installation Verification

After completing the installation, perform these tests to verify it. The integration checks the private token and the organization each time it connects to Eventbrite for a transfer, so the first transfer also exercises the settings.

Data Sync Test

  1. Register for one of your events with a free ticket, using an email address you control.

  2. Within a few minutes, check that iPaaS.com has a customer with that email and that the Eventbrite Events Registered custom field names the event.

  3. With orders on, check that iPaaS.com has a transaction with the Eventbrite order number, one line per ticket with your event ticket Sku, and line status Pending.

  4. Check that the customer has an attendance record: a transaction of type Ticket with status Pending, one line per ticket and a total of 0.

Functionality Test

  1. Check the attendee in, in Eventbrite.

  2. Check that the customer's Eventbrite Events Attended custom field names the event, that the ticket's line status is Complete, and that the person's attendance record is Complete.

  3. Review the transfers in iPaaS.com under Dashboard / Integration Monitoring / Error Logs.

If transfers fail because the integration cannot connect with the saved settings, the failed transfer's message appears in Dashboard / Integration Monitoring / Error Logs, and its reason is one of the integration messages under Error Messages below. Correct the setting it names and click Apply. You can also check the settings directly: Private Token is the private token (not the API key, client secret or public token), Organization Id is blank when the token's user belongs to one organization, and API Url is blank or Eventbrite's own address.

Error Messages

Every message the integration records, with its cause and resolution, is listed in Eventbrite Error Messages. The messages you are most likely to meet during installation are below. When a transfer fails, its message appears in Dashboard / Integration Monitoring / Error Logs; see Post-Installation Verification for the settings checklist.

  • "The Private Token setting is required.": the Private Token setting is empty. Create an API key in Eventbrite, copy its private token into Private Token and click Apply.

  • "Eventbrite did not return a user for the Private Token." or "Eventbrite refused … (401)": Eventbrite does not accept the token. Copy the private token again from Account Settings > Developer Links > API Keys and click Apply.

  • "The Private Token can see several Eventbrite organizations" or "The Organization Id setting … is not an organization the Private Token can see": copy the right organization id from the message into Organization Id, or leave it blank when there is only one.

  • "The Private Token's Eventbrite user belongs to no organization.": use the private token of a user in the organization that runs your events.

  • "The API Url setting … is not a web address.": clear API Url (blank means Eventbrite's own address) and click Apply.

  • "Eventbrite couldn't complete checking the Private Token right now": Eventbrite did not answer the connection check. Try again later.

  • "Eventbrite refused … (403)" or "Eventbrite refused the webhook for …": the token's Eventbrite user may not do this in the organization. Use the private token of an owner or admin, then turn the scope off and on again.

  • "NFND-1003 - Product Id: REPLACE with your event ticket SKU does not exist or can not be found.": see Create the Event Ticket Product above, then resend the order from Manual Sync.

Support and Troubleshooting

Click the Help button on any iPaaS.com page to contact iPaaS.com Support or to search our documentation.

Related Documents

Did this answer your question?