AirWatch
AirWatch was an enterprise mobility management (EMM) and mobile device management (MDM) company founded in 2003 in Atlanta, Georgia and backed by Accel. It provided cloud-based device, application, content, and email management for enterprise mobile fleets. VMware acquired AirWatch in February 2014 for roughly USD 1.5 billion, folding it into the VMware Workspace ONE Unified Endpoint Management (UEM) platform, and the brand was fully retired. In 2024 VMware End-User Computing (including Workspace ONE) was divested to Omnissa. As an independent brand AirWatch no longer operates a developer portal or public API: airwatch.com now redirects to the Omnissa Workspace ONE UEM product page, and the historical AirWatch REST API lives on as the per-tenant Workspace ONE UEM REST API served from customer *.awmdm.com consoles. This profile is retained as an acquired-company lead in the API Evangelist network.
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.
AirWatch is tracked in the API Evangelist network. This page is the human-readable profile that sits on top of the machine-readable index we maintain at apis.io.
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 — AirWatch scores 6.8/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
Resources
Every other property we hold for AirWatch — 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.
Company 1
The organization behind the API
AirWatch is in the network as a tracked entity. We haven't yet indexed a public API surface for it — when one is published, the artifacts, score, and agent-readiness read will appear here automatically. The source repository is where that profile is built.
← All providers · Data indexed from github.com/api-evangelist/airwatch · machine-readable index on apis.io