Skip to main content

Eventbrite Connections and Settings

How to connect Eventbrite to iPaaS.com: the private token, the Organization Id, Initialization Days and API Url settings, the webhook scopes, initialization and throttling.

Integrate iPaaS.com with Eventbrite to enable seamless data synchronization for Eventbrite attendees and order buyers (as iPaaS.com customers with their addresses), orders and their tickets (as transactions and transaction lines), and each person's attendance at each event.

How to Connect

Prerequisites

Before configuring the integration in iPaaS.com, set up API access in Eventbrite:

  • An Eventbrite user who is an owner or admin of the organization that runs your events. The integration acts as this user and can do only what this user can do in the organization. Eventbrite's help notes that a user who does not see API Keys under Developer Links may not have been given permission by the organization, and should ask the owner or an admin for the Create webhooks permission (Generate an API key). Creating the token with a shared owner or admin account, rather than a person's own account, keeps the integration working when people change roles.

  • An Eventbrite API key for that user, and its private token. Eventbrite's help describes creating the key: open Account Settings, select API Keys under Developer Links, select Create API key, complete the form and select Create Key (Generate an API key). Eventbrite may email you when the key is approved. Eventbrite's API reference then says to open your API Keys page and copy your private token (Eventbrite API reference). The integration does not use OAuth, so the form's OAuth Redirect URI can stay empty.

  • One API key for each iPaaS.com subscription. Eventbrite counts its API limit per token, so a token shared with other tools or subscriptions shares that limit (see Throttling).

Configuration Details

You will need the following values to connect:

  • Private Token: The value Eventbrite labels Your private token on the API key's page. It is the only credential the integration uses. The other values on that page (the API key itself, the client secret and the public token) are not used and do not work in this setting. Paste it exactly as Eventbrite shows it, and keep it private: anyone who has it can read your organization's orders and attendees. Example: (your Eventbrite private token, copied from Your private token).

  • Organization Id: The id of the Eventbrite organization whose orders, attendees and webhooks the integration works with. Leave it blank when the token's user belongs to one organization. The organization id is not the organizer id shown in an Organizer Profile URL: Eventbrite's API reference says the organization id "is NOT equal to an organizer_id" (Eventbrite API reference). How to find it is described under Organization Id below. Example: 1234567890123.

  • Initialization Days: How many days back an initialization run looks. Example: 30.

  • API Url: The address of the Eventbrite API. Leave the default. Example: https://www.eventbriteapi.com/v3

Configure Subscription Settings

In your iPaaS.com subscription, open the Eventbrite subscription settings and complete the integration's own fields below, which appear in this order. The iPaaS.com throttle and concurrency fields on the same page are described under Throttling.

The Subscription Settings of an Eventbrite subscription, with the Private Token, Organization Id, Initialization Days, API Url and throttle fields

Field

Description

Required

Example

Private Token

The Eventbrite private token the integration sends with every call to Eventbrite. Spaces before or after the value are removed.

Yes

(your Eventbrite private token)

Organization Id

The Eventbrite organization the integration works in. Blank: the integration uses the one organization the token's user belongs to. Filled: the integration uses this organization, after checking that the token's user belongs to it. Needed when the token's user belongs to several Eventbrite organizations; otherwise leave it blank.

No

1234567890123

Initialization Days

How far back the two initialization runs look, in whole days. Pre-populated with 7.

No

7, 90 or 365

API Url

The address of the Eventbrite API. Pre-populated with Eventbrite's address. A blank value uses the same address.

No

Private Token

  • Empty: the integration cannot connect, and its reason reads: "The Private Token setting is required. In Eventbrite, open Account Settings > Developer Links > API Keys, create a key and copy "Your private token"."

  • Not accepted by Eventbrite, for example mistyped: every call fails with Eventbrite's reason followed by: "Check the Private Token setting: in Eventbrite, Account Settings > Developer Links > API Keys, copy "Your private token"."

  • If the API key is deleted in Eventbrite: create a new one, paste its private token into Private Token and click Apply, then turn each webhook scope off and on again (see below).

  • A user without enough rights in the organization: reading orders or creating webhooks is refused, with the advice "use a token of an organization owner or admin".

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

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.

Organization Id

When Organization Id is blank, the integration lists the organizations the token's user belongs to and uses the only one. When the user belongs to several organizations, or to none, or when Organization Id names an organization the user does not belong to, the integration cannot connect, and its reason lists every organization the token can see by name and id. The reason reads, depending on the case:

  • "The Private Token can see several Eventbrite organizations: Events Team (1234567890123), Music Nights (2345678901234). Put the one that runs your events in the Organization Id setting."

  • "The Organization Id setting (1234567) is not an organization the Private Token can see. Organizations it can see: Events Team (1234567890123). Correct the setting, or leave it blank when there is only one."

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

To find the id, leave Organization Id blank, click Apply, and resend one Eventbrite order from Manual Sync by its order number. If the token's user belongs to several organizations, the connection fails with the first reason above, which lists them. 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.

Use one Eventbrite subscription for each Eventbrite organization. Each subscription keeps its own webhooks, so a second subscription on the same organization receives every order a second time. Subscribers should validate this behavior in a staging environment before relying on it in production.

DESTRUCTIVE SETTING: Organization Id, and a Private Token from another organization. These settings decide which Eventbrite organization the subscription works in. Pointing an existing subscription at a different organization leaves its webhooks in the previous organization: records that still arrive from there are skipped, and the new organization sends nothing until its webhooks are created. The orders, people and attendance records already in iPaaS.com stay linked to the previous organization's Eventbrite ids. Do not change the organization on an existing subscription. If a change is unavoidable, follow Changing the organization below. If you are unsure, consult your MiSP (Managed Integration Service Provider) or implementation partner before proceeding: the recovery cost if the change is wrong is significantly higher than the consultation cost.

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 Initialization Support).

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 the leftover webhooks remain in that organization.

Initialization Days

  • A value from 1 to 365 is used as entered. A value above 365 is treated as 365.

  • A blank, zero, negative or non-numeric value uses 7.

  • It applies only when an initialization runs. Webhooks bring every change made after the scopes are turned on, whatever this value is.

  • One run reads at most about 10,000 orders or attendee tickets. For a large organization, lower Initialization Days so one run covers fewer records.

Examples: 7 loads the last week (the default); 90 loads the last quarter; 365 loads the last year.

API Url

Eventbrite's API reference gives a single base address for all calls, https://www.eventbriteapi.com/v3 (Eventbrite API reference), so leave the default. A trailing slash is removed. Use an https address: at the time this documentation was written, an http address is accepted by the setting, but Eventbrite then refuses every call, and the transfer fails with an error that asks you to check the Private Token, even though the token is correct. A value that is not a web address stops the connection, with the reason: "The API Url setting "not a url" is not a web address. Leave it blank (the default is https://www.eventbriteapi.com/v3)." Change it only if iPaaS.com Support asks you to.

When the connection fails

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. Nothing it finds is saved on the subscription. If the check fails, the transfer fails as a connection failure. The failed transfer's message appears in Dashboard / Integration Monitoring / Error Logs, and the reason is one of the integration messages quoted above. Work through this checklist:

  • Private Token is the value Eventbrite labels Your private token, not the API key, the client secret or the public token.

  • Organization Id is blank when the token's user belongs to one organization; otherwise it is the id of the organization that runs your events, not an organizer profile id.

Correct the setting and click Apply, then resend the failed records from Manual Sync. See Eventbrite Error Messages for each message and its fix.

Authentication Methods

The integration authenticates to Eventbrite with a private token. There is no OAuth sign-in, no Authorize button and nothing to renew.

  1. In Eventbrite, create an API key while signed in as an owner or admin of the organization, and copy Your private token (see Prerequisites).

  2. Paste it into Private Token in the subscription settings, set Organization Id if the user belongs to several organizations, and click Apply.

  3. iPaaS.com sends the token with every call to Eventbrite. Eventbrite's API reference describes including the token in the Authorization header of each request (Eventbrite API reference).

  4. Each time it connects, the integration reads the token's Eventbrite user to prove the token, and resolves the organization (see When the connection fails).

The token acts as the Eventbrite user who created the API key. If that user leaves the organization or loses the owner or admin role, the integration can no longer read the organization's orders and attendees: sign in as another owner or admin, create an API key, put its private token in Private Token and click Apply (see Private Token above). If Eventbrite stops accepting the token, create a new API key and replace the value.

Inbound Data Flows

Changes reach iPaaS.com through Eventbrite webhooks. There is no scheduled poll. Turn on the scopes for the data you want TO iPaaS.com in the subscription's Inbound Data Flows.

Scope

Type

What it brings TO iPaaS.com

order.placed

Transaction

A new order, with one line per ticket. The buyer and each attendee are sent as customers first.

order.updated

Transaction

A changed order: its state, its tickets and their attendance.

order.refunded

Transaction

A refunded order.

attendee.updated

Customer

An attendee changed in Eventbrite, for example their name, email, answers or address.

attendee.checked_in

Customer

An attendee checked in.

attendee.checked_out

Customer

A check-in was undone, or the attendee was checked out.

attendee/registered

Customer

The people of a new order, without the order. Turn it on only when order.placed is off.

transaction/initialize

Transaction

An initialization run: the orders changed in the last Initialization Days days.

customer/initialize

Customer

An initialization run: the attendees changed in the last Initialization Days days.

  • order.placed and attendee/registered start from the same Eventbrite event. With order.placed on, each new order already sends its people first, so turning on attendee/registered as well would send every person twice. Use attendee/registered only to bring people TO iPaaS.com without orders.

  • After an attendee scope updates a person whose order is already in iPaaS.com, the integration also sends that order again, so the ticket's line status follows the check-in.

  • Each person's attendance record has no scope of its own: it is sent right after the person, whatever started the person's transfer.

What turning a scope on does in Eventbrite. The integration manages the webhooks itself; nothing has to be set up in Eventbrite. Turning on a webhook scope creates one webhook for that scope in your Eventbrite organization, pointing at this subscription's iPaaS.com webhook address with the subscription's webhook key. Turning the scope off deletes that webhook. The initialization scopes create no webhook.

  • The integration changes only its own webhooks for this subscription. Webhooks you or other tools created in the organization are left alone.

  • The Eventbrite API reference names the check-in webhook actions attendee.checked_in and attendee.checked_out (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.

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

  • 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.

What each flow writes is described in Eventbrite to iPaaS.com Attendee Mapping Documentation, Eventbrite to iPaaS.com Order Mapping Documentation and Eventbrite to iPaaS.com Attendance Mapping Documentation.

Initialization Support

Initialization is supported for attendees (Customer) and orders (Transaction). It loads what happened in Eventbrite before the webhook scopes were turned on, and can be run again to catch up after an outage.

  1. Set Initialization Days to how far back to go, up to 365, and click Apply.

  2. 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 once per person per event, with their attendance record. This catches check-ins and cancellations that changed the attendee but not the order, and loads people when orders are not brought TO iPaaS.com.

Running an initialization again creates no duplicates: customers, transactions and attendance records already in iPaaS.com are updated. A run appears in Integration Monitoring as one run; the records it sends do not appear one by one. Attendee addresses and tickets are not initialized on their own: they travel with their person and their order.

Throttling

Eventbrite allows 2,000 API calls per hour for each token by default (Eventbrite API reference), shared by everything that uses the token. When the limit is reached:

  • While a transfer reads records: iPaaS.com holds the transfer and sends it again when Eventbrite's limit resets. When Eventbrite does not say when the limit resets, the transfer waits one hour.

  • While the subscription is connecting: the transfer is not held. It fails as a connection failure instead (see When the connection fails). Resend the record from Manual Sync once the hour has passed.

  • While a webhook scope is being turned on or off: turn the scope off and on again once the hour has passed.

A large initialization uses many calls, so run it when few registrations are arriving, and give each subscription its own API key and private token.

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.

Related Documents

External References

Did this answer your question?