Knox Configure 26.10 release notes

Last updated October 8th, 2026

This document is new for the Knox cloud services 26.10 UAT.

On this tab

New

Application and content management endpoints (v2 API)

26.10 introduces the following application management and content management endpoints:

Supported HTTP methods	Endpoint	Description
`GET`, `DELETE`	`/kc/v2/applications`	Retrieves a detailed list of applications, with support for filtering by application ID, name, source (`InHouse` or `GooglePlayStore`), and package name, and sorting by creation time, update time, or package version. Results are paginated. Deletes applications by application ID or package name
`POST`	`/kc/v2/applications/getDetail`	Retrieves detailed application information by application ID or package name, including version history, file size, MD5 checksum, thumbnail URL, and processing status
`POST`	`/kc/v2/applications/googleplayApplications`	Uploads public applications from Google Play Store to Knox Configure. Supports batch upload with per-application success and error reporting
`POST`	`/kc/v2/applications/inhouseApplications`	Uploads in-house APK files to Knox Configure via multipart/form-data. Returns application ID and processing status (InProgress, Deployable, or Failed)
`POST`	`/kc/v2/applications/{applicationId}/downloadUrl`	Generates a temporary download URL for a specific application by application ID
`POST`, `DELETE`	`/kc/v2/contents`	Uploads content files (.jpg, .jpeg, .png, max 50 MB) via multipart/form-data. Deletes content files by content IDs, with support for partial failure reporting (HTTP 207)
`POST`	`/kc/v2/contents/{contentId}/downloadUrl`	Generates a temporary download URL for a specific content file by content ID

OAuth 2.0 scopes for application and content management (v2 API)

The following OAuth 2.0 scopes have been added to support the new Application and Content APIs:

Scope	Description
`kc.application`	Manage all functionality related to Knox Configure applications.
`kc.application:view`	View Knox Configure applications and their information.
`kc.application:manage`	Upload, delete, and manage Knox Configure applications.
`kc.content`	Manage all functionality related to Knox Configure content.
`kc.content:manage`	Upload and delete Knox Configure content files.

Knox Webhook Notification support for device status changes

Knox Configure now integrates with Knox Webhook Notification to send asynchronous notifications when device statuses change. You can subscribe to the KC_DEVICE_STATUS_CHANGE event to receive real-time updates about device state transitions without polling the Get devices endpoint.

For setup instructions, an event payload example, and signature verification, see Knox Webhook Notification for Knox Configure.

Updates

Pagination improvements for retrieving device lists (v1 and v2 APIs)

The Get devices (v1) and Get devices (v2) endpoints now support searchAfter as an alternative to paginating using pageNum.

The nextSearchAfter value returned in the response can be used as the searchAfter value in the next request to retrieve the next page of results, which improves performance for large result sets. You can use pageSize with searchAfter. However, the searchAfter and pageNum parameters are mutually exclusive.

If both are provided in the same request, the API returns a 400 Bad Request error (RESOURCE_INVALID_PARAM).
If neither is provided, pageNum is used, and it defaults to 0.

Improved error responses (v2 API)

The Send command endpoint now returns detailed response bodies for 404 (Device Not Found) and 500 (Internal Server Error) errors, instead of a status code alone.

See Knox Configure API reference v1 and Knox Configure API reference v2 for more information.

Back to release notes

Is this page helpful?