Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In The Halo integration , the with MSPbots shows API data synchronization has failed or is pendingin Pending status. When this occurs,  please 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:

Table of Contents
minLevel2

Issue Description

...

When the customer has successfully connected Halo After establishing a successful Halo Integration with MSPbots, they encountered clients encounter API data synchronization failure or experience cases where the data is pendingin Pending status.

The error messages displayed are as follows: 

...

403:

...

Forbidden

...

error

...

indicates

...

lack

...

of

...

permission

...

to

...

access.

...


"/Appointment

...

:

...

403:Forbidden"

...


"/Tickets

...

:

...

403:Forbidden"

Prerequisites

Halo Integration connected and authorization successful.

Possible Reasons

Due to the customer's failure to correctly set the login type as Agent, there is a lack of access permissions, resulting in data synchronization failure.

Applications and Permissions

This issue may be encountered by all users using Halo integration. Only administrators can set the login type.

Resolution

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

    image set up agent in HaloImage Added

  3. Set the minimum permission to read:tickets. Other permissions can be added according to
  4. Please set the Login Type as Agent and set Agent to log in as to Administrator in Details when configuring Add an Application.
    Image Removed
  5. Set the minimum permission as "read:tickets" and other permissions can be added based on actual needs. For more information, please refer to this article: https://halopsa.com/guides/article/?kbid=1566.

Related Topic

...

  1. refer to the HaloPSA guide on Setting up an API Agent

Related Topic

...

Content by Label
showLabelsfalse
max5
showSpacefalse
excludeCurrenttrue
cqllabel = "halo"