Knox Manage 25.07 release notes
Last updated August 5th, 2025
Rate limits in effect
As announced previously, starting with the 25.07 release Knox Manage APIs are subject to rate limits described in the following table:
API endpoint | API purpose | Rate limit quota |
---|---|---|
/emm/oapi/audit/read
|
Read audit | 600 requests/min |
|
Device command | 300 requests/min |
/emm/oapi/
|
All other Knox Manage endpoints | 1800 requests/min |
Any calls made over the allowed rate limits will result in a 429: Too Many Requests
error. You can call the API again after 1 minute.
New APIs to enroll devices via QR code
The following endpoints have been added to allow generating Base64-encoded QR codes for device enrollment:
- For Android:
/oapi/enrollment/selectAndroidEnrollmentQrCode
- For Wear OS:
/oapi/enrollment/selectWearOsEnrollmentQrCode
New iOS activation lock APIs
The following endpoints let you enable and disable the activation lock on iOS devices:
- To enable activation lock:
/mdm/commonOTCServiceWrapper/sendDeviceControlEnableActivationLock
- To disable activation lock:
/mdm/commonOTCServiceWrapper/sendDeviceControlDisableActivationLock
Knox Manage cannot turn on the activation lock if it has been disabled from Apple Business Manager. Only devices activated from Knox Manage can be disabled from Knox Manage.
New API to map a profile to groups
You can call the new /mdm/profileServiceWrapper/assign
endpoint to assign a profile to one or more groups.
New timestamp fields
APIs that include timestamps in their responses now include the following ISO-8601 timestamp fields. We recommend using these fields going forward. Existing timestamp fields have been deprecated.
Type | API | New response field(s) |
---|---|---|
Device |
/emm/oapi/device/selectDeviceAppList
|
stdFormatInstalled
|
|
|
|
|
|
|
Organization |
|
|
|
|
|
User |
|
|
|
|
Deprecations
The following schema fields have been deprecated, and will be removed in a future release:
CreateOrgReqSchema
>properties
>created
Organization
>properties
>created
UpdateOrgReqSchema
>properties
>created
UserEmm
>properties
>created
UserSearchCondition
>properties
>forceAddUserIds
See also
On this page
Is this page helpful?