Back to top
Home / Knox Deployment Program /

What’s new

Find out what’s new in these releases of the Knox Deployment Program REST APIs:

Knox Deployment Gen 2

November 2020

The following API update was made:

API Update

Delete Devices

PUT /kcs/v1/rp/devices/delete

The server now returns the error RESELLER_CUSTOMER_DEVICE_NOT_FOUND (40000044) in any of the following cases:

  • A reseller tries to delete a device from the wrong customer.
  • A reseller tries to delete a device that doesn't exist in their Reseller Portal account; that is, this reseller did not upload that device.

This behavior is consistent with that of the Knox Deployment Program Gen 1 API.

July 2020

API Update

Get KME Profile Aliases

GET /kcs/v1/rp/profilealias/kme
  • The query parameters resellerId and customerId were moved to the header.
  • A profileId associated with each alias is now returned in the response.

Upload Devices

PUT /kcs/v1/rp/devices/upload 		The ProfileAliasObject was added to the request. This allows you to specify a Knox service for each profile alias name you attach to devices you upload.

June 2020

The Knox Deployment Program APIs have been updated to let resellers automatically assign a Knox Mobile Enrollment profile to a device upon upload. Use the new Get Knox Mobile Enrollment Profile Aliases API to retrieve a list of all alias names registered in Knox Mobile Enrollment for a customer. Then, use the new targetService and profileAliases fields in your Upload Devices request to assign a profile to the registered devices.

New API:

Get KME Profile Aliases

GET /kcs/v1/rp/profilealias/kme

Returns a list of Knox Mobile Enrollment-specific profile aliases for a customer.

March 2019

The Knox Deployment Program APIs Gen2 reference now includes the List Devices API call which lets you view all registered devices in the Knox Deployment Program Portal.

Knox Deployment Gen 2 Beta

January 2019

In Knox Deployment Program APIs Gen2, the Knox Deployment Program APIs have been restructured to simplify your workflow and enhance API authentication security. The Gen1 static API authentication key X-WSM-API-TOKEN has been replaced with an authentication JSON Web Token called x-knox-apitoken. This token expires every 30 minutes, making it more secure than the Gen1 license key. You can find more about the differences between Generations 1 and 2.

Knox Deployment Gen 1

Late 2017

Initial release of Samsung Knox Deployment Program REST APIs. You can find more about this version in the Knox Reseller API guide.

Is this page helpful?