Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Hexnode UEM (BYOK) — connector documentation

  • MCP endpoint: https://byok-hexnode.connectorbay.com/mcp
  • REST API: POST https://byok-hexnode.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-hexnode.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Hexnode UEM API key (Admin, API, enable API access), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-hexnode.connectorbay.com/health · Tool schemas: https://byok-hexnode.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-hexnode · agent@connectorbay.com

What Hexnode UEM (BYOK) is for

Hexnode UEM (BYOK) lets an AI assistant read your own Hexnode UEM data through the Hexnode UEM API with a key you supply (API key (Admin, API, enable API access)). Read-only: 9 tools (list_devices, get_device, list_device_policies, list_users, list_device_groups, list_user_groups, list_policies, list_apps, list_organizational_units). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to *.hexnodemdm.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Hexnode UEM. Hexnode UEM and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which Hexnode devices are not compliant?"
  • "What are the details of Hexnode device 5?"
  • "Which policies apply to Hexnode device 5?"
  • "How many devices does each Hexnode user have?"
  • "Which device groups exist in Hexnode?"
  • "Which user groups exist in Hexnode?"

What it does

  • list_devices: List enrolled devices with name, model, OS, enrollment status, compliance, serial number, last report time and owner name. Filter by platform, activity or device type.
  • get_device: Get one device's details: platform, enrollment status, last report and scan times, lost mode, hardware model, OS version, storage and battery. Location, phone numbers and IMEI are not returned.
  • list_device_policies: List the policies associated with one device, with policy ID, name and version.
  • list_users: List enrolled users with name, device count and directory domain. Email and phone number are not returned.
  • list_device_groups: List device groups with name, description, type (custom or dynamic), device count and last modification.
  • list_user_groups: List user groups with name, description, user count and last modification.
  • list_policies: List policies with description, version, archived flag, which platforms they are configured for, device count and timestamps.
  • list_apps: List the applications in the Hexnode app inventory with name, identifier, platform, version, vendor, type, license and category.
  • list_organizational_units: List the organizational units of a directory domain with name, parent, description and status.

BYOK key

You bring your own Hexnode UEM API key (Admin, API, enable API access) (https://www.hexnode.com/mobile-device-management/api/setting-up-an-api/authentication/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to *.hexnodemdm.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Hexnode UEM API (*.hexnodemdm.com) with a BYOK key; documentation: https://www.hexnode.com/mobile-device-management/developers/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Hexnode UEM. Hexnode UEM and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Hexnode UEM account.

Built for: Worldwide. Languages: English.