What Neo reads — and what it never does
For the report, Neo makes only these read-only calls:/api/Tickets— the list of recent tickets (summary, status, dates, client name)/api/Actions— the ticket notes, for better summaries- Ticket lookups — statuses, priorities, ticket types and categories, so IDs render as names
Creating the read-only API application
1
Create a new API application
Go to Configuration → Integrations → HaloPSA API, click View Applications, then New.
- Application Name:
Neo Free Report - Active: checked
- Authentication Method: Client ID and Secret (Services)
2
Pick the agent to log in as
HaloPSA limits an API application to what its login agent can see. Pick an agent with access to all teams and ticket areas (an administrator-level agent is easiest) — otherwise the report only samples the tickets that agent can see, and the numbers come out low.
3
Grant only the read:tickets permission
Open the Permissions tab and tick read:tickets. Leave every other permission — including all, all:standard and admin — unticked.
4
Enter the details in the report form
Copy the Client ID and Client Secret, then back in the report form enter:
- HaloPSA URL — the web address of your instance, for example
https://yourcompany.halopsa.com - Client ID and Client secret — from the application you just created
