Eventee

Eventee is an event management platform for organizing conferences and events, giving organizers tools to build an agenda, manage speakers and sessions, and engage attendees through a mobile and web app. The Eventee public API exposes an event's content — such as halls, days, lectures, speakers, workshops, tracks, partners, and participants — so it can be read into downstream systems. This connector uses API key (Bearer token) authentication to ingest that event data into Nexla.

Power end-to-end data operations for your Eventee API with Nexla. Our bi-directional Eventee connector is purpose-built for Eventee, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Eventee or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Eventee workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating an Eventee credential, you need to generate an API token for your Eventee organizer account. The Eventee public API uses Bearer token authentication: the token is sent in the Authorization header of every request.

To obtain your Eventee API token, follow these steps:

1. Sign in to the Eventee organizer admin at https://admin.eventee.co/ using your organizer credentials.

2. Open the Settings section, then go to Features.

3. Locate the API access option and generate your unique API token.

4. Copy the generated token and store it securely, as it grants access to your event data through the public API.

The token is passed as a Bearer token in the Authorization header (for example, Authorization: Bearer <your_token>) for all requests to the Eventee public API. Keep this token confidential; if it is compromised, regenerate it from the same Settings > Features screen. For more details on the API and available endpoints, refer to the Eventee API documentation.

Authenticate

Credentials required

Authenticate to Eventee.

Field	Required	Secret	Description
API Key	Yes	Yes	API key.

Create a credential in Nexla

1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

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

3. Enter your Eventee API token in the API Key field. This is the token you generated in Prerequisites; it is sent as a Bearer token in the Authorization header for all requests to the Eventee public API and must be kept confidential.

4. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Eventee connector tile, then select the credential that will be used to connect to Eventee, and click Next; or, create a new Eventee credential for use in this flow.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Eventee endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Halls

This endpoint template retrieves the halls defined for your Eventee event. Use this template when you need to ingest the list of halls (rooms or venues) used to organize sessions.

[Rest API] List Days

This endpoint template retrieves the days that make up your Eventee event's agenda. Use this template when you need to ingest the event's schedule days.

[Rest API] List Lectures

This endpoint template retrieves the lectures scheduled in your Eventee event. Use this template when you need to ingest lecture sessions and their details.

[Rest API] List Speakers

This endpoint template retrieves the speakers associated with your Eventee event. Use this template when you need to ingest speaker profiles and details.

[Rest API] List Workshops

This endpoint template retrieves the workshops scheduled in your Eventee event. Use this template when you need to ingest workshop sessions and their details.

[Rest API] List Pauses

This endpoint template retrieves the pauses (breaks) in your Eventee event's agenda. Use this template when you need to ingest scheduled breaks between sessions.

[Rest API] List Tracks

This endpoint template retrieves the tracks used to categorize sessions in your Eventee event. Use this template when you need to ingest the event's session tracks.

[Rest API] List Partners

This endpoint template retrieves the partners associated with your Eventee event. Use this template when you need to ingest partner or sponsor information.

[Rest API] List Participants

This endpoint template retrieves the participants registered for your Eventee event. Use this template when you need to ingest attendee or participant records.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

Eventee data sources can also be manually configured to ingest data from any valid Eventee public API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Eventee data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.