Zoom

Zoom is a leading video conferencing and communication platform that enables virtual meetings, webinars, chat, and phone services, providing reliable and secure collaboration tools for remote work, education, and business communications.

Power end-to-end data operations for your Zoom API with Nexla. Our bi-directional Zoom connector is purpose-built for Zoom, 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 Zoom or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Zoom 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 a Zoom credential, ensure you have the following:

Zoom Account

You must have an active Zoom account with administrative privileges. This account provides access to the Zoom platform and its API.

Zoom App Registration

You need to create a Server-to-Server OAuth application in your Zoom developer account to obtain the required credentials for API access.

Server-to-Server OAuth Credentials

The Zoom API uses Server-to-Server OAuth for authentication. You will need to obtain Account ID, Client ID, and Client Secret credentials for your application.

1. Create a Server-to-Server OAuth App: Follow the instructions in the Zoom Developer Documentation to create a Server-to-Server OAuth application in your Zoom developer account.

2. Configure App Settings: During app creation, ensure you select the appropriate scopes for your use case. Common scopes include:

   • User Management: For managing users and their settings
   • Meeting Management: For creating and managing meetings
   • Webinar Management: For webinar operations
   • Phone Management: For phone system operations

3. Note your credentials: Once created, you will be provided with an Account ID, Client ID, and Client Secret. Keep these secure, as they are essential for authenticating your API requests.

For complete information about setting up Zoom Server-to-Server OAuth applications and obtaining credentials, refer to the official Zoom Developer Documentation.

Required Scopes

Ensure your Server-to-Server OAuth application is granted the necessary scopes to access the required Zoom functionality. The specific scopes needed depend on your use case:

• User Management: user:read, user:write for user administration
• Meeting Management: meeting:read, meeting:write for meeting operations
• Webinar Management: webinar:read, webinar:write for webinar operations
• Phone Management: phone:read, phone:write for phone system operations
• Reporting: report:read for accessing usage reports

Credential Validation

The Server-to-Server OAuth application requires a validation URL to test credentials. By default, this is set to https://api.zoom.us/v2/users/me, but you can customize this URL based on your specific needs and approved scopes.

Authenticate

Credentials required

Zoom Server-to-Server authentication enables you to securely integrate with Zoom APIs and get your account owner access token without user interaction.

Field	Required	Secret	Description
Zoom App: Account ID	Yes	No	Account ID of your Server-to-Server application. You can find your application credentials in your Zoom developer account.
Zoom App: Client ID	Yes	No	Client ID of your Server-to-Server application. You can find your application credentials in your Zoom developer account.
Zoom App: Client Secret	Yes	Yes	Client Secret of your Server-to-Server application. You can find your application credentials in your Zoom developer account.
Credential Validation URL	No	No	Set the URL that should be used for validating the credentials. Note that this endpoint must be part of the scopes you have approved for the Server-to-Server application.

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 – Zoom

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

3. Zoom uses Server-to-Server OAuth authentication, which provides secure, automated access to Zoom APIs without requiring user interaction. Enter your Zoom App: Account ID in the Zoom App: Account ID field. This should be the Account ID of your Server-to-Server OAuth application. This unique identifier is provided when you create your Server-to-Server OAuth app in the Zoom developer portal.

4. Enter your Zoom App: Client ID in the Zoom App: Client ID field. This should be the Client ID of your Server-to-Server OAuth application. This identifier is used to authenticate your application with Zoom's OAuth service.

5. Enter your Zoom App: Client Secret in the Zoom App: Client Secret field. This should be the Client Secret of your Server-to-Server OAuth application. This secret key is used to securely authenticate your application and should be kept confidential. The Client Secret is sensitive information and must be kept confidential.

6. Enter your Credential Validation URL in the Credential Validation URL field. This should be the URL that will be used for validating the credentials. This endpoint must be part of the scopes you have approved for your Server-to-Server OAuth application. The default value is https://api.zoom.us/v2/users/me, but you can customize this based on your needs.

   Your Zoom credentials (Account ID, Client ID, Client Secret) can be found in your Zoom developer account after creating a Server-to-Server OAuth application. The Credential Validation URL is used to test your credentials when creating the credential in Nexla. Ensure this endpoint is included in the scopes approved for your Server-to-Server OAuth application.

   Keep your Client Secret secure and never expose it in client-side code or public repositories. Only request the minimum scopes necessary for your application's functionality to follow the principle of least privilege. Server-to-Server OAuth tokens are automatically managed by Nexla, eliminating the need for manual token refresh operations.

   For detailed information about Zoom API authentication, rate limits, and best practices, see the Zoom Developer Documentation and Zoom API Rate Limiting 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 Zoom connector tile, then select the credential that will be used to connect to the Zoom instance, and click Next; or, create a new Zoom 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 Zoom 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 All Users

This endpoint retrieves a list of all users in your Zoom account. Use this endpoint when you need to access user information, roles, and account details for analysis, reporting, or user management purposes.

• This endpoint automatically retrieves all users accessible to your account. No additional configuration is required beyond selecting this endpoint template.
• The endpoint uses pagination to handle large user datasets efficiently, automatically fetching additional pages as needed.
• Each user record includes information such as user ID, email, display name, role, status, and account settings.

This endpoint returns comprehensive user information including user IDs, email addresses, and account roles. Use this data for user management, reporting, and integration with other systems. For complete information about user management, see the Zoom API Documentation.

Get User's Meetings

This endpoint retrieves all meetings scheduled by a specific user (meeting host). Use this endpoint when you need detailed meeting information, scheduling data, or meeting analytics for a particular user.

• Enter the User ID in the User ID field. You can find this ID by first using the "Get All Users" endpoint to retrieve available users and their corresponding IDs.
• The endpoint will return all meetings associated with the specified user, including meeting details, scheduling information, and participant data.
• This endpoint supports pagination to handle users with large numbers of meetings efficiently.

User IDs are unique identifiers that can be obtained from the "Get All Users" endpoint. This endpoint only returns scheduled meetings, not instant meetings. For complete information about meeting management, see the Zoom API Documentation.

Get Webinar Participant Reports

This endpoint retrieves detailed reports on webinar attendees. Use this endpoint when you need participant analytics, attendance data, or engagement metrics for your webinars.

• Enter the Webinar ID in the Webinar ID field. This is the unique identifier for the webinar you want to analyze.
• The endpoint will return detailed participant information including attendance duration, engagement metrics, and participant details.
• This endpoint provides data for webinars held within the last 6 months.

Webinar IDs are unique identifiers that can be found in your Zoom account's webinar management section. This endpoint provides comprehensive participant analytics for webinar performance analysis. For complete information about webinar reporting, see the Zoom 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

Zoom data sources can also be manually configured to ingest data from any valid Zoom 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 Zoom 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 Zoom destination, and select the Send to Destination option from the menu. Select the Zoom connector from the list of available destination connectors, then select the credential that will be used to connect to the Zoom organization, and click Next; or, create a new Zoom 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 Zoom 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.

Add Meeting Registrants

This endpoint registers participants for a Zoom meeting. Use this template when you need to automatically add registrants to scheduled meetings based on data from your Nexla flows.

• Enter the Meeting ID in the Meeting ID field. This is the unique identifier for the Zoom meeting where you want to add registrants. You can find this ID in your Zoom account or by using the "Get User's Meetings" source endpoint.
• The endpoint will automatically send participant data from your Nexset to the Zoom meeting registration system.
• Each record in your Nexset will be processed as a separate registrant, allowing you to bulk-register multiple participants at once.

Meeting IDs are unique identifiers that can be obtained from your Zoom account or by using Zoom's API to list meetings. Ensure you have the correct Meeting ID before configuring this endpoint. For complete information about meeting registrant management, see the Zoom API Documentation.

Update Phone Blocked List

This endpoint updates Zoom's phone blocked list to manage which phone numbers are blocked from calling into Zoom meetings. Use this template when you need to automatically manage blocked phone numbers based on data from your Nexla flows.

• Enter the Block List ID in the Block List ID field. This is the unique identifier for the phone blocked list you want to update. You can find this ID in your Zoom account settings under Phone Management.
• The endpoint will automatically send phone number data from your Nexset to update the blocked list.
• Each record in your Nexset will be processed to update the blocked list configuration, allowing you to bulk-manage blocked phone numbers.

Block List IDs are unique identifiers that can be found in your Zoom account's Phone Management settings. Ensure you have the correct Block List ID before configuring this endpoint. For complete information about phone blocked list management, see the Zoom API Documentation.

Manual configuration

Zoom destinations can also be manually configured to send data to any valid Zoom API endpoint. Using manual configuration, you can also configure Nexla to automatically send the response received from the Zoom API after each call to a new Nexla webhook data source. 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.

Zoom APIs typically expect JSON format for most operations.

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 Zoom endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Zoom endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.