For the complete documentation index, see llms.txt. This page is also available as Markdown.

ThreatLocker

Connection Requirements

1 - Domain

The Portal API host of your ThreatLocker instance, without the scheme. Take the instance code from your portal URL and prefix it with portalapi.: a portal at portal.ae1.threatlocker.com uses portalapi.ae1.threatlocker.com.

2 - API Key

The token of a ThreatLocker API User. It is sent as-is in the Authorization header. The token renews itself on every use, so it only expires after a period of inactivity.

You can follow the steps below.

  1. In the ThreatLocker Portal, navigate to Manage > Users > API Users.

  2. Create a new API User and assign it a role that has the View Computers permission for the organization you want to discover.

  3. Choose an expiration period and copy the generated token. It is only shown once.

3 - Organization ID

The GUID of the organization whose devices will be collected. It is sent as the ManagedOrganizationId header. Devices of child organizations are included automatically, so for MSP tenants use the parent organization. You can find the GUID in the portal URL after switching into the organization.

4 - Override Organization ID

Optional. Sent as the OverrideManagedOrganizationId header only when filled. Leave it empty unless ThreatLocker support asks you to set it.

5 - Proxy

Proxy URL (optional).

6 - Timeout

The amount of time (in seconds) to wait for API responses. (default: 30)

Last updated

Was this helpful?