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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Webex

Webex Call Monitoring API

The Call Monitoring API from Webex — 7 operation(s) for call monitoring.

Documentation Provider Profile APIs.io OpenAPI GitHub

Webex Call Monitoring API is one of 193 APIs that Webex publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 7 operations across 7 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 1.0.0.

7 operations 7 paths 1 schemas 1 DELETE1 GET5 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, OAuth 2.0, HTTP Bearer, HTTP Bearer
Resource Areas
1

Authentication & Security 5

Webex Call Monitoring API declares 5 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. It accepts HTTP bearer tokens (BEARER_TOKEN_FROM_CI). It accepts HTTP bearer tokens (JWT) (Bearer).

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

Paths & Operations 7

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

Call Monitoring 7
POST
/v1/monitor
Create Monitoring Request
createMonitoringRequest body → 202401403412500503
POST
/v1/monitor/{taskId}/bargeIn
BargeIn Request
bargeInRoute 1 param → 202401403412500503
POST
/v1/monitor/{taskId}/end
End Monitoring Request
endActiveMonitoringRoute 1 param → 202401403412500503
POST
/v1/monitor/{taskId}/hold
Hold Monitoring Request
supervisorHoldMonitoringRoute 1 param → 202401403412500503
POST
/v1/monitor/{taskId}/unhold
Unhold Monitoring Request
supervisorUnHoldMonitoringRoute 1 param → 202401403412500503
GET
/v1/monitor/sessions
Fetch Monitoring Sessions
fetchMonitoringSessionsRoute → 202401403412500503
DELETE
/v1/monitor/{requestId}
Delete Monitoring Request
deleteMonitoringRequestRoute 1 param → 202401403412500503

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is CallMonitoringRequest (9 properties). Each schema is shown below with its type and property counts.

CallMonitoringRequest
object
9 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

webex-call-monitoring-api-openapi.yml Raw ↑

Other APIs Webex publishes across the network.

Webex Address Book API
AE Profile APIs.io
Webex Admin Audit Events API
AE Profile APIs.io
Webex Agent Personal Greeting Files API
AE Profile APIs.io
Webex Agent Summaries API
AE Profile APIs.io
Webex Agent Wellbeing API
AE Profile APIs.io
Webex Agents API
AE Profile APIs.io
Webex AI Feature API
AE Profile APIs.io
Webex API - Domain Management API
AE Profile APIs.io
Webex Archive Users API
AE Profile APIs.io
Webex Attachment Actions API
AE Profile APIs.io
Webex Audio Files API
AE Profile APIs.io
Webex Authorizations API
AE Profile APIs.io
#Call Monitoring
← Back to W APIs
API Details
ID
webex:webex-call-monitoring-api
Docs
https://developer.webex.com/docs/messaging
Provider
Webex
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=webex-call-monitoring-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/webex-call-monitoring-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Webex Call Monitoring 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.