API Data Synchronization Failure or Pending in Halo Integration

The Halo integration with MSPbots shows API data synchronization has failed or is in Pending status. When this occurs, check if you have configured the correct login type for the API application. This guide shows how to set the correct login type for the API application and configure the login account, etc.

What's on this page:

Issue Description

After establishing a successful Halo Integration with MSPbots, clients encounter API data synchronization failure or experience cases where the data is in Pending status.

The error messages are as follows: 

403: Forbidden error indicates lack of permission to access.
"/Appointment : 403:Forbidden"
"/Tickets : 403:Forbidden"

This issue occurs because the Agent's login type is incorrectly set resulting in insufficient permissions and data synchronization failure. To resolve this, clients need to set the correct login type for the Agent.

Prerequisites

Before proceeding, ensure successful Halo integration and authorization. These steps can only be performed by admins and may only affect Halo users.

Resolution

To set up the Agent with the correct login type

1. On the Add an Application screen of Halo PSA, select Agent for the Login Type. 
2. Then select Administrator for Agent to log in as. 
   
   
   
   
3. Set the minimum permission to read:tickets. Other permissions can be added according to needs. For more information, refer to the HaloPSA guide on Setting up an API Agent. 
   
   

Related Topic

• Page:
  Halo Integration Setup
• Page:
  NextTicket Manager for Halo
• Page:
  Halo Public Datasets