Zoom Integration
Configure Zoom bots with SDK credentials, OBF tokens, and secure credential management in v2
Zoom Integration
Meeting BaaS v2 provides enhanced Zoom integration with secure credential management, improved OBF token handling, and better error tracking.
March 2, 2026 Deadline: Zoom requires OBF tokens for bots joining external meetings. If your bots join meetings hosted by external Zoom accounts, you must implement OBF tokens before this date. See OBF Token Support for details and Zoom's official announcement.
What's New in v2
The v2 API introduces several improvements for Zoom integration:
| Feature | v1 | v2 |
|---|---|---|
| Credential Storage | Separate OAuth connection endpoint | Unified /v2/zoom-credentials API |
| SDK Credentials | Passed with each bot request | Store once, reference by ID |
| Encryption | Basic | AES-256-GCM for secrets and tokens |
| Credential Types | OAuth only | App-only (SDK) and User (OAuth) |
| State Tracking | Limited | Active/Invalid with error tracking |
| Configuration | Multiple top-level params | Single zoom_config object |
Two Approaches
How you integrate with Zoom depends on whose meetings your bots join:
Internal Meetings
Bots join meetings within your Zoom organization. Store SDK credentials once and reference them in bot requests.
External Meetings
Bots join meetings hosted by external accounts. OBF tokens required after March 2, 2026.
Quick Decision Guide
| Your Use Case | What You Need | Documentation |
|---|---|---|
| Recording your team's meetings | App-only credentials | Zoom Credentials |
| Building a product for customers | User credentials with OBF | OBF Token Support |
| Joining meetings hosted by others | OBF tokens | OBF Token Support |
| Already managing OAuth yourself | Direct token or Token URL | OBF Token Support |
The zoom_config Object
In v2, all Zoom-specific configuration is passed in a single zoom_config object:
{
"bot_name": "Recording Bot",
"meeting_url": "https://zoom.us/j/123456789",
"zoom_config": {
"credential_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890"
}
}Available options within zoom_config:
| Parameter | Description |
|---|---|
credential_id | UUID of a stored credential (recommended for most use cases) |
credential_user_id | Look up stored credential by Zoom user ID |
obf_token | Direct OBF token for one-off joins |
obf_token_url | URL that returns an OBF token at join time |
zak_token_url | URL that returns a ZAK token for host-level access |
Pages in This Section
Zoom Credentials
Store and manage Zoom app credentials and OAuth tokens with the credentials API.
OBF Token Support
Implement OBF tokens for external meetings. Covers all integration options.
OAuth Consent Flow
Build an OAuth consent flow for your users to authorize your Zoom app.
Key Concepts
Credential Types
App-only credentials store your Zoom app's SDK credentials (client ID and secret). Use these when your bots only join internal meetings.
User credentials store OAuth tokens for a specific Zoom user who authorized your app. These enable OBF token support for joining external meetings.
Credential States
v2 tracks credential health:
- active: Credential is working and can be used
- invalid: Credential has failed (e.g., tokens revoked, refresh failed)
When a credential becomes invalid, last_error_message and last_error_at provide debugging information.
Security
All credentials are encrypted at rest using AES-256-GCM. Client secrets and OAuth tokens are never returned in API responses—only credential IDs and metadata.
FAQ
Related Resources
- Zoom App Setup — Create a Zoom app in the Marketplace (same for v1 and v2)
- Sending a Bot — Basic bot creation in v2
- Zoom's OBF Blog Post — Official announcement
- Zoom's OBF FAQ — Detailed Q&A from Zoom