Leap Motion
Leap Motion is the hand-tracking company behind the Leap Motion Controller. It merged with Ultrahaptics in 2019 to form Ultraleap, and the Leap Motion brand now continues as Ultraleap's hardware line (Leap Motion Controller 2) and as the "Leap" naming across the tracking SDK. The developer surface is not a hosted web API: it is LeapC, a native C API that connects a local client to the Ultraleap Hand Tracking Service and delivers tracked hands, digits, bones, images and device events as polled messages, plus first-party plugins for Unity, Unreal, OpenXR and Python. The original leapmotion.com and developer.leapmotion.com domains no longer resolve; docs.ultraleap.com and github.com/ultraleap are the live developer surfaces.
Leap Motion publishes 2 APIs on the APIs.io network. Tagged areas include Company, Hand Tracking, Computer Vision, Spatial Computing, and Augmented Reality.
Leap Motion’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, changelog, sandbox, and 21 more developer resources.
API Rating
APIs
LeapC Tracking API
LeapC is the native C API for Ultraleap / Leap Motion hand tracking. A client opens a LEAP_CONNECTION to the locally running Ultraleap Hand Tracking Service and drives a message...
Ultraleap Tracking WebSocket
An open-source WebSocket server from Ultraleap that restores the LeapJS-compatible websocket surface removed when Leap Motion Orion V4 was replaced by Ultraleap Gemini V5. It st...
Resources
Get Started 3
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 6
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 4
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type