Zoom Video SDK

Name: Video SDK API
Brand: Video SDK
Availability: InStock

★ Only Publicly Available OpenAPI DocumentIdentity AuthAuthorizationapiKey, oauth236 EndpointsREST

Install Jentic One Beta

Connect the Video SDK to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Video SDK, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzoom.us%2Fvideo-sdk" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fzoom.us%2Fvideo-sdk" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Video SDK API.

Update Bring Your Own Storage settings

Add storage location

List storage location

Storage location detail

GET STARTED

Start building with Video SDK API

Explore with Jentic One

View OpenAPI Document

For Agents

Programmatically update bring your own storage settings, add storage location. Covers 36 operations with apiKey, oauth2 authentication.

Use for: I need to bring your own storage settings, I want to add storage location, Search for storage location, Find all storage location detail

Not supported: Does not handle payments, communications, or crm - use for identity and authentication only.

Use The Video SDK **API Key** and **API Secret** to authorize requests to the Video SDK APIs and [Account Settings APIs](https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#tag/Accounts). Zoom Video SDK APIs use [JSON Web Tokens (JWT)](https://datatracker.ietf.org/doc/html/rfc7519) for authorization. Each request to the Video SDK API must be authorized by an encrypted **Video SDK . The API exposes 36 endpoints secured with apiKey, oauth2 authentication.

Use Cases

Patterns agents use Video SDK API for, with concrete tasks.

★ Identity and Authentication Operations

Use the Video SDK to perform identity auth operations programmatically. The API provides 36 endpoints covering core functionality including update bring your own storage settings, add storage location, list storage location.

Call PATCH /videosdk/settings/storage to update bring your own storage settings

Automated Videosdk Management

Automate videosdk operations by combining multiple Video SDK endpoints. Agents can add storage location and then list storage location in a single workflow.

Call POST /videosdk/settings/storage/location to add storage location, then verify the result

AI Agent Integration via Jentic

AI agents discover and call Video SDK endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey, oauth2 tokens manually.

Search Jentic for 'update bring your own storage settings', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

36 endpoints — use the video sdk **api key** and **api secret** to authorize requests to the video sdk apis and [account settings apis](https://developers.

METHOD

PATH

DESCRIPTION

PATCH

/videosdk/settings/storage

Update Bring Your Own Storage settings

POST

/videosdk/settings/storage/location

Add storage location

GET

/videosdk/settings/storage/location

List storage location

GET

/videosdk/settings/storage/location/{storageLocationId}

Storage location detail

PATCH

/videosdk/settings/storage/location/{storageLocationId}

Change storage location detail

DELETE

/videosdk/settings/storage/location/{storageLocationId}

Delete storage location detail

GET

/videosdk/recordings

List recordings of an account

GET

/videosdk/sessions/{sessionId}/recordings

List session's recordings

PATCH

/videosdk/settings/storage

Update Bring Your Own Storage settings

POST

/videosdk/settings/storage/location

Add storage location

GET

/videosdk/settings/storage/location

List storage location

GET

/videosdk/settings/storage/location/{storageLocationId}

Storage location detail

PATCH

/videosdk/settings/storage/location/{storageLocationId}

Change storage location detail

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring Zoom Video SDK by hand means handling its Authorization header token or OAuth2 flow, pointing at the api.zoom.us/v2 host, and managing token refresh yourself. Through Jentic you install once, import Zoom Video SDK from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Zoom Video SDK puts the storage location id in the URL path (/videosdk/settings/storage/location/{storageLocationId}), so a rule can pin your agent to one storage location: it can read and patch that location and nothing else. You choose the operations it may call, so destructive ones like deleting a storage location are not included unless you add them.

Credential isolation

Your Zoom Video SDK token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'update bring your own storage settings' or 'list session recordings', and Jentic returns the matching Zoom Video SDK operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Video SDK API through Jentic.

What authentication does the Video SDK use?

The Video SDK uses apiKey, oauth2 authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

Can I update bring your own storage settings with the Video SDK?

Yes. Use the PATCH /videosdk/settings/storage endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the Video SDK?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I update bring your own storage settings through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'update bring your own storage settings'. Jentic returns the matching Video SDK operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

How many endpoints does the Video SDK have?

The Video SDK exposes 36 endpoints covering videosdk operations.

Can I limit what my agent is allowed to do with the Zoom Video SDK API?

Yes. Because you run Jentic One yourself, your own rules decide which Zoom Video SDK operations and credentials the agent may use. Since the API puts the storage location id in the URL path (/videosdk/settings/storage/location/{storageLocationId}), a rule can pin your agent to a single location so it can read and patch that one and nothing else. You pick the operations it may call, so destructive ones like deleting a storage location stay out of reach unless you add them.

Zoom Video SDK

Connect the Video SDK to your agent

Capabilities

Start building with Video SDK API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs