Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Webex Conference Controls API

The Conference Controls API from Webex — 8 operation(s) for conference controls.

Webex Conference Controls API is one of 178 APIs that Webex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Conference Controls. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 10 operations across 8 paths, and defines 4 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.

10 operations 8 paths 4 schemas 1 DELETE1 GET8 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Authentication
OAuth 2.0, HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 3

Webex Conference Controls API declares 3 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow. It accepts HTTP bearer tokens (JWT) (bearer-key). It supports OAuth 2.0 (bearerAuth) using the authorizationCode flow, exposing 1 scope.

  • bearer-key — e.g. Bearer YOURAUTHORIZATIONTOKEN
  • bearerAuth — OAuth 2.0 Bearer token authentication

Paths & Operations 10

Across 8 paths, the API surfaces 10 operations — 1 DELETE, 1 GET, 8 POST. Each is listed below with its method, path, parameters, and response codes.

Conference Controls 10
POST
/telephony/conference
Start Conference
Start Conference body → 204400401403404405409410
DELETE
/telephony/conference
Release Conference
Release Conference 1 param → 204400401403404405409410
GET
/telephony/conference
Get Conference Details
Get Conference Details 1 param → 200400401403404405409410
POST
/telephony/conference/addParticipant
Add Participant
Add Participant body → 204400401403404405409410
POST
/telephony/conference/mute
Mute
Mute body → 204400401403404405409410
POST
/telephony/conference/unmute
Unmute
Unmute body → 204400401403404405409410
POST
/telephony/conference/deafen
Deafen Participant
Deafen Participant body → 204400401403404405409410
POST
/telephony/conference/undeafen
Undeafen Participant
Undeafen Participant body → 204400401403404405409410
POST
/telephony/conference/hold
Hold
Hold 1 param → 204400401403404405409410
POST
/telephony/conference/resume
Resume
Resume 1 param → 204400401403404405409410

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are ConferenceDetails (6 properties), ConferenceParticipant (3 properties). Each schema is shown below with its type and property counts.

ConferenceTypeEnum
string
ConferenceStateEnum
string
connected - The controller is an active participant. held - The controller has held the conference and so is no longer an active participant. disconnected - Th…
ConferenceDetails
object
6 properties 3 required
ConferenceParticipant
object
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

webex-conference-controls-api-openapi.yml Raw ↑

Other APIs Webex publishes across the network.

Webex Address Book API
Webex Admin Audit Events API
Webex Agent Personal Greeting Files API
Webex Agent Summaries API
Webex Agent Wellbeing API
Webex Agents API
Webex AI Feature API
Webex API - Domain Management API
Webex Archive Users API
Webex Attachment Actions API
Webex Audio Files API
Webex Authorizations API