{
  "schema": "aaes/capability-pack/1",
  "provider": "zoom",
  "version": "1.0.0",
  "description": "Zoom API v2 with Server-to-Server OAuth: read users, meetings and recordings; create, update and delete meetings; delete meeting recordings.",
  "notes": "The endpoint host 'zoom-api.invalid' is a reserved non-production placeholder (an RFC 2606 reserved TLD): substitute the Zoom API host (api.zoom.us) before enabling, in every endpoint, in the resource locator and in every egress allowlist entry. The allowlist matches exactly, so endpoints and allowlist must be substituted together, and substitution is a required deployment step — the reserved host being allowlisted does not make an unsubstituted pack safe to enable.\n\nThis pack registers only API v2 operations the retrieved Zoom developer documentation establishes: listing users, listing a user's meetings, creating, updating and deleting a meeting, listing a user's cloud recordings, and deleting a meeting's recording files. USER_ID and MEETING_ID in the endpoint paths are placeholders the deployment binds before enabling. The API's 'me' keyword is not registered guidance here: under Server-to-Server OAuth the token is an account-level credential, not an ordinary token-owner user session, so bind a concrete user ID.\n\nZoom enforces the Server-to-Server OAuth app's scopes and admin role on every call, so a capability works only if the app carries the matching scope (for example cloud_recording:delete:meeting_recording:admin for recording deletion); the registration records the endpoint, not Zoom's authorization decision.\n\nDocumented exclusions — this pack does not register: user provisioning and deprovisioning (POST /v2/users and DELETE /v2/users/{userId} — creating or deleting account members is an identity-lifecycle surface requiring its own review); webinar APIs; meeting registrant add/remove; live-meeting control and in-meeting operations; the recording download URLs themselves (downloading recording content is a bulk-content read, not registered); the meeting/webinar archiving endpoints (FINRA compliance archiving, admin-only and support-enabled); archive file deletion (DELETE /past_meetings/{meetingUUID}/archive_files exists in the reviewed documentation and is deliberately not registered); Zoom Phone, Team Chat messaging, and account settings or role management.\n\nThe legacy JWT app type is retired by Zoom; this pack describes Server-to-Server OAuth only.",
  "credential": {
    "secret_ref_id": "secret-ref-zoom-s2s-oauth",
    "custody": "customer_vault",
    "inject": "header",
    "inject_name": "Authorization",
    "note": "A Zoom Server-to-Server OAuth access token, externally minted, held in the client's own secret manager. This reference defines ONE stored value and nothing else: the complete Authorization header value (scheme included), 'Bearer ' followed by the access token. The app's account ID, client ID and client secret are NOT stored under this reference — they belong under separate credential references that only the deployment's custody job may resolve.\n\nZoom's documented flow is two-legged OAuth: the custody job POSTs to the token endpoint with grant_type=account_credentials and a Basic Authorization header built from the client ID and secret, receiving a bearer access token with a one-hour TTL (3600 seconds) and no refresh token; it stores the resulting 'Bearer <token>' value under this reference and re-runs the exchange before the hour expires. The HTTP injector injects the stored value verbatim and performs no OAuth itself — there is no execution-time derivation option.\n\nPer the reviewed documentation: multiple access tokens can be generated without invalidating previous ones — issuing a new token does NOT revoke an older one — and whether a per-token revocation path exists is not established by the reviewed documentation, so an already-issued token must be treated as valid for up to its full hour. Deactivating or deleting the app is the documented cut-off path — tokens stop working when the app is deactivated — but the exact interaction between deactivation and an in-flight token's remaining lifetime is unspecified in the retrieved docs, so treat every issued token as live for its full hour; deactivation is an app-level cut-off, not a per-token control — on suspected exposure, deactivate the app AND treat any already-issued token as live for up to its remaining hour.\n\nLeast privilege: create a dedicated Server-to-Server OAuth app per integration, grant only the scopes these capabilities require (user read, meeting read/write, cloud recording read, and recording delete only if the delete capability is enabled), and keep the app owner's own permissions minimal since scopes are authorized against them.\n\nExecutor hygiene: the client secret and derived tokens must live only in executor memory for the lifetime of a call, must never be written to logs, traces or diagnostics, and must not appear in crash dumps; a deployment that cannot meet that bar must not enable the pack."
  },
  "capabilities": [
    {
      "capability_id": "zoom.users.read",
      "version": "1.0.0",
      "kind": "tool",
      "risk_tier": "R0",
      "owner": "REPLACE-WITH-ACCOUNTABLE-HUMAN",
      "data_class": "pii",
      "egress_allowlist": [
        "zoom-api.invalid"
      ],
      "endpoint": "https://zoom-api.invalid/v2/users",
      "method": "GET",
      "connector": "http",
      "custody": "customer_vault",
      "secret_ref_id": "secret-ref-zoom-s2s-oauth",
      "inject": "header",
      "inject_name": "Authorization",
      "actions": [
        "read"
      ],
      "resource_id": "zoom-account",
      "description": "List the users on the account; this pack registers the collection read only — single-user reads (GET /v2/users/{userId}) are not registered. User records carry names, email addresses and user IDs, which are personal data, so the read is classified as pii (personal data).\n\nThe host is a reserved placeholder: substitute the Zoom API host before enabling.",
      "requires_review": true
    },
    {
      "capability_id": "zoom.meetings.read",
      "version": "1.0.0",
      "kind": "tool",
      "risk_tier": "R0",
      "owner": "REPLACE-WITH-ACCOUNTABLE-HUMAN",
      "data_class": "internal",
      "egress_allowlist": [
        "zoom-api.invalid"
      ],
      "endpoint": "https://zoom-api.invalid/v2/users/USER_ID/meetings",
      "method": "GET",
      "connector": "http",
      "custody": "customer_vault",
      "secret_ref_id": "secret-ref-zoom-s2s-oauth",
      "inject": "header",
      "inject_name": "Authorization",
      "actions": [
        "read"
      ],
      "resource_id": "zoom-account",
      "description": "List one user's meetings (scheduled, live and upcoming); this pack registers the collection read only — single-meeting reads (GET /v2/meetings/{meetingId}) are not registered. Meeting topics, times and join metadata are the organization's schedule content, classified as internal data. USER_ID is a placeholder the deployment binds before enabling.",
      "requires_review": true
    },
    {
      "capability_id": "zoom.meeting.create",
      "version": "1.0.0",
      "kind": "tool",
      "risk_tier": "R3",
      "owner": "REPLACE-WITH-ACCOUNTABLE-HUMAN",
      "data_class": "internal",
      "egress_allowlist": [
        "zoom-api.invalid"
      ],
      "endpoint": "https://zoom-api.invalid/v2/users/USER_ID/meetings",
      "method": "POST",
      "connector": "http",
      "custody": "customer_vault",
      "secret_ref_id": "secret-ref-zoom-s2s-oauth",
      "inject": "header",
      "inject_name": "Authorization",
      "actions": [
        "create",
        "send"
      ],
      "resource_id": "zoom-account",
      "description": "Schedule a meeting for one user. The unrestricted body can set join-before-host, auto-recording, alternative hosts, and other meeting settings. Enforce any narrower limits separately; Zoom settings and app scopes also constrain requests.\n\nInvitation delivery and alternative-host assignments can email named recipients. Because those messages cannot be recalled, the capability declares create and send at R3.\n\nOn supported AAES-mediated execution paths, send requires approval by an authorized person; this does not prevent calls through bypass or observation-only paths. Bind USER_ID before enabling.",
      "requires_review": true
    },
    {
      "capability_id": "zoom.meeting.update",
      "version": "1.0.0",
      "kind": "tool",
      "risk_tier": "R3",
      "owner": "REPLACE-WITH-ACCOUNTABLE-HUMAN",
      "data_class": "internal",
      "egress_allowlist": [
        "zoom-api.invalid"
      ],
      "endpoint": "https://zoom-api.invalid/v2/meetings/MEETING_ID",
      "method": "PATCH",
      "connector": "http",
      "custody": "customer_vault",
      "secret_ref_id": "secret-ref-zoom-s2s-oauth",
      "inject": "header",
      "inject_name": "Authorization",
      "actions": [
        "update",
        "send"
      ],
      "resource_id": "zoom-account",
      "description": "Update a meeting's topic, time, settings, agenda, or other fields. The unrestricted body can reschedule the meeting or change security settings, affecting everyone already invited.\n\nChanges to invitation-relevant fields (time, topic, or settings) can send update notifications that cannot be recalled. Treat every update as potentially notifying. The capability therefore declares update and send at R3.\n\nOn supported AAES-mediated execution paths, send requires approval by an authorized person; this does not prevent calls through bypass or observation-only paths. Bind MEETING_ID before enabling.",
      "requires_review": true
    },
    {
      "capability_id": "zoom.meeting.delete",
      "version": "1.0.0",
      "kind": "tool",
      "risk_tier": "R3",
      "owner": "REPLACE-WITH-ACCOUNTABLE-HUMAN",
      "data_class": "internal",
      "egress_allowlist": [
        "zoom-api.invalid"
      ],
      "endpoint": "https://zoom-api.invalid/v2/meetings/MEETING_ID",
      "method": "DELETE",
      "connector": "http",
      "custody": "customer_vault",
      "secret_ref_id": "secret-ref-zoom-s2s-oauth",
      "inject": "header",
      "inject_name": "Authorization",
      "actions": [
        "delete",
        "send"
      ],
      "resource_id": "zoom-account",
      "description": "Delete one meeting. Deleting a scheduled meeting invalidates its join links and, where configured, sends cancellation notices to invitees — a cancellation notice cannot be recalled after delivery — so the capability is registered as delete and send at the minimum R3 tier; delete and send are designated actions requiring human approval.\n\nOn supported AAES-mediated execution paths, irreversible actions require approval by an authorized person; this does not prevent calls through bypass or observation-only paths. Re-creating a meeting later mints a new meeting ID and new links, not an undo. MEETING_ID is a placeholder the deployment binds before enabling.",
      "requires_review": true
    },
    {
      "capability_id": "zoom.recordings.read",
      "version": "1.0.0",
      "kind": "tool",
      "risk_tier": "R0",
      "owner": "REPLACE-WITH-ACCOUNTABLE-HUMAN",
      "data_class": "pii",
      "egress_allowlist": [
        "zoom-api.invalid"
      ],
      "endpoint": "https://zoom-api.invalid/v2/users/USER_ID/recordings",
      "method": "GET",
      "connector": "http",
      "custody": "customer_vault",
      "secret_ref_id": "secret-ref-zoom-s2s-oauth",
      "inject": "header",
      "inject_name": "Authorization",
      "actions": [
        "read"
      ],
      "resource_id": "zoom-account",
      "description": "List one user's cloud recordings across their meetings, with the documented date-range paging; this pack registers the collection read only — per-meeting recording detail (GET /v2/meetings/{meetingId}/recordings) is not registered. Recording metadata names who met, when, and about what, and exposes play URLs, classified as pii (personal data); downloading the recording files themselves is deliberately not registered (see the pack notes). USER_ID is a placeholder the deployment binds before enabling.",
      "requires_review": true
    },
    {
      "capability_id": "zoom.recording.delete",
      "version": "1.0.0",
      "kind": "tool",
      "risk_tier": "R3",
      "owner": "REPLACE-WITH-ACCOUNTABLE-HUMAN",
      "data_class": "pii",
      "egress_allowlist": [
        "zoom-api.invalid"
      ],
      "endpoint": "https://zoom-api.invalid/v2/meetings/MEETING_ID/recordings",
      "method": "DELETE",
      "connector": "http",
      "custody": "customer_vault",
      "secret_ref_id": "secret-ref-zoom-s2s-oauth",
      "inject": "header",
      "inject_name": "Authorization",
      "actions": [
        "delete"
      ],
      "resource_id": "zoom-account",
      "description": "Delete all recording files for a meeting or webinar. These may include compliance records. The reviewed documentation prevents deletion of recordings selected for a simulive webinar but establishes no general recovery path through this endpoint.\n\nZoom's console has a recording trash. The reviewed reference does not establish whether this API call uses it or permanently deletes the files. Treat deletion as permanent and make no recovery assumption. Registered as delete at R3.\n\nOn supported AAES-mediated execution paths, delete requires approval by an authorized person; this does not prevent calls through bypass or observation-only paths. The Server-to-Server OAuth app needs a recording-delete scope, such as cloud_recording:delete:meeting_recording:admin. Bind MEETING_ID before enabling.",
      "requires_review": true
    }
  ],
  "resources": [
    {
      "resource_id": "zoom-account",
      "kind": "api",
      "locator": "https://zoom-api.invalid/v2",
      "data_class": "pii",
      "owner": "REPLACE-WITH-ACCOUNTABLE-HUMAN"
    }
  ],
  "review": {
    "state": "library",
    "date": "2026-09-22",
    "sources": [
      "https://developers.zoom.us/docs/api/meetings/ (retrieved 2026-09-21)",
      "https://developers.zoom.us/docs/api/users/ (retrieved 2026-09-21)",
      "https://developers.zoom.us/docs/internal-apps/s2s-oauth/ (retrieved 2026-09-21)"
    ],
    "reviewer_id": "aaes-eng"
  }
}