RingCentral Events
RingCentral Events (formerly Hopin) is a virtual, hybrid, and in-person event platform. Its REST API lets you manage organizations, events, registrations, sessions, tickets, booths, reports, and magic links programmatically. Nexla connects to the RingCentral Events API using OAuth 2.0 to ingest event data into your pipelines and to push records such as new events and registrations back to the platform.
Power end-to-end data operations for your RingCentral Events API with Nexla. Our bi-directional RingCentral Events connector is purpose-built for RingCentral Events, 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 RingCentral Events or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your RingCentral Events workflows fast, secure, and fully governed.
Features
Type: API
- 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 a RingCentral Events credential, you need to register an OAuth application in the RingCentral Developer Console and obtain its Client ID and Client Secret. The RingCentral Events API uses the OAuth 2.0 three-legged authorization-code flow, and Nexla exchanges the resulting authorization code for an access token automatically.
To obtain your credentials, follow these steps:
-
Sign in to the RingCentral Developer Console with your RingCentral account.
-
Navigate to Console > Apps and click Create App.
-
For the app type, select REST API App.
-
Under Authentication, select the 3-legged OAuth flow authorization code grant type and the Server-side web app platform type.
-
Configure the OAuth scopes (permissions) your integration requires, and add Nexla's redirect (callback) URL to the app's allowed redirect URIs.
-
Save the app. From the app's dashboard, copy the Client ID and Client Secret and store them securely — you will enter them when creating your Nexla credential.
For details on registering applications, the authorization-code flow, redirect URIs, and available scopes, see the RingCentral Events Developer Portal and its authentication guide.
Authenticate
Credentials required
Authenticate using the OAuth 2.0 three-legged authorization-code flow. The user grants permission in RingCentral Events, and Nexla exchanges the authorization code for an access token that is sent as a Bearer token on API requests.
| Field | Required | Secret | Description |
|---|---|---|---|
| Authorization URL | No | No | The URL endpoint where users authenticate and authorize access |
| Client ID | Yes | Yes | A unique public identifier assigned to your application |
| Access Scope | No | No | A space-separated list of permissions your application requests |
| Token URL | No | No | The URL endpoint where authorization codes are exchanged for access tokens |
| Client Secret | No | Yes | A private key used to authenticate your application when requesting tokens |
Create a credential in Nexla
-
After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.
-
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
-
RingCentral Events uses a 3-legged OAuth 2.0 flow, where users authorize Nexla to access their event data by signing in to RingCentral Events and granting permission. Enter the Client ID from your RingCentral Events OAuth application in the Client ID field. This is the unique public identifier assigned to your application.
-
Enter the Client Secret from your RingCentral Events OAuth application in the Client Secret field. This private key authenticates Nexla's requests when exchanging the authorization code for an access token.
ImportantThe Client Secret should be kept confidential and never shared. It authenticates your application with RingCentral Events during the token exchange process.
-
In the Access Scope field, enter a space-separated list of OAuth scopes matching the permissions your integration requires. Request only the scopes necessary for your use case, and ensure they match or are a subset of the scopes configured on your RingCentral Events OAuth application.
-
The Authorization URL and Token URL fields are pre-filled with RingCentral Events' standard OAuth endpoints and should remain unchanged for most integrations.
-
Click the Authorize button to begin the OAuth authorization flow. You will be redirected to the RingCentral Events sign-in page.
-
Sign in with your RingCentral Events account credentials and review the requested permissions. Grant access to allow Nexla to connect to your account.
-
After authorization is complete, you will be redirected back to Nexla and the credential will be populated with an access token automatically.
RingCentral Events access tokens expire periodically. Nexla automatically handles token refresh using the refresh token obtained during the initial authorization, so you do not need to manually re-authorize the credential under normal circumstances.
-
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 and can be selected for use with a new data source or destination.
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 RingCentral Events connector tile, then select the credential that will be used to connect to RingCentral Events, and click Next; or, create a new RingCentral Events 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 RingCentral Events 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.
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
RingCentral Events data sources can also be manually configured to ingest data from any valid RingCentral Events 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 RingCentral Events 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.
Use as a destination
Click the + icon on the Nexset that will be sent to the RingCentral Events destination, and select the Send to Destination option from the menu. Select the RingCentral Events connector from the list of available destination connectors, then select the credential that will be used to connect to RingCentral Events, and click Next; or, create a new RingCentral Events credential for use in this flow.
Endpoint templates
Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common RingCentral Events endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.
Manual configuration
RingCentral Events destinations can also be manually configured to send data to any valid RingCentral Events API endpoint. 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, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.
Save & activate
Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured RingCentral Events endpoint, open the destination resource menu, and select Activate.
The Nexset data will not be sent to the RingCentral Events endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.