Hello @mees and @remi,
Thanks for reaching out.
At the moment, Hexnode does not directly link Hexnode device IDs with your internal user IDs. The mapping has to be maintained on your side, by connecting Hexnode device data with your internal database.
That said, you can still achieve your requirement using the approach below.
Recommended workflow:
- Use the Hexnode API to fetch device details.
- From the API response, extract values like:
- device_id
- user_email (or the assigned user identifier available in Hexnode)
- In your internal system, match the retrieved user_email against your internal records and map it to your internal user ID.
Optional (recommended for easier tracking): Add Internal User ID as a Custom Attribute
If you want the internal user ID to be searchable and visible inside Hexnode, you can store it as a Custom Attribute for each device.
This can be populated through:
Once added, it becomes easier to filter/search devices in the portal using that internal ID.
Regarding your app fetching the Hexnode Device ID:
Hexnode doesn’t currently provide a built-in method for an app to directly retrieve the device’s Hexnode device ID from within the device itself.
If you need the app to know an identifier, the best approach is to handle it using app-side logic, using Hexnode’s App Configurations to pass required values (like user ID or a device mapping key) into the app.
Regards,
Eden Pierce
Hexnode UEM