This article lists the Eventbrite API endpoints the iPaaS.com Eventbrite integration calls, grouped by entity. Use it as a reference for firewall allow-listing, for troubleshooting, and for checking whether the integration is affected when Eventbrite announces an API change.
API Endpoints Intro
The Eventbrite API is a REST API that returns JSON. The integration sends every transfer TO iPaaS.com: it only reads from Eventbrite, except for the organization webhooks it creates and deletes for this subscription's webhook scopes. It never creates, changes, cancels or refunds an order, attendee or event in Eventbrite.
Requests are sent to the base URL in the subscription's API Url setting. When the setting is blank, the integration uses Eventbrite's published base URL:
https://www.eventbriteapi.com/v3
Throughout this article, [Base URL] stands for that value. For example, reading order 1234567890 calls [Base URL]/orders/1234567890/. Eventbrite's API reference gives this one base URL for all requests.
Several endpoints work inside one Eventbrite organization, shown as {organizationId}. That is the Organization Id setting when it is filled in, or the only organization the private token's user belongs to when it is blank. The organization is resolved when the subscription connects (see Account Endpoints).
For full request and response details, see the Eventbrite API reference.
Table of Contents
Account Endpoints
Order Endpoints
Attendee Endpoints
Webhook Endpoints
Pagination
Rate Limits and Concurrency
Authorization Endpoint
Account Endpoints
Get the Token's User Account (GET)
[Base URL]/users/me/
Retrieves the Eventbrite user account the private token belongs to. Called each time the subscription connects, to prove the Private Token setting before any record is read.
List the User's Organizations (GET)
[Base URL]/users/me/organizations/
Lists the organizations the token's user is a member of. Called each time the subscription connects: with Organization Id blank, the integration works in the only organization listed; with it filled in, the integration checks that the organization is in the list. The answer is kept for that connection only. Returns a paginated response (see Pagination).
Order Endpoints
Get an Order by Id (GET)
[Base URL]/orders/{orderId}/?expand=attendees,event,contact_list_preferences,answers,survey,survey_responses,ticket_buyer_settings,refund_requests,merchandise,concierge,event.venue,event.organizer,event.format,event.category,event.subcategory,event.music_properties,event.ticket_availability,event.external_ticketing,event.event_sales_status,event.checkout_settings,event.basic_inventory_info,event.has_digital_content,event.refund_policy,attendees.contact_list_preferences,attendees.promotional_code,attendees.assigned_unit,attendees.team,attendees.survey,attendees.survey_responsesRetrieves one order together with its attendees, its event and the order's other details, in a single call. Eventbrite's API reference describes the attendee model as "one Attendee per each sold ticket". Used during TO iPaaS.com transfers of the order and of its buyer, to find a person's other tickets on the same order, and to read an event's name and start for a person's Event Attendance record.
Parameter | What the integration reads with it |
expand=attendees | The order's attendees (tickets) |
expand=event | The order's event |
expand=contact_list_preferences | The buyer's marketing opt-in |
expand=answers, survey, survey_responses | The answers to the event's custom registration questions, the order form's questions, and survey responses |
expand=ticket_buyer_settings, refund_requests, merchandise, concierge | The order's buyer settings, refund requests and add-ons |
expand=event.venue, event.organizer, event.format, event.category, event.subcategory, event.music_properties, event.ticket_availability, event.external_ticketing, event.event_sales_status, event.checkout_settings, event.basic_inventory_info, event.has_digital_content, event.refund_policy | The event's details |
expand=attendees.contact_list_preferences, attendees.promotional_code, attendees.assigned_unit, attendees.team, attendees.survey, attendees.survey_responses | Each attendee's own opt-in, promotional code, seat, team and survey |
Eventbrite returns the order whether or not it has each of these details, and leaves out the ones it does not have.
When Eventbrite no longer has the order, there is nothing to transfer and the integration records no error of its own.
List a Person's Orders for an Event (GET)
[Base URL]/events/{eventId}/orders/?only_emails={email}&expand=attendees&status=allLists the orders one email address placed for one event, in every status, with their attendees. Used during every person transfer and for the person's Event Attendance record, so that the person's attendance at an event counts the tickets on every order they placed for it. Returns a paginated response.
Parameter | Meaning |
only_emails | Orders placed by this email address (Eventbrite API reference) |
expand=attendees | The orders' attendees |
status=all | The integration sends the value all to read orders in every status. Eventbrite's API reference does not list this value (it lists active, inactive, both and all_not_deleted); the integration's behavior with it was confirmed in testing. |
List Orders Changed Since (GET)
[Base URL]/organizations/{organizationId}/orders/?changed_since={changedSinceUtc}&status=allLists the organization's orders changed since a date and time, in every status. Used only by the Transaction initialization, run from the subscription, to find the orders changed in the last Initialization Days days; each order found is then transferred on its own with Get an Order by Id. Returns a paginated response.
Parameter | Meaning |
changed_since | Only return orders changed on or after the time given (Eventbrite API reference). The integration sends a UTC date and time, for example 2026-10-08T14:30:00Z. |
status=all | Orders in every status. As for List a Person's Orders for an Event, this value is not listed in Eventbrite's API reference; initialization with it was confirmed in testing. |
Attendee Endpoints
Get an Attendee by Id (GET)
[Base URL]/events/{eventId}/attendees/{attendeeId}/?expand=contact_list_preferences,promotional_code,assigned_unit,answers,survey,survey_responses,eventRetrieves one attendee: their profile (name, email, phone numbers, company, job title and addresses), ticket type, status, check-in and answers, with their own opt-in, promotional code, seat, survey and event. Eventbrite's API reference retrieves an attendee by its event id and attendee id together, so the integration identifies an attendee by both. Used during TO iPaaS.com transfers started by an attendee webhook or by the Customer initialization, and for each attendee other than the buyer when an order transfer or the attendee/registered scope sends the people on an order. When Eventbrite no longer has the attendee, there is nothing to transfer.
List Attendees Changed Since (GET)
[Base URL]/organizations/{organizationId}/attendees/?changed_since={changedSinceUtc}Lists the attendees of the organization's events changed since a date and time. Used only by the Customer initialization, run from the subscription, to find the attendees changed in the last Initialization Days days; each person is then transferred once per event with Get an Attendee by Id. Returns a paginated response.
Parameter | Meaning |
changed_since | Filter attendees by resource changed on or after the time given (Eventbrite API reference). The integration sends a UTC date and time, for example 2026-10-08T14:30:00Z. |
Webhook Endpoints
These endpoints are called only when a webhook scope is turned on or off on the subscription. Each scope that is turned on has one organization-wide Eventbrite webhook that points at this subscription's iPaaS.com webhook address. Eventbrite then sends each change to that address, so anything that filters traffic to iPaaS.com must allow Eventbrite to reach it.
List the Organization's Webhooks (GET)
[Base URL]/organizations/{organizationId}/webhooks/Lists the organization's webhooks, to find the ones that belong to this subscription and scope. Webhooks that belong to anything else in the organization are never changed or deleted. Returns a paginated response.
Create a Webhook (POST)
[Base URL]/organizations/{organizationId}/webhooks/Creates the webhook for a scope that was turned on, when this subscription does not already have it or the subscription's webhook key has changed. The request sets the webhook's address and its one Eventbrite action:
Webhook scope | Eventbrite action |
order.placed | order.placed |
order.updated | order.updated |
order.refunded | order.refunded |
attendee/registered | order.placed |
attendee.updated | attendee.updated |
attendee.checked_in | attendee.checked_in |
attendee.checked_out | attendee.checked_out |
When the organization's webhook list shows the check-in or check-out webhook under the name barcode.checked_in or barcode.un_checked_in, the integration recognizes either name as the same webhook and does not create a duplicate.
Delete a Webhook (DELETE)
[Base URL]/webhooks/{webhookId}/Deletes this subscription's webhook for a scope that was turned off, or an older copy of a scope's webhook after the new one has been created. A webhook that is already gone is not treated as an error.
Pagination
Eventbrite returns lists in pages. Each page carries a continuation token, which Eventbrite's API reference (as published in October 2026) describes as "the continuation token you'll use to get to the next set of results by making the same request again but including this token."
The integration requests the next page with the continuation parameter until Eventbrite reports that there are no more items. The page size is Eventbrite's.
Reading also stops when a page comes back empty, when a continuation token repeats, after 1,000 pages, or once 10,000 records have been read from one list. Because whole pages are read, the last page read can take the count slightly past 10,000.
When a list reaches the 10,000-record limit with more records left, the integration stops reading, records a warning, and does not read the remaining records. For an initialization, lower Initialization Days so that one run covers fewer records, and run it again.
Single orders and attendees are read with one call each and are not paginated.
Rate Limits and Concurrency
Eventbrite's API reference (as published in October 2026) states: "Hourly rate limit has been reached for this token. Default rate limits are 2,000 calls per hour." The limit is counted per private token and is shared by everything that uses the same token, so give each iPaaS.com subscription its own private token.
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. When Eventbrite does not say when the limit resets, the transfer waits one hour. The integration itself never waits or retries in a loop.
If the limit is reached while the subscription is connecting (the checks under Account Endpoints), 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.
With each transfer, the integration passes Eventbrite's remaining calls and reset time to iPaaS.com when Eventbrite reports them, so iPaaS.com can pace the next transfers.
To save calls, an order, or a person's orders for an event, read in the last 60 seconds is reused by the transfers that follow, so one order that starts several person transfers is not read again for each of them.
How fast and how many transfers iPaaS.com sends at once is controlled by the iPaaS.com subscription's throttle and concurrency settings, not by Eventbrite; see Throttling in Eventbrite Connections and Settings. A large initialization uses many calls, so run it when few registrations are arriving.
Authorization Endpoint
The integration does not call a separate authorization or token endpoint. The private token is created in the organizer's Eventbrite account under Account Settings > Developer Links > API Keys, as Eventbrite's help article Generate an API key describes, and the subscription stores it in the Private Token setting. Every call above carries it in the request header, as Eventbrite's API reference describes:
Authorization: Bearer [Private Token]
The integration sends the token only in the request header, never in the URL. The steps to create the token are in Eventbrite Installation Instructions.
Related Documents
External References
Eventbrite API reference: endpoints, parameters, pagination, expansions, errors and rate limits.
