Automate

Zoom exposes a rich set of JSON-based Web APIs, as well as a powerful Search & Execute automation framework. In addition Zoom also comes with a Zapier app that supports built-in integration with 1000+ of Zapier compatible app.

Before venturing into these APIs & frameworks, please review our terminology first:

Terminology

	Term	Explanation
	API User	An API user in Zoom that takes up a desktop license. The API user needs to login and establish a session before invoking any further APIs.
	Zoom Repository	Instance of a Zoom server that stores the users files in the cloud or on-premises.
	Role	A group of users with a specific set of permissions.
	Project Vault	A group of folders & files with a common set of permissions.
	Asset ID	Any file or folder stored in Zoom gets assigned a unique number, “Asset ID”. Even if an asset is renamed or moved, the Asset ID stays the same, allowing you to query metadata or perform operations by just specifying the asset ID. Often 3rd party integrations use our Asset ID to tie an asset in another system with Zoom.
	Check-in or Ingest	Importing new files and folders or checking-in new versions of existing assets to Zoom.
	Check-out or Export	Exporting an asset from the Zoom repository to a destination.
	Revision	Modified version of an asset stored using Zoom’s patented de-duplication technology.
	High-res or External asset	Read-only raw media such as high-res audio/video clips or raw images that have a proxy stored in Zoom repository.
	Direct asset	Assets that have revisions such as images or project files.
	API Server	An optional Docker container or server that hosts the API end-point, to allow clean separation between the user generated requests and automation driven calls. This can significantly improve security policy enforcement.