Eventbrite

Eventbrite is an online event-planning site. It allows you to create an event page, register attendees, track attendance, promote local events, and even sell tickets online or at the door.

In order to integrate Eventbrite with Relyance AI you will need a Client ID, Client Secret, and will need to follow an Oauth2 flow.

In Eventbrite:

1. Login to your Eventbrite account.
2. Click on the account menu in the top right-hand side and select Account settings.
3. Open the Developer Links section in the left-hand navigation menu and select API Keys.
4. Click the Create API Key button.
5. Fill out the Request a new key form. First Name: << Use your name >> Last Name: << Use your name >> Application URL: https://www.relyance.ai/ OAuth Redirect URI: https://root.relyance.ai/api/oauth2 Application Name: << Provide a relevant name e.g. Relyance AI >> Description: << Provide a description >>
6. Click the Create Key button.
7. This will create a new key and bring you back to your API Keys page. Click the Show API key, client secret and tokens link under the Keys column.
8. Copy the API Key ( Client ID) and Client Secret to be used in Relyance.

In the Relyance AI application:

1. Login to your Relyance account.
2. Navigate to the Settings Menu in the bottom left-hand side.
3. Select Integrations.
4. Click on the Vendor Integration tab.
5. Find the Eventbrite integration card and click it to open its connections.
6. Under Authentication Method, choose Oauth2 / App Token.
7. Paste the Client ID and Client Secret into their respective fields.

9. Click Authenticate.
10. This will open up the Eventbrite page, login if needed, and follow the prompts to grant Relyance permission to Eventbrite.

11. At this point, you should see the following result on the Vendor Integrations page:

12. Congratulations, you are now connected to Eventbrite.

If the connection reports Connected but returns nothing

These are the ways this integration comes back empty without reporting an error. Generated from the integration catalog, so it tracks what the connection actually asks for.

1. Authorised, then empty. The connection carries an authorisation, not a password: it stops returning data if the account that granted it loses access, its own permissions narrow, or the grant is revoked at the vendor. None of that reports an error here -- the connection keeps its last status until the next scan.
2. A credential rotated at the vendor is not picked up here. Client Secret is stored when you save the connection, so regenerating the value at the vendor breaks the next scan until it is re-pasted here. Recording the expiry on the connection means Relyance warns you before it lapses.

Manage this integration with Terraform

Connections for this integration can be managed as code with the Relyance Terraform provider. Non-secret fields go in auth.params; secret fields go in auth.secrets_wo, which is write-only — never stored in Terraform state. Rotate secrets by bumping auth.secrets_wo_version.

The OAuth (browser authorization) method uses a browser authorization flow, so the connection is created in the Relyance app. Manage it in Terraform afterwards by importing it (terraform import relyance_integration_connection.example eventbrite/<connection_id>) or reading it with the relyance_integration_connection data source.