HaloPSA uses "Applications" to allow API access. We need to create one for Level.

1. Go to Settings > Integrations:

2. Click "HaloPSA API":

3. Take note of the base URL shown below. This will be used as the "HaloPSA URL" when configuring Level:

4. Click "View Applications":

5. This is a list of your existing "Applications". Click "New" in the top-right corner to create an application for Level:

6. Complete the required "Application Name" field with a name of your choice. Select the "Client ID and Secret (Services)" option:

7. Make note of the "Client ID" and "Client Secret" as we will need those when configuring Level.

8. Choose "Agent" for the "Login Type" and select the agent you wish for Level to use.

Note: Halo recommends that you create an "API only" agent for this purpose. This kind of agent won't count against any licenses.

9. Click "Save":

10. Click "Permissions":

11. Select the following permissions:

12. Click "Save" when finished:

1. Go to Settings > Integrations:

2. Click on HaloPSA integration:

3. Complete the three configuration fields:

HaloPSA URL
The URL you use to access your HaloPSA instance. This URL can point to an on-premises or cloud location and should include the appropriate protocol. For example: https://domainhalopsa.com.

Client ID
The value we generated in the previous steps.
​
​Client secret
The value we generated in the previous steps.

4. Click the "Save changes" button:

5. Press "Test connection" to make sure your settings are working:

Level will create assets in HaloPSA based on your group mappings. You can choose any group or subgroup in Level and match it with a company and site combo from HaloPSA.

1. Go to "Group mapping":

2. Click "Add new groups" to select the Level groups to map to HaloPSA sites:

3. Choose one or more groups and click "Add new groups":

4. Choose a HaloPSA company for the first mapping:

5. Select the HaloPSA site:

6. Repeat for every row and click "Save" when finished:

Note: the integration is still disabled, so this won't send any devices yet.

Level can map alerts to HaloPSA tickets. We just need to select which monitor policies should create tickets, as well as which ticket types they should be created as.

1. Click on "Ticketing":

2. Choose HaloPSA ticket types for each policy that you wish to map:

3. When finished, click "Save changes" at the bottom of the page:

Note: the integration is still disabled, so this won't send any alerts yet.

1. Click the "Disabled" toggle:

2. This will immediately begin sending devices and alerts. You can see the group mappings change from "Unsynced" to "Syncing" and eventually to "Synced":

3. If you want to follow the progress, or troubleshoot an issue, navigate to the "Events" tab to see a real-time list of requests being sent to HaloPSA: