Webex Meetings REST API expects:

• joinBeforeHostMinutes – integer minutes users may join early; 900 s ÷ 60 = 15.

• durationMinutes – length in minutes; 30 meets the 30-minute requirement.

• timeZone – an IANA TZ string; “America/LosAngeles” is the Pacific-US zone.

Option B alone supplies

"joinBeforeHostMinutes": 15,

"durationMinutes": 30,

"timeZone": "America/LosAngeles",

thereby satisfying all three conditions exactly.

1. Cisco Systems

“Webex Meetings API – Create a Meeting

” Request Body Parameter table

rows ‘joinBeforeHostMinutes’

‘durationMinutes’

‘timeZone’. https://developer.webex.com/docs/api/v1/meetings/create-a-meeting

2. Cisco DevNet Learning Lab “Schedule Meetings with the Webex REST API

” Step 3: Define joinBeforeHostMinutes and durationMinutes (Lab ID COLLAB-WEBEX-REST-05).

To automate provisioning you must:

1) POST /teams → creates the parent team (Teams API, “Create a Team”).

2) POST /team/memberships → adds users to that team (Team-Memberships API, “Create a Team Membership”).

3) POST /rooms with teamId → creates a room that belongs to the team (Rooms API, “Create a Room”).

4) POST /memberships → adds users to the new room (Memberships API, “Create a Membership”).

This sequence both “creates” and “populates” the team and its room, satisfying the requirement.

A. Uses /memberships for team population (should be /team/memberships) and omits room population.

B. /people only lists or creates accounts, not team membership; omits room population.

C. Creates team and room but never adds users to the room, leaving it unpopulated.

1. Cisco Webex REST API – Teams: “Create a Team”

https://developer.webex.com/docs/api/v1/teams (Section: Create a Team

para 1).

2. Cisco Webex REST API – Team Memberships: “Create a Team Membership”

https://developer.webex.com/docs/api/v1/team-memberships (Section: Create a Team Membership

para 1).

3. Cisco Webex REST API – Rooms: “Create a Room”

https://developer.webex.com/docs/api/v1/rooms (Section: Create a Room

para 1 – note teamId field).

4. Cisco Webex REST API – Memberships: “Create a Membership”

https://developer.webex.com/docs/api/v1/memberships (Section: Create a Membership

para 1).

In Webex (Teams) OAuth 2.0, a refresh token’s only role is to obtain a fresh access token. The token-refresh request must include the integration’s client ID and client secret; without them the refresh token is unusable. Therefore, the refresh token itself cannot directly perform API operations, and it is time-limited by the platform.

1. Cisco Webex for Developers

“Integrations – Refresh an Access Token”

https://developer.webex.com/docs/integrations (Section: Refresh Access Token) – specifies POST parameters clientid

clientsecret

refreshtoken and notes 90-day/14-day expiry.

2. Cisco DevNet

Developing with Webex APIs (300-920 courseware)

Module “OAuth 2.0 Workflow”

p. 14-15 – describes refresh token usage and required client credentials.

Cisco Webex webhooks accept a filter string made of one or more field/operator/value triplets joined by “&”.

• The only operators allowed are = and !=.

• For message or membership resources the supported fields include roomId and personId.

Therefore a filter beginning with roomId=… or personId!=… is syntactically and semantically valid, while the other strings contain unsupported fields or illegal syntax.

C. spaceId=  No Webex resource recognizes a spaceId field; the API uses roomId or teamId.

D. personId=$spaceId= Contains unsupported field (spaceId) and illegal double “=”.

E. personId=$roomId= Mixes two fields in one term and repeats “=”; not valid syntax.

1. Cisco Webex for Developers

API Reference – “Create a Webhook”

parameter “filter”. States: “Filter functions are of the form fieldName=value or fieldName!=value.” (web page section “Request Body Parameters”

retrieved 2024-08-26).

2. Same page

sub-section “Supported filters by resource”. Lists roomId and personId for messages and memberships resources.

The Webex Meetings XML API returns the listRecording result inside the namespace http://www.webex.com/schemas/2002/06/service/meeting.

To reach each element you must either (a) register that namespace or (b) embed the namespace URI in the search path and, for each recording, extract the two child elements and .

Option A is the only snippet that:

1. registers the Webex meeting namespace,

2. searches for “.//m:recording” within that namespace,

3. retrieves recording.find('m:confName') and recording.find('m:downloadUrl'), and

4. prints them, generating the required name-to-download-URL report.

1. Cisco Webex Meetings XML API Reference Guide

“LstRecording – Response Elements”

pp. 302-304 (confName

downloadUrl; namespace URI).

2. Python 3 Library Reference

xml.etree.ElementTree

“Parsing XML with namespaces”

§19.7.1 – explains need for namespace-qualified tags.