API enhancements: Patch data and granular access controls
Device and site patch details via REST API
Two new REST API v2 endpoints are available: GET /v2/device/{deviceUid}/patches and GET/v2/sites/{siteUid}/patches. These endpoints return full patch metadata for a specific device or site, matching the level of detail currently available in the UI and enabling external systems to retrieve and act on patch data programmatically.
API keys: Security Level and Component Level access restrictions
API keys now support two new permission controls: API Security Level and API Component Level. These settings allow administrators to restrict security levels and component-level resources an API key can access, providing more granular control over API key permissions independent of user Security Level memberships.
One Complete Platform for IT & Security Management
Kaseya 365 is the all-in-one solution for managing, securing, and automating IT. With seamless integrations across critical IT functions, it simplifies operations, strengthens security, and boosts efficiency.
MCP for MSPs: What changes in service delivery
Learn how Model Context Protocol (MCP) changes MSP service delivery, six workflows it impacts, how to approach adoption and which controls to put in place.
Read nowMCP security: Risks, authentication and gateways
Learn about MCP security risks, how authentication should work, what an MCP gateway does and seven steps IT teams can take to adopt MCP safely.
Read nowMCP vs. API: What’s the difference and why it matters
Explore the differences between MCP and APIs, how MCP builds on APIs like the Datto RMM API, and when IT teams and MSPs should use each approach or both.
Read now