Understanding Organizations

An Organization is an Eventbrite object representing a business structure (like a financial entity, or taxID) in which Events are owned, created and managed. Organizations are owned by one User and can have multiple Members, and are used to group Events, Venues, Members, Permissions and other entities.

The new Organization architecture was introduced in the first half of 2018, to better support Users with more complex needs. This includes the ability for one individual (the Organization owner) to grant and manage the permissions of other Eventbrite Users (other members of the Organization). For example, a music promoter may run an annual festival and multiple music venues. Now with a single Organization account, the music promoter can granularly manage which employees, teams or outside parties (i.e. other Eventbrite Users) have access to specific Events, can take action on those Events, and view associated data.

In addition, Organizations make the experience of using integrated applications more seamless, since your application can access information across Organizations. Previously, Users had to maintain multiple connections to your application through multiple Eventbrite accounts, for example for separate Venues.

Authenticating Your Access to the Eventbrite API

To work with Organizations, you must authenticate your access to the Eventbrite API. To learn how, refer to Authenticating Your Access.

List Your Organizations

Every User has a least one Organization.

GET/v3/users/me/organizations/

Note: A list of all the Organizations to which you belong is returned. If you don't belong to any Organizations, your user_id is your default Organization ID.

Changes to the Permission Model

Permissions are now defined, assigned and managed within the Organization object. Users, and their associated Eventbrite accounts, belong to at least one and possibly multiple organizations. This model provides a lot more flexibility in managing permissions, since a permission can be granted once and used for Events in all the User's Organizations.

The Organization object returns information on which Organizations a User belongs to (is a member of) and what permissions that User has within each Organization.

List Members by Organization ID

GET/v3/organizations/{organization_id}/members/

List Roles by Organization ID

GET/v3/organizations/{organization_id}/roles/

Note: The new Organization architecture does not impact or change the OAuth authentication process.

Migrating to the New Architecture

With the introduction of the Organization object, many of the Eventbrite API endpoints have necessarily changed to indicate the Organization, rather than the User, of an API call. For example, the endpoint previously used to list a User's Events

GET /v3/users/{user_id}/events/ — deprecated

is now replaced by the endpoint to list an Organization's Events

GET/v3/organizations/{organization_id}/events/

Events must be created on New Create to be compatible for Organization and Permissions.

Currently, all Eventbrite Music creators are on Organizations. Access to Organizations for new Eventbrite users started to roll out on January 28th, 2020. Throughout 2020, all users will be migrated to the Organizations and Permissions model. Access to several APIs will no longer be usable on June 1st, 2020, as they are incompatible with Organizations & Permissions.

Here is the list of APIs that are incompatible with Organizations and Permissions:

Note: There are a few new APIs that are missing links because the documentation is currently private.