Device Management
Use this page to inspect and control the device records created by runtime activity.
Who This Is For
- support and operations teams handling device replacement or abuse cases
- developers implementing hardware-bound licensing
- teams debugging activation churn
When To Use This
Use device management when you need an operator-facing view of runtime bindings or you need to reset or blacklist a device record.
How It Works
Runtime binding payloads are normalized into device records. The management API then lets you:
- list devices for a license
- fetch one device
- reset a device
- blacklist a device
Scope split:
- reads use
license:read - reset and blacklist use
device:write
Example
List devices:
bash
curl https://api.licensekit.dev/api/v1/licenses/lic_123/devices \
-H "Authorization: Bearer $LICENSEKIT_TOKEN"Reset a device:
bash
curl -X POST https://api.licensekit.dev/api/v1/licenses/lic_123/devices/dev_123/reset \
-H "Authorization: Bearer $LICENSEKIT_TOKEN"Blacklist a device:
bash
curl -X POST https://api.licensekit.dev/api/v1/licenses/lic_123/devices/dev_123/blacklist \
-H "Authorization: Bearer $LICENSEKIT_TOKEN"Common Mistakes
- using reset when blacklist is the real intention
- blaming device management for unstable client-side fingerprinting
- expecting the runtime client to perform these operator-side actions directly