Skip to main content

Authorization

Follow this guide to create a new Eventbrite credential that will allow Nexla to authenticate to and exchange data with your Eventbrite account.
eventbrite_api_auth.png

Eventbrite

Prerequisites​

To connect Nexla to Eventbrite, you need an active Eventbrite account and an API key generated from the Eventbrite Developer Portal. Eventbrite authenticates API requests using a Bearer token—your API key is passed in the Authorization request header as Bearer <your_api_key> on every call.

Generate an Eventbrite API Key​

Eventbrite issues API keys through the Developer Links section of your Account Settings. Each key is tied to an application record that you create in the portal.

  1. Sign in to your Eventbrite account at eventbrite.com.

  2. Click your profile icon in the top-right corner, then select Account Settings from the dropdown menu.

  3. In the left-hand navigation, scroll to the Developer Links section and click API Keys.

  4. Click Create API Key (or Get a Key if you have not created one before).

  5. Fill in the required application details:

    • Application Name: Enter a descriptive name for the integration (e.g., "Nexla Integration").

    • Application URL: Enter the URL of the application or system that will use the key (e.g., your organization's Nexla instance URL or your company website).

    • OAuth Redirect URI: Enter the redirect URI that Eventbrite will use after an OAuth authorization flow. For a server-side integration with Nexla, you can enter your Nexla instance URL.

    • Description (optional): Enter a brief description of how the key will be used.

  6. Accept Eventbrite's API Terms of Service, then submit the form.

  7. Eventbrite will send a confirmation email when your API key is approved. Once approved, return to Account Settings > Developer Links > API Keys to find your API Key (also referred to as your Private Token or OAuth Token).

  8. Copy the API key value and store it securely—it will be required when creating the credential in Nexla.

Treat your Eventbrite API key like a password. Anyone who has access to it can make API calls on behalf of your Eventbrite account. Store it in a secrets manager or secure vault and avoid sharing it in plain text.

Important

Eventbrite may require some time to approve newly created API key applications. If you do not receive an approval email within a few business days, check the API Keys section of your Account Settings or contact Eventbrite support. Additional details are available in the Eventbrite Help Center.

Create an Eventbrite Credential​

  • To create a new Eventbrite credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

Credential Name & Description​

  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

    Resource descriptions are recommended but are not required. They should be used to provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

API Key​

  1. Enter your Eventbrite API key in the API Key field. This key authenticates every request Nexla sends to the Eventbrite API on your behalf.

    Nexla passes the key as a Bearer token in the Authorization header of each request (i.e., Authorization: Bearer <your_api_key>). You can verify that the key is valid before saving by confirming that it was copied correctly from the Developer Links > API Keys section of your Eventbrite Account Settings.

    The API key value is stored securely and will not be displayed again after the credential is saved. If you need to update the key in the future, you can edit the credential and enter a new value.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.