On24

On24 provides comprehensive virtual event and webinar management solutions, enabling businesses to create, host, and analyze engaging digital experiences with detailed attendee tracking, interactive features, and robust analytics for marketing and sales optimization.

Power end-to-end data operations for your On24 API with Nexla. Our bi-directional On24 connector is purpose-built for On24, 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 On24 or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your On24 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 ON24 credential, you need to obtain your API Base URL, Client ID, Access Token Key, and Access Token Secret from your ON24 account. ON24 uses custom header authentication for all API requests, with the Access Token Key and Access Token Secret sent in custom headers.

To obtain your ON24 API credentials, follow these steps:

1. Sign in to your ON24 account using your administrator credentials.

2. Navigate to your account settings or API management section in the ON24 interface.

3. Look for the API or API Credentials section in your account settings.

4. If you don't have API credentials yet, look for the option to generate or view your Client ID, Access Token Key, and Access Token Secret.

5. Your Client ID will be displayed in the API section. This is a unique identifier for your ON24 API client application.

6. Your Access Token Key will be displayed in the API section. This is used for API authentication.

7. Your Access Token Secret will be displayed in the API section. Copy the Access Token Secret immediately, as it may not be accessible again after you navigate away from the page.

8. Identify your API Base URL based on your ON24 datacenter:

   • North America Data Center: https://api.on24.com
   • EU Data Center: https://api.eu.on24.com

9. Store all credentials securely, as you will need them to configure your Nexla credential. The Access Token Key and Access Token Secret are sensitive information and should be kept confidential.

The Access Token Key and Access Token Secret are sent in custom headers (accessTokenKey and accessTokenSecret) for all API requests to the ON24 API. The Client ID is used to identify your API client application. The API Base URL determines which ON24 datacenter your API requests will be sent to. If your credentials are compromised, you should immediately revoke them in your ON24 account settings and generate new ones. For detailed information about obtaining API credentials, API authentication, and available endpoints, refer to the ON24 API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Base URL	Yes	No	The base for API requests. This is dependant on the datacenter where your accounts are hosted. Allowed values: https://api.on24.com (Select this if your On24 accounts are hosted in North America Data Center); https://api.eu.on24.com (Select this if your On24 accounts are hosted in EU Data Center)
Client ID	Yes	Yes	Your On24 API Client ID. Check out On24 documentation for how to create this in your On24 account.
Access Token Key	Yes	Yes	Your On24 API Access Token Key. Check out On24 documentation for how to create this in your On24 account.
Access Token Secret	Yes	Yes	Your On24 API Access Token Secret. Check out On24 documentation for how to create this in your On24 account.

Create a credential in Nexla

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

New Credential Overlay – ON24

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 ON24 API Base URL in the API Base URL field. Select https://api.on24.com if your ON24 accounts are hosted in the North America Data Center, or https://api.eu.on24.com if your ON24 accounts are hosted in the EU Data Center. The API Base URL determines which ON24 datacenter your API requests will be sent to.

4. Enter your ON24 Client ID in the Client ID field. This is the Client ID you obtained from your ON24 account settings (API or API Credentials section). The Client ID is used to identify your API client application.

5. Enter your ON24 Access Token Key in the Access Token Key field. This is the Access Token Key you obtained from your ON24 account settings. The Access Token Key is sent in the accessTokenKey header for all API requests to the ON24 API. The Access Token Key is sensitive information and must be kept confidential.

6. Enter your ON24 Access Token Secret in the Access Token Secret field. This is the Access Token Secret you obtained from your ON24 account settings. The Access Token Secret is sent in the accessTokenSecret header for all API requests to the ON24 API. The Access Token Secret is sensitive information and must be kept confidential.

   Your ON24 API credentials can be found in your ON24 account settings under the API or API Credentials section. The Access Token Key and Access Token Secret are sent in custom headers (accessTokenKey and accessTokenSecret) for all API requests to the ON24 API. The Client ID is used to identify your API client application, and the API Base URL should match your ON24 datacenter (North America or EU).

   If your credentials are compromised, you should immediately revoke them in your ON24 account settings and generate new ones. The Access Token Key and Access Token Secret provide access to your ON24 account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.

   For detailed information about obtaining API credentials, API authentication, and available endpoints, see the ON24 API documentation.

7. 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/destination 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 ON24 connector tile, then select the credential that will be used to connect to your ON24 account, and click Next; or, create a new ON24 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 ON24 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.

Get a List of Events for a Client

This endpoint template retrieves a listing of events for a particular client from your ON24 account. Use this template when you need to retrieve event information, event details, or event metadata for your ON24 virtual events and webinars. Events belonging to sub-client accounts are not included in the response.

• This endpoint automatically retrieves all events for your ON24 client. No additional configuration is required beyond selecting this endpoint template. The endpoint uses incrementing page-based pagination to handle large datasets efficiently.

This endpoint retrieves a listing of events for your ON24 client. The endpoint uses incrementing page-based pagination with pageOffset and itemsPerPage parameters to handle large datasets efficiently. Nexla will automatically fetch subsequent pages of data by incrementing the page offset. The endpoint returns up to 100 events per page by default.

Events belonging to sub-client accounts are not included in the response. For detailed information about event management, API response structures, pagination, and available event data, see the ON24 API documentation.

Get a List of Attendees for a Client

This endpoint template retrieves a listing of attendees for a particular client from your ON24 account. Use this template when you need to retrieve attendee information, attendee details, or attendee registration data for your ON24 virtual events and webinars.

• This endpoint automatically retrieves all attendees for your ON24 client. No additional configuration is required beyond selecting this endpoint template. The endpoint uses incrementing page-based pagination to handle large datasets efficiently.

This endpoint retrieves a listing of attendees for your ON24 client. The endpoint uses incrementing page-based pagination with pageOffset and itemsPerPage parameters to handle large datasets efficiently. Nexla will automatically fetch subsequent pages of data by incrementing the page offset. The endpoint returns up to 100 attendees per page by default.

For detailed information about attendee management, API response structures, pagination, and available attendee data, see the ON24 API documentation.

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

ON24 data sources can also be manually configured to ingest data from any valid ON24 API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom query parameters and filters. 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.

The ON24 API endpoint URL should include your API base URL (from your credential), the API path (e.g., /v2/client/{client_id}/event), and any required query parameters (e.g., https://api.on24.com/v2/client/{client_id}/event?itemsPerPage=100). For the Response Data Path, use $.events[*] to extract all events from the events array, or $.attendees[*] to extract all attendees from the attendees array, depending on your endpoint. ON24 uses incrementing page-based pagination with pageOffset and itemsPerPage parameters for most endpoints.

Once all of the relevant steps have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the data source configuration for later use.