How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
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 193 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.2.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.2.0
API Version
1.0.0
Authentication
OAuth 2.0, HTTP Bearer, HTTP Bearer
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 accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearer-key — e.g. Bearer YOURAUTHORIZATIONTOKEN
  • bearerAuth — e.g. Bearer YOURAUTHORIZATIONTOKEN

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.

ConferenceParticipant
object
3 properties 3 required
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

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
Where this information came from

This is an independent, third-party profile of Webex Conference Controls API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.