Skip to content
Chinron
Integrations

HaloPSA

HaloPSA's Custom Integrations module can call authenticated REST APIs directly with field mapping and scheduled runs — Chinron is the rare API you can connect without a third-party automation layer in between.

Before you start

Generate an API key in Chinron under MSP Settings → General → API Access. You'll also want the client org UUID or tenant slug for each Halo company you're mapping — get the full list from GET /clients in the interactive docs.

  1. In Halo, go to Configuration → Integrations → Custom Integrations and create a new integration.
  2. Set the base URL to https://au.chinron.io/api/public/v1.
  3. Add an Authorization header of Bearer msp_live_… using your generated key. Store it in Halo's credential vault, not inline in the integration definition.
  4. Import the OpenAPI spec if Halo's version supports spec import — it will pre-populate every endpoint, parameter, and schema.
  5. Map a Halo trigger to a Chinron action. The two you'll use most:
    • New user / contact created → POST /clients/{clientId}/users with the contact's name, email, and department.
    • Offboarding ticket closed → GET /clients/{clientId}/users?email=… to resolve the id, then POST .../deactivate.
  6. Schedule a monthly run against GET /clients/{clientId}/reports/training-summary and .../reports/phishing-summary if you want completion and phishing data flowing into a Halo report or dashboard widget.

Idempotency matters here. User creation is safe to call repeatedly — a duplicate contact sync returns the existing user instead of erroring, so you don't need dedup logic on the Halo side.

Integrations overview Next: ConnectWise PSA