Polycom
Polycom, Inc. was a pioneer of unified communications and video conferencing, known for its RealPresence video collaboration platform, SoundStation conference phones, and Group Series and HDX room video endpoints. Polycom merged with Plantronics in 2018 to form Poly, which HP acquired in 2022; the polycom.com domain now redirects to HP's Poly product line. For developers, Polycom exposed the RealPresence Platform REST API (via the RealPresence Resource Manager and Distributed Media Application, later branded Clariti) along with device REST APIs on its VideoOS endpoints, enabling programmatic conference control, scheduling, provisioning, resource monitoring, and billing integration. Developer resources are now consolidated under HP's Poly developer portal.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles Polycom the way a machine reads it — 2 machine-readable artifacts across 1 API, 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 — Polycom scores 12.3/100 (minimal), with a separate agent-readiness read of 0/100 (human only). 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 Polycom
Each block below is one kind of artifact we hold for Polycom. 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 1
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.
RealPresence Platform REST API
REST API for the Polycom RealPresence Platform (RealPresence Resource Manager / Distributed Media Application, later Poly Clariti). Integrates the platform into business process...
Security Posture 1
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.
Resources
Every other property we hold for Polycom — 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.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Access & Security 1
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Company 1
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/polycom · machine-readable index on apis.io