Enabling the Kaseya Web Services API

NOTE   This information is provided as a service to Autotask users who are implementing the Kaseya Extension. Kaseya problems and questions should be directed to Kaseya Customer Support at support@kaseya.com.

You enable the Kaseya Web Services by selecting the Enable VSA API Web Service check box via the System tab on the Kaseya server.

For Kaseya 5.x and Managed Service Edition - G1:

  1. Select the Kaseya System tab.
  2. On the left side of the System tab, under Server Management, click the Configure link.
  3. Locate the Enable VSA API Web Service check box. If it is clear, click to select.
  4. Continue the implementation of the Autotask Kaseya Extension.

For Kaseya 2 (v. 6 and 7):

  1. In the left navigation menu, click the white Down arrow, then select System.
  2. Under Server Management, click Configure.
  1. Locate the Enable VSA API Web Service check box. If it is clear, click to select.
  2. Continue the implementation of the Autotask Kaseya Extension.

For hosted Kaseya

Contact Kaseya to enable the Kaseya API for Hosted Managed Workplace.

To access the Kaseya monitoring service, you must configure a Kaseya security level that provides the required access rights. Following are step by step instructions to set up a dedicated Kaseya Role and user account with the minimum required access rights for the integration to function.

IMPORTANT  While a user account with full access rights would certainly do the job, for security reasons, we strongly advise against this.

  1. Open the Kaseya application and navigate to the System > User Security > User Roles page.
  2. Click New.
  3. Enter a Role Name.
  4. In the Role Type field, select VSA Admin.
  5. Click Save.
  6. Select the new role on the list of roles and click the Access Rights tab.
  7. Click Set Role Access Rights.
  8. On the page that opens, click Disable All.
  9. Click Collapse All.
  10. Open Root > Kaseya VSA > Audit > Device > View Devices and check View.
  11. Open Root > Kaseys VSA > Audit > Individual Data > Machine Summary and click Machine Status.
  12. Scroll to Root > Kaseya VSA and check Service Desk.
  13. Scroll to Root > Kaseya VSA > System and check User Settings.
  14. At the bottom of the page, click OK.

The role is now configured. The next step is to assign this role to the user account that you will use for the integration. If you are a current user of the integration, assign the new role to the existing user account.

Kaseya is now using access tokens instead of passwords, so the next step is to create an access token.

  1. Navigate to User Security > Users and select the user account you created for the integration.
  2. Click the Access Token tab.
  3. Enter a Token Name.
  4. Enter a date when this token will expire.
  5. Under Scopes Assigned, select REST API.
  6. Click Save. The token is created and displayed this one time. Once you click OK, you cannot return to the dialog window.
  7. Click Copy to Clipboard, then click OK.
  8. In Autotask, open the Admin > Extensions & Integrations > Remote Monitoring / Management Extensions > Kaseya page.
  9. In the Adapter Web Services section, paste the contents of the clipboard into the Token field.
  10. Click Save.

After you save the Kaseya Extension Settings, we recommend that you launch device discovery. If the URL, Username, or Token are not entered correctly, the launch will fail with a message that will help diagnose the issue.

To have the ticket number match with the "ticketreferencing" number in the URL:

In the left pane, go to Ticketing > Email Reader and check the Turn off independent ticket sequence numbering (use identity value) box.

This check box is not available on multi-tenant systems.

Next step

The next step is Setting up Kaseya Device Discovery in Autotask.