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.
Lifesize publishes 2 APIs on the APIs.io network. Tagged areas include Company, Video Conferencing, Communications, Collaboration, and Meetings.
Lifesize’s developer surface includes documentation, API reference, getting-started guide, support, signup flow, changelog, authentication, and 15 more developer resources.
Kin Score
APIs 2
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.
Resources
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