Cisco Collaboration Hybrid Solutions
APIs for Cisco's hybrid collaboration solutions that combine Webex cloud services with on-premises Unified Communications Manager (CUCM), Expressway, and supporting infrastructure. Hybrid Services let an organization keep calling, calendaring, and identity on-premises while using Webex for meetings, messaging, devices, and management.
Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.
API Evangelist profiles Cisco Collaboration Hybrid Solutions the way a machine reads it — 20 machine-readable artifacts across 12 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Cisco Collaboration Hybrid Solutions scores 38.6/100 (thin), with a separate agent-readiness read of 48/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile Cisco Collaboration Hybrid Solutions
Each block below is one kind of artifact we hold for Cisco Collaboration Hybrid Solutions. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 12
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Webex Meetings API
Schedule, list, update, and cancel Webex meetings; manage participants, recordings, transcripts, and meeting templates.
Webex Hybrid Services API
Manage Webex Hybrid Calendar, Hybrid Call Service, Hybrid Message, Video Mesh nodes, and other connectors that bridge on-premises collaboration infrastructure to the Webex cloud.
Webex Calling API
Cloud calling capabilities including call control, dial plans, voicemail, voice portals, queues, hunt groups, and number provisioning.
Control Hub API
Administer Webex organizations, users, licenses, audit events, and service settings programmatically.
Webex Devices API
Manage and control Webex Room and Desk Devices including remote configuration, status queries, and the device-side xAPI.
Webex Events API
Create and manage Webex Webinars and large-format virtual events, including registration, panelists, and analytics.
Cisco Collaboration Hybrid Solutions Devices API
The Devices API from Cisco Collaboration Hybrid Solutions — 1 operation(s) for devices.
Cisco Collaboration Hybrid Solutions Memberships API
The Memberships API from Cisco Collaboration Hybrid Solutions — 2 operation(s) for memberships.
Cisco Collaboration Hybrid Solutions Messages API
The Messages API from Cisco Collaboration Hybrid Solutions — 2 operation(s) for messages.
Cisco Collaboration Hybrid Solutions Rooms API
The Rooms API from Cisco Collaboration Hybrid Solutions — 2 operation(s) for rooms.
Cisco Collaboration Hybrid Solutions Teams API
The Teams API from Cisco Collaboration Hybrid Solutions — 2 operation(s) for teams.
Cisco Collaboration Hybrid Solutions Webhooks API
The Webhooks API from Cisco Collaboration Hybrid Solutions — 2 operation(s) for webhooks.
Scroll within the panel for all 12 ·
Open Collections 1
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Cisco Webex Platform API (Collaboration Hybrid Solutions)
OPEN COLLECTIONPricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
FinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Semantic Vocabularies 1
JSON-LD contexts give the data shared meaning across APIs. We profile them because semantics are what let a machine reconcile 'customer' here with 'customer' somewhere else.
JSON-LD contexts and semantic vocabularies used across these APIs.
Cisco Collaboration Context
JSON-LDSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for Cisco Collaboration Hybrid Solutions — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 2
Authentication, authorization, and security posture
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/cisco-collaboration-hybrid-solutions · machine-readable index on apis.io