Skip to main content

​
Prerequisites

In Halo ITSM, you need an API application configured with the Client Credentials grant type. To create one:
  1. Log in to your Halo ITSM instance
  2. Navigate to Configuration > Integrations > HaloPSA API > View Applications
  3. Click New to create an application
  4. Set Authentication Method to Client ID and Secret (Services)
  5. Set Login Type to Agent and set Agent to Application Identity
  6. Under Identity Roles, select IT Agent
  7. Grant the application access to the following scopes: read:tickets, edit:tickets, read:customers
  8. Copy the Client ID and Client Secret
  9. Save the application

​
Connect Wirespeed to Halo ITSM

  1. Log in to Wirespeed and navigate to Integrations > Add Integration
  2. Select Halo ITSM and click Integrate
  3. Fill in the following fields:
    • Halo Instance URL — the base URL of your Halo instance (e.g. https://yourcompany.halopsa.com)
    • Client ID — from the API application created above
    • Client Secret — from the API application created above
  4. Click Save
Wirespeed will verify the credentials by checking access to Teams, Ticket Types, and Categories. If any check fails, the integration will not be enabled — double-check the credentials and scopes.

​
Configure Ticket Behavior

After enabling the integration, click Configure to set ticket creation preferences: Click Save when done.

​
Add a Webhook

To have Wirespeed automatically close cases when a ticket is resolved in Halo and sync notes back, set up a webhook:
  1. Log in to Wirespeed and navigate to Integrations > select your Halo ITSM integration > Configure
  2. Copy the Webhook URL and the Webhook Secret
  3. Log in to your Halo ITSM instance
  4. Navigate to Configuration > Integrations > Webhooks
  5. Click New to create a webhook
  6. Paste the Webhook URL from Step 2
  7. Set Authentication to Sign Request Body with a Secret Key
  8. Set the Secret to the Webhook Secret from Step 2
  9. Configure the signature header name as x-signature and set the Signing Algorithm to SHA-256
    Halo’s Signing Algorithm dropdown also offers RSA-SHA256 and other RSA variants. Do not select one of these — Wirespeed cannot verify RSA-signed requests, and every webhook call will fail with a 400 error until the algorithm is changed back to SHA-256.
  10. Add the following Request Headers to the signature, in this exact order:
    1. content-length
    2. content-type
    3. host
    4. x-halo-date
    All four headers are required. Omitting any of them invalidates the HMAC and Wirespeed returns 400. Halo’s Version field is ignored by Wirespeed. Leave the default; it does not affect signature verification.
  11. Under Events, add Ticket Updated by Agent. In Edit criteria, set:
    • Rule Type: Contains (comma separated value)
    • Summary: Wirespeed:, WSPD-, DTN-
  12. Add Ticket Updated by User with the same Edit criteria values
  13. Save the webhook
The webhook secret is required. Wirespeed verifies the x-signature header using HMAC-SHA256, keyed with the Webhook Secret from Step 2. Halo includes x-halo-date in that signature; Wirespeed also rejects callbacks whose x-halo-date is missing, unparseable, or more than 5 minutes off the server clock.Halo should compute the signature from this canonical string:
The resulting HMAC-SHA256 digest should be base64-encoded and sent in the x-signature header.

​
How It Works

  • When a Wirespeed case or detection triggers, a ticket is created in Halo as an Incident with priority mapped from severity (Critical → P1, High → P2, Medium → P3, Low/Info → P4).
  • When a ticket is closed in Halo (status ID 9), the corresponding Wirespeed case is automatically closed.
  • Notes added to a ticket in Halo are synced back to the Wirespeed case timeline.
  • Comments added to a Wirespeed case or one of its detections are posted to the linked Halo ticket.