Appearance
Device classes #
Developer inventory is scoped to Device Classes owned by the API key's organisation. A device's current customer organisation can differ from its Device Class owner. Device visibility and remote interaction also respect customer allocation policy and plan entitlement.
Use the device_class reference in developer device responses to group devices by product type. Read linked monitor health through:
text
GET /api/developer/devices/{device_hash}/class-monitoring/Signed-in class management #
GET /api/device-classes/{hash_id}/summary/ requires a signed-in user belonging to the class owner. It is not an organisation API-key endpoint.
Class editing, Software Builds, cohorts, and OS rollout management use their application permissions. Publishing a Product Application version is a separate operation from selecting device Software or an OS image.
The obsolete /api/organisations/{org_hash}/firmware-deployments/ route has been removed. Its per-device assignment did not select the effective Build consumed by current agents. Use current class Builds and cohort pins for Software desired state, and the managed image rollout flow for OS updates.