Zoom Connector

The high-performance Zoom Connector provides read/write capabilities within your application, allowing you to perform numerous Zoom operations with minimal coding or even no-coding at all. Integrate Zoom data into applications such as SSIS, SQL Server, any ODBC-compatible application, or even directly within a programming language using this connector.

Download for SSIS Download for SQL Server and ODBC Documentation

Integrate Zoom with these applications

All

Data Integration

Database

BI & Reporting

Productivity

Programming Languages

Automation & Scripting

ODBC applications

Azure Data Factory (Pipeline)

Azure Data Factory (SSIS)

Actions supported by Zoom Connector

Zoom Connector support following actions for REST API integration. If some actions are not listed below then you can easily edit Connector file and enhance out of the box functionality.

GET Settings

Retrieve a user's settings. For user-level apps, pass the me value instead of the userId parameter. [ Read more... ]

Parameter	Description
UserId	The user ID or email address of the user. For user-level apps, pass the me value.

List Meetings

Get the list of scheduled meetings. For current user (me) or specified user Id. To get more details about a meeting you can call get_meeting EndPoint. [ Read more... ]

Parameter	Description
UserId	The user ID or email address of the user. For user-level apps, pass the me value.

Get Meeting By Id

The Meeting Id or email address of the user. For user-level apps, pass the me value. [ Read more... ]

Parameter	Description
MeetingId	The Meeting ID for which you want to get details.

List Meeting Registrants

A host or a user with admin permission can require registration for a Zoom meeting. Use this API to list users that have registered for a meeting. [ Read more... ]

Parameter	Description
UserId	Only Used to list Meetings in the UI
MeetingId	The Meeting ID for which you want to get details.

Past Meeting

Use this API to get information about a past meeting. [ Read more... ]

Parameter	Description
MeetingId	The Meeting ID for which you want to get details.

List Registration Questions

List registration questions that will be displayed to users while registering for a meeting. [ Read more... ]

Parameter	Description
MeetingId	The Meeting ID for which you want to get details.

List Users

Use this API to list your account's users.'s users [ Read more... ]

List Webinars

Use this API to list all the webinars scheduled by or on-behalf a user (webinar host). For user-level apps, pass the me value instead of the userId parameter. [ Read more... ]

Parameter	Description
UserId	The user ID or email address of the user. For user-level apps, pass the me value.

Get Webinar Settings

Use this API to get settings details of a scheduled webinar. [ Read more... ]

Parameter	Description
WebinarId	The Webinar ID for which you want to get details.

Get Webinar Settings By Id

Use this API to get details of a scheduled webinar. [ Read more... ]

Parameter	Description
WebinarId	The Webinar ID for which you want to get details.

List Webinar Registrants

Use this API to list all the users that have registered for a webinar. [ Read more... ]

Parameter	Description
WebinarId	The Webinar ID for which you want to get details.

Generic Request

This is generic endpoint. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [ Read more... ]

Parameter

Description

Url

API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains

Body

Request Body content goes here

IsMultiPart

Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle

Filter

Enter filter to extract array from response. Example: $.rows[*] --OR-- $.customers[*].orders[*]. Check your response document and find out hierarchy you like to extract

Option	Value
No filter
Example1	$.store.books[*]
Example2 (Sections Under Books)	$.store.books[].sections[]
Example3 (Equals)	$.store.books[?(@author=='sam')]
Example4 (Equals - Any Section)	$..[?(@author=='sam')]
Example5 (Not Equals - Any Section)	$..[?(@author!='sam')]
Example6 (Number less than)	$.store.books[?(@.price<10)] Example7 (Regular Expression - Contains Pattern)=$.store.books[?(@author=~ /sam\|bob/ )]
Example8 (Regular Expression - Does Not Contain Pattern)	$.store.books[?(@author=~ /^((?!sam\|bob).)*$/ )]
Example9 (Regular Expression - Exact Pattern Match)	$.store.books[?(@author=~ /^sam\|bob$/ )]
Example10 (Regular Expression - Starts With)	$.store.books[?(@author=~ /^sam/ )]
Example11 (Regular Expression - Ends With)	$.store.books[?(@author=~ /sam$/ )]
Example12 (Between)	$.store.employees[?( @.hiredate>'2015-01-01' && @.hiredate<'2015-01-04' )]

Headers

Headers for Request. To enter multiple headers use double pipe or new line after each {header-name}:{value} pair

Generic Request (Bulk Write)

This is a generic endpoint for bulk write purpose. Use this endpoint when some actions are not implemented by connector. Just enter partial URL (Required), Body, Method, Header etc. Most parameters are optional except URL. [ Read more... ]

Parameter	Description
Url	API URL goes here. You can enter full URL or Partial URL relative to Base URL. If it is full URL then domain name must be part of ServiceURL or part of TrustedDomains
IsMultiPart	Set this option if you want to upload file(s) (i.e. POST RAW file data) or send data using Multi-Part encoding method (i.e. Content-Type: multipart/form-data). Multi-Part request allows you to mix key/value and upload files in same request. On the other hand raw upload allows only single file upload (without any key/value) ==== Raw Upload (Content-Type: application/octet-stream) ===== To upload single file in raw mode check this option and specify full file path starting with @ sign in the Body (e.g. @c:\data\myfile.zip ) ==== Form-Data / Multipart Upload (Content-Type: multipart/form-data) ===== To treat your Request data as multi part fields you must specify key/value pairs separated by new lines into RequestData field (i.e. Body). Each key value pair is entered on new-line and key/value are separated using equal sign (=). Preceding and trailing spaces are ignored also blank lines are ignored. If field value has some any special character(s) then use escape sequence (e.g. For NewLine: \r\n, For Tab: \t, For at (@): \@). When value of any field starts with at sign (@) its automatically treated as File you want to upload. By default file content type is determined based on extension however you can supply content type manually for any field using this way [ YourFileFieldName.Content-Type=some-content-type ]. By default File Upload Field always includes Content-Type in the request (non file fields do not have content-type by default unless you supply manually). For some reason if you dont want to use Content-Type header in your request then supply blank Content-Type to exclude this header altogather [e.g. SomeFieldName.Content-Type= ]. In below example we have supplied Content-Type for file2 and SomeField1, all other fields are using default content-type. See below Example of uploading multiple files along with additional fields. If some API requires you to pass Content-Type: multipart/form-data rather than multipart/form-data then manually set Request Header => Content-Type: multipart/mixed (it must starts with multipart/ else will be ignored). file1=@c:\data\Myfile1.txt file2=@c:\data\Myfile2.json file2.Content-Type=application/json SomeField1=aaaaaaa SomeField1.Content-Type=text/plain SomeField2=12345 SomeFieldWithNewLineAndTab=This is line1\r\nThis is line2\r\nThis is \ttab \ttab \ttab SomeFieldStartingWithAtSign=\@MyTwitterHandle
Filter	Enter filter to extract array from response. Example: $.rows[] --OR-- $.customers[].orders[*]. Check your response document and find out hierarchy you like to extract
Headers	Headers for Request. To enter multiple headers use double pipe (\|\|) or new line after each {header-name}:{value} pair

SQL examples for Zoom Connector

Use these example Zoom SQL queries within SQL Server or any other ODBC-compatible application:

List Users [ Read more... ]

Lists all available Users for organization level

SELECT * FROM Users

Get Settings [ Read more... ]

Get the user settings by by user id

SELECT * FROM UserSettings
WITH(
  UserId='me' -- enter user id or email
)
--You can get UserId by selecting from 'list_users' endpoint and also this value available as dropdown value for UserId parameter.

List Meetings [ Read more... ]

List all the meetings for a selected User

SELECT *  FROM Meetings 
WITH(
  UserId ='me' -- enter user id or email
)
--You can get UserId by selecting from 'list_users' endpoint and also this value available as dropdown value for UserId parameter.

Get Meeting [ Read more... ]

Select a meeting from the list_meetings by providing meeting id

SELECT * FROM Meetings Where id=1234
--You can get id by selecting from 'list_meetings' endpoint and also this value available as dropdown value for MeetingId parameter.

List Meeting Registrants [ Read more... ]

Select a meeting registants for the specific meeting id

SELECT * FROM MeetingRegistrants
WITH(
  MeetingId='1234'
)
--You can get MeetingId by selecting from 'list_meetings' endpoint and also this value available as dropdown value for MeetingId parameter.

List Past Meeting Registrants [ Read more... ]

Select a past meeting registants for the specific meeting id

SELECT * FROM PastMeetingRegistrants
				
			WITH(
					  MeetingId='123456'
				)
				--You can get MeetingId by selecting from 'list_meetings' endpoint and also this value available as dropdown value for MeetingId parameter.

List Registration Questions [ Read more... ]

Select a meeting registants questions for the specific meeting id

SELECT * FROM RegistrationQuestions

				WITH(
					  MeetingId='123456'
				)
				--You can get MeetingId by selecting from 'list_meetings' endpoint and also this value available as dropdown value for MeetingId parameter.

List Webinars [ Read more... ]

Lists all available Webinars for a selected User with webinars access rights

SELECT *  FROM Webinars
				
				WITH(
					  UserId='test' -- enter user id or email
				)
				--You can get UserId by selecting from 'list_users' endpoint and also this value available as dropdown value for UserId parameter.

List Webinar Registrants [ Read more... ]

Select a webinar registants for the specific webinar id

SELECT * FROM [WebinarRegistrants]
					WITH(
				 WebinarId='123456'
				)
				--You can get WebinarId by selecting from 'list_webinars' endpoint and also this value avialable as dropdown value for MeetingId parameter.

Get Webinar [ Read more... ]

Select a webinar from the list_webinars by providing webinar id

SELECT * FROM Webinars Where id=1234
				--You can get id by selecting from 'list_webinars' endpoint and also this value available as dropdown value for WebinarId parameter.

Get Webinar Settings [ Read more... ]

Select a webinar from the list_webinars by providing webinar id

SELECT * FROM WebinarSettings

					WITH(
						  WebinarId='85463711883'
					)
				--You can get WebinarId by selecting from 'list_webinars' endpoint and also this value available as dropdown value for WebinarId parameter.

Download for SSIS Download for SQL Server and ODBC