Zoom | Operate As Docs

Website: zoom.us
Connects by: Signing in with Zoom
Category: Calendars and meetings
Services: 1
Tools: 365

Service	Key	Base URL
Zoom	`zoom`	`https://api.zoom.us/v2`

Connecting

Your client presses Connect on their link and approves on Zoom's own screen. Operate As never sees their password.

Check they're connected

curl https://api.operate.as/v1/me/clients \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl https://api.operate.as/v1/me/clients \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

[
  {
    "id": "6f1c2a7e-...",
    "name": "Miller Dental",
    "services": [
      "zoom"
    ]
  }
]

[  {    "id": "6f1c2a7e-...",    "name": "Miller Dental",    "services": [      "zoom"    ]  }]

Permissions

What the client reads	Permission it asks for
See and schedule your meetings, and get their recordings	Chosen on the provider's screen
See and manage your Zoom Phone users, calls and recordings	Chosen on the provider's screen
See and send your Zoom Team Chat messages	Chosen on the provider's screen
See and manage your Zoom Rooms	Chosen on the provider's screen
See and manage your Zoom Contact Center	Chosen on the provider's screen
See and manage your Zoom whiteboards	Chosen on the provider's screen
See and manage your Zoom Scheduler bookings	Chosen on the provider's screen

Tools

Install Zoom's typed package for your language:

pip install operate-as-zoom

pip install operate-as-zoom

Run zoom.account

curl -X POST https://api.operate.as/v1/actions/zoom.account \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "clientId": "6f1c2a7e-...",
    "input": {
      "account_id": "<account_id>"
    }
  }'

curl -X POST https://api.operate.as/v1/actions/zoom.account \  -H "Authorization: Bearer $OPERATE_AS_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "clientId": "6f1c2a7e-...",    "input": {      "account_id": "<account_id>"    }  }'

Shows the required inputs. Every input, with its JSON Schema: GET /v1/actions/zoom.account

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

Pass-through

Paths continue from https://api.zoom.us/v2. Your Operate As key goes in Authorization; the client's access is added for you.

See Pass-through requests for the full request and response format.

Call any endpoint

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../zoom/..." \
  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

curl "https://api.operate.as/v1/clients/6f1c2a7e-.../zoom/..." \  -H "Authorization: Bearer $OPERATE_AS_API_KEY"

Response

{
  "status": 200,
  "data": {
    "…": "the service's own response"
  },
  "encoding": "json"
}

{  "status": 200,  "data": {    "…": "the service's own response"  },  "encoding": "json"}

When access ends

Operate As renews the sign-in before it runs out and checks it daily. If Zoom refuses to renew it, the service shows Expired, you're alerted, and your client reconnects from the same link.

See Keeping access alive and Removing access.

Calls answer

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "detail": "Miller Dental's Zoom access ended. Send them their link to reconnect."
}

HTTP/1.1 409 ConflictContent-Type: application/json{  "detail": "Miller Dental's Zoom access ended. Send them their link to reconnect."}

Your webhook receives

{
  "id": "evt_3f9a1c…",
  "type": "connection.expired",
  "createdAt": "2026-10-16T08:00:00+00:00",
  "data": {
    "clientId": "6f1c2a7e-...",
    "clientName": "Miller Dental",
    "provider": "zoom",
    "services": [
      "zoom"
    ],
    "reconnectUrl": "https://…"
  }
}

{  "id": "evt_3f9a1c…",  "type": "connection.expired",  "createdAt": "2026-10-16T08:00:00+00:00",  "data": {    "clientId": "6f1c2a7e-...",    "clientName": "Miller Dental",    "provider": "zoom",    "services": [      "zoom"    ],    "reconnectUrl": "https://…"  }}