Skip to main content
The ThreatLocker API tool gives Neo agents direct access to the whole ThreatLocker Portal API — read computers, applications, policies and the audit log, test a requested file, and resolve pending software-approval requests (the “app won’t run” workflow) during ticket resolution.
Automatically enabled when you configure ThreatLocker permissions in your agent workflow. No manual toggle needed.

What It Does

  • Find the pending approval request behind an “app won’t run” ticket, and the computer/application it’s for
  • Get the requested file, ask the computer to upload it when ThreatLocker has no copy, and open it in ThreatLocker’s Testing Environment for a technician
  • Gather the evidence for a decision: hashes, file path, signature, matching applications, file history and the VirusTotal link
  • Approve or reject pending software-approval requests
  • Look up computers, computer groups, check-ins and online status; manage maintenance mode, restarts and agent updates
  • Look up applications and application files ThreatLocker has observed
  • View and edit allowlist / Config Manager / network access policies, and push policy changes to computers
  • Search the unified audit and the system audit, and read reports and Health Center findings
  • Enumerate ThreatLocker organizations to scope a call to a specific customer, create a child organization, and invite a portal user
  • Read an organization’s install key and installer link to deploy ThreatLocker through your RMM

Testing a requested file

ThreatLocker’s Testing Environment is a disposable machine where a person runs the file and reads the Risk Center: malware scan, canary files, network, registry, new files. Neo gets the file and opens the Testing Environment for the request, then gives the technician the link and the evidence it gathered. The technician reads the Risk Center results in that window, and Neo prepares the approve or reject decision from what they report. Testing is not available for macOS requests.

Permission Groups

Each group has an access level: Disabled, Read Only, or Read/Write. The install key is a secret that installs ThreatLocker into that organization, so Neo hides it from the agent’s run log and never hands it to a sandbox script.

Access Profiles

Every group Read Only except Agent Deployment, which stays off. Agent can look up any resource but cannot modify or act on approval requests.
Approval Requests and File Testing at Read/Write, with technician approval on every write. Everything else Read Only, and Agent Deployment off — enough to test and resolve the “app blocked” workflow without touching computers, applications, or policies directly.
Every group at Read/Write. Approving or rejecting software, editing policies and file testing run autonomously; Computers, Applications and Organizations writes require technician approval.
Maintenance mode, disabling protection and override codes still wait on a technician. Every other write runs autonomously, approving software and editing policies included.

Safety Controls

How to Configure

1

Connect ThreatLocker

Connect your ThreatLocker Portal API credentials in the Neo Dashboard under the Endpoint Security integrations category.
2

Configure permissions

On the agent’s Tools & Settings tab, click Endpoint Security and expand the ThreatLocker block. Pick one of its Presets, which are the access profiles above, or set each permission group yourself.
3

Set approval requirements

Decide per group which writes wait on a technician, Approval Requests and Policies included. To keep every allow or reject decision behind a technician, turn on approval for Approval Requests and Policies.
Start with Read Only or Helpdesk and expand once you’re confident in the agent’s triage.