Kace
KACE is the endpoint and systems management product line from Quest Software, originally founded in 2003 as KACE Networks (backed by Norwest Venture Partners, Sigma Partners, and Focus Ventures), acquired by Dell in 2010, and now sold as Quest KACE. The portfolio centers on the KACE Systems Management Appliance (SMA) for inventory, patching, software distribution, scripting, and service desk; the KACE Systems Deployment Appliance (SDA) for OS imaging and provisioning; and KACE Cloud for mobile device management and modern endpoint management. The KACE SMA ships a REST API (JSON and XML) that lets administrators programmatically manage assets, inventory, managed installations, scripting, users, and service-desk tickets on the customer-hosted appliance. This profile enriches the original Norwest portfolio lead with the real Quest KACE identity and its documented API surface.
Kace publishes 1 API on the APIs.io network. Tagged areas include Company, Endpoint Management, Systems Management, IT Asset Management, and Patch Management.
Kace’s developer surface includes documentation, API reference, support, authentication, and 7 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
KACE Systems Management Appliance (SMA) API
REST API for the KACE Systems Management Appliance. Authenticated KACE SMA users can manage appliance data across the Asset, Inventory, Managed Install, Scripting, User, and Ser...
Security Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Get Started 1
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 2
Pagination, idempotency, versioning, errors, and events
Access & Security 2
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Company 1
The organization behind the API