Skip to content
English
  • There are no suggestions because the search field is empty.

HaloPSA Integration Guide

A step-by-step guide to getting HaloPSA connected

Here are the minimum requirements for on-premise environments.

  1. Fully Chained SSL Certificate.
  2. The latest stable version of HaloPSA.
  3. If your Halo instance restricts access based on IP, our IPs are 3.19.3.152 &  3.19.4.238

Note: On-premise users can populate the Tenant field by typing 'Not set'.

Note: Setting All permissions on step 10 will cause authentication to fail.

  1. Within the DNS Filter dashboard, navigate to Organization > PSA Management
  2. Select Data Sources > Integrations
  3. Choose API Authentication > Connect 
  4. Select HaloPSA and click Next.
  5. You will then be presented with a connection checklist. Please gather these items before progressing to the next page. Let's head over to HaloPSA.

Create Role

Roles can be accessed by navigating to Configurations > Teams and Agents > Roles. You can create a new Role for the Agent you are using, or edit an existing one. Make sure the Role that your Agent will be using has the following permissions:

  1. Clients Access Level - Read Only
  2. Invoices Access Level - Read and Modify
  3. Client Contracts Access Level - Read and Modify
  4. Items Access Level - Read and Modify

Configure Agent

Navigate back to the Configurations page. Now go to Teams & Agents > Agents, and ensure the following permissions are enabled:

  1. Clients Access Level - Read Only
  2. Items Access Level - Read and Modify
  3. Invoices Access Level - Read, Create and Modify
  4. Client Contracts Access Level - Read and Modify

Save the API Application.



Create New Application

Login to HaloPSA.

Navigate to Configuration > Integrations > HaloPSA API > View Applications

Click New in the top right.

On the Details tab, enter an "Application Name" of your choice.

Set the "Authentication Method" to Client ID and Secret (Services) and Record the Client ID and Client Secret. Keep a record of the Client ID and Client Secret.

Set the Login Type to Agent.

Select an Agent to log in as. This must be an Agent who has a Role with appropriate permissions, as outlined in the Configure Agent step later in this guide.

Press Save.

On the Permissions tab, enable the following permissions:

  1. Read: Customers
  2. Read and edit: Contracts
  3. Read and edit: Items
  4. Read and edit: Invoices

 

Finish Connection

Within Halo PSA, navigate to Configuration > Integrations > HaloPSA API

Record the Resource Server, Authorization Server and Tenant.

Return to DNSFilter, select HaloPSA and insert the following information:

  1. Client ID
  2. Client Secret
  3. Resource Server
  4. Authorization Server
  5. Tenant (On-premise users can populate the Tenant field by typing in the words Not set)

Select Save and Test to confirm that the integration is configured properly. The wizard will run the initial sync, which may take a few minutes, before asking you to continue to your dashboard.

        Warning: Authorization Server requires a forward slash "/" at the end of the URL https://domain.halopsa.com/auth/

        Congratulations, you've successfully connected your PSA!

        If you do not have any active recurring agreements in your PSA, the integration cannot go to an active state.  You can try again as soon as there are active agreements with usage, usually after the 1st of the month.