Webhooks
Signed payloads for enrollment, alert, and command events, with automatic delivery retries.
Explore →The full Hive control plane, available as a REST API: devices, groups, policies, apps, commands, and alerts. Authenticate with scoped API keys, wire up webhooks, and ship against the same endpoints our own console uses.
Every action available in the Hive console is also a documented API call: enrolling a device, pushing a policy, queuing a command.
A predictable, resource-oriented API served over HTTPS, returning JSON, and versioned so your integration never breaks under you.
Organisation-scoped API keys for server-to-server calls, and short-lived scoped tokens when you need to delegate narrower access.
Every endpoint follows the same request and response shape, so learning one resource means you already know the rest.
| Resource | Description | Key operations |
|---|---|---|
| Devices | Enrollment state, hardware detail, and live health | list, get, command, delete |
| Groups | Static and dynamic device groupings | list, create, update, delete |
| Policies | Configuration profiles and inheritance | list, get, assign, publish |
| Apps | Managed Play, private, and APK packages | list, upload, assign, rollback |
| Commands | Remote actions queued to a device | create, get, cancel |
| Alerts | Alert rules and triggered incident history | list, get, acknowledge |
Push events out with webhooks, or build directly against the platform with an SDK for the layer you're integrating.
Signed payloads for enrollment, alert, and command events, with automatic delivery retries.
Explore →Embed the Hive agent directly into an OEM image or a custom AOSP build.
Explore →Platform-signed hooks for manufacturers shipping fleet-ready hardware.
Explore →Wire scanners, printers, and payment devices into fleet-wide health monitoring.
Explore →A starter that wires enrollment into your own device-procurement pipeline.
View guide →A reference build polling device state to drive an ops-room display.
View guide →Forward monitoring alerts into a channel your team already watches.
View guide →v1 is the current stable surface. Every change, whether a new endpoint, a new field, or a deprecation, ships to the changelog before it ships to production.