Skip to main content

​
Setup Overview

Setting up the Kaseya VSA X integration involves two main steps:

Creating an API Token

Create a Third-Party Token in your VSA X portal with the scopes Neo Agent needs.

Connecting to Neo Agent

Configure the connection between your VSA X tenant and Neo Agent using your Token ID and Token Secret.

​
Prerequisites

Before starting the integration setup, ensure you have:
  • Admin Access: An account in your VSA X tenant with the API Access permission (Super Admin, or a custom role that includes it)
  • Your tenant URL: e.g. https://yourtenant.vsax.net
Kaseya VSA X (also written VSAX) is the modern, cloud-native Kaseya RMM built on the Pulseway engine — distinct from the classic VSA 9/10. Its REST API v3 lives at https://<tenant>.vsax.net/api/v3.

​
What Neo Can Do with VSA X

Neo Agent reads and (where you allow it) writes the VSA X REST API v3 surface, gated by per-area permission groups you configure in Agent Settings.
  • Device lookup — find devices, status, OS type, organization/site/group, applied policies, antivirus status
  • Custom fields & notifications — read device custom fields and notifications
  • Write — move a device to another group, update device custom fields
  • Hardware inventory — BIOS, operating system, CPU, RAM, disks, network adapters
  • Installed software — name, publisher, version per device
  • Last-seen — the true LastSeenOnline timestamp
The assets endpoint is rate-limited by Kaseya to 60 requests/hour, so Neo queries it sparingly.
  • Hierarchy — read and (with write access) manage the organization → site → group structure and their custom fields
  • Catalog — list automation scripts, tasks, and workflows and inspect execution history
  • Execute — run pre-registered scripts on a device and read back the result (with write access to the Automation group)
Script execution runs scripts that already exist in your VSA X dashboard — Neo never submits ad-hoc source. To let Neo run on-prem PowerShell (AD / Exchange) through VSA X, register the Neo wrapper script — see On-prem AD & Exchange setup.
  • Patch management — read patch policies and global rules
  • Endpoint protection — read antivirus policies
  • Notifications — read notifications; create notifications and manage webhooks (with write access)
  • System — read audit logs, environment info, RBAC scopes, custom field definitions
Write access is opt-in per area. In Agent Settings → Permission Groups, set the relevant VSA X groups to Read & Write to enable creates, updates, and deletes.

​
Available Actions

Neo Agent uses the VSA X REST API v3. Make sure your Third-Party Token has the necessary permissions for the areas you want Neo to act in — see the API token guide.