StackTether Support
Menu
All support topics

HaloPSA: prepare a read-only API application

StatusComing soon

Short answer: in HaloPSA, go to Configuration > Integrations > Halo API, click View Applications, then New. Choose the Authentication Method Client ID and Secret (Services), log in as a dedicated API agent (or the application identity) with read-only access, and on the Permissions tab tick only read: permissions. Copy the client ID and client secret.

What you need

  • A HaloPSA admin who can create agents and API applications.
  • Your Halo web address (for example yourcompany.halopsa.com). The Halo API page shows your resource server and authorisation server details.

Step 1: create a dedicated API agent (recommended)

  1. Create a new agent for StackTether only, for example "StackTether API".
  2. Give it a read-only role and access to the teams and departments whose tickets your techs should be able to ask about. Halo limits API answers to what this agent can see, so missing team access shows up as empty results.

Step 2: create the API application

  1. Go to Configuration > Integrations > Halo API and click View Applications.
  2. Click New (top right).
  3. On the Details tab, name the application ("StackTether"), make sure it is enabled, and choose Authentication Method: Client ID and Secret (Services).
  4. Set Login Type to Agent and Agent to log in as to the agent from step 1. Halo also offers Application identity with Identity Roles, which keeps the application's activity separate from agents in Halo's audit logs; if you use it, do not pick sys-all-permissions.
  5. Open the Permissions tab and tick only read permissions for the data StackTether will read: tickets (read:tickets), customers and sites (read:customers), and the read permission for each of assets, contracts, projects and time that your Halo version lists. Leave every edit: and create: permission, and all, unticked.
  6. Save and copy the Client ID and Client Secret into your password manager. Halo does not show the secret again; generating a new secret stops the old one.

Official reference: HaloPSA Guides: Creating API Applications. Your own instance documents every endpoint at https://<your Halo address>/api/swagger.

Rotate and revoke

  • Rotate: generate a new client secret on the application and replace it in StackTether. The old secret stops at once.
  • Revoke: disable or delete the application, or deactivate the API agent.

FAQ

Halo also offers its own MCP server. Is this the same?

No. StackTether uses Halo's normal API with its own read-only, vendor-neutral tools, so your audit log, data rules and prompts stay the same across PSAs.

When will HaloPSA be available?

It is in the first group of new vendors. To be told when it opens, use the contact form.