Lifesize
Lifesize is a video conferencing and meeting-room platform — cloud meeting service (Lifesize Cloud), Icon conference-room systems, the Lifesize Share wireless presentation appliance, Phone HD, and the web/desktop/mobile apps — originally founded in Austin, Texas. Lifesize merged with contact-center provider Serenova (CxEngage) in 2020 and was acquired by Enghouse Systems in 2023; the video business now operates as Enghouse Video (Vidyo Inc.) and the Lifesize brand and product line continue under enghousevideo.com/lifesize. The developer surface is an on-device automation API on the Lifesize Icon series: a REST interface and a Lifesize Automation Command Line Interface (CLI) reachable over HTTPS or SSH with administrator credentials, both self-documenting on the device itself, used to read configuration, change system preferences, report call status and statistics, and control calls. Lifesize also runs a hosted cloud service API host and publishes chat (Slack, Microsoft Teams) and calendar (Google Workspace, Microsoft 365) integrations, dated release notes, and an Atlassian-hosted status page.
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 Lifesize the way a machine reads it — 4 machine-readable artifacts across 2 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 — Lifesize scores 31.5/100 (thin), with a separate agent-readiness read of 10/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 Lifesize
Each block below is one kind of artifact we hold for Lifesize. 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 2
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.
Lifesize Icon Automation API
The automation and control interface built into Lifesize Icon video systems (models 300, 400, 450, 500, 600, 700, 800). It exposes a REST method for accessing a set of resources...
Lifesize Cloud API
The hosted service API behind the Lifesize Cloud meeting service, the Lifesize Admin Console, and the web/desktop/mobile applications. The host is live and serves JSON from an A...
Security 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.
Resources
Every other property we hold for Lifesize — 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 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 1
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/lifesize · machine-readable index on apis.io