ThreatLocker
ThreatLocker is a Zero Trust endpoint and cloud security platform used by enterprises and managed service providers to enforce least privilege across endpoints, networks, and cloud workloads. Its capabilities include Application Control (allowlisting), Ringfencing, Elevation Control, Storage Control, Network Control / ZTNA, Web Content Control, Patch Management, and ThreatLocker Detect (managed detection and response). The multi-tenant ThreatLocker Portal is exposed programmatically through the PortalAPI — a public OpenAPI 3.0 REST contract covering action logs, applications, approval requests, computers and computer groups, maintenance mode, organizations, policies, reports, saved searches, scheduled agent actions, system audit, tags, upload requests, and agent versions. The platform is deployed as regionally isolated instances (A–H plus AE1, AU1, CA1, EU1, SA1 and a FedRAMP instance), so both the portal and the API are addressed per instance.
Real signal across most facets with visible, nameable gaps — the contract exists but is thin, or the portal is good while governance and commercial terms are absent.
API Evangelist profiles ThreatLocker the way a machine reads it — 44 machine-readable artifacts across 18 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — ThreatLocker scores 53.0/100 (developing), with a separate agent-readiness read of 40/100 (agent ready). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from ThreatLocker's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/threatlocker/"
title="ThreatLocker on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/threatlocker.svg"
alt="ThreatLocker Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/threatlocker/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/threatlocker/"
title="ThreatLocker on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/threatlocker/card.svg"
alt="ThreatLocker Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile ThreatLocker
Each block below is one kind of artifact we hold for ThreatLocker. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 18
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
ThreatLocker Action Log API
The ActionLog API from ThreatLocker — 9 operation(s) for actionlog.
ThreatLocker Application API
The Application API from ThreatLocker — 6 operation(s) for application.
ThreatLocker Approval Request API
The ApprovalRequest API from ThreatLocker — 12 operation(s) for approvalrequest.
ThreatLocker Computer API
The Computer API from ThreatLocker — 21 operation(s) for computer.
ThreatLocker Computer Checkin API
The ComputerCheckin API from ThreatLocker — 1 operation(s) for computercheckin.
ThreatLocker Computer Group API
The ComputerGroup API from ThreatLocker — 4 operation(s) for computergroup.
ThreatLocker Maintenance Mode API
The MaintenanceMode API from ThreatLocker — 4 operation(s) for maintenancemode.
ThreatLocker Online Devices API
The OnlineDevices API from ThreatLocker — 1 operation(s) for onlinedevices.
ThreatLocker Organization API
The Organization API from ThreatLocker — 3 operation(s) for organization.
ThreatLocker Policy API
The Policy API from ThreatLocker — 1 operation(s) for policy.
ThreatLocker Report API
The Report API from ThreatLocker — 2 operation(s) for report.
ThreatLocker Save Search API
The SaveSearch API from ThreatLocker — 3 operation(s) for savesearch.
ThreatLocker Scheduled Agent Action API
The ScheduledAgentAction API from ThreatLocker — 6 operation(s) for scheduledagentaction.
ThreatLocker System Audit API
The SystemAudit API from ThreatLocker — 3 operation(s) for systemaudit.
ThreatLocker Tag API
The Tag API from ThreatLocker — 3 operation(s) for tag.
ThreatLocker Threat Locker Version API
The ThreatLockerVersion API from ThreatLocker — 1 operation(s) for threatlockerversion.
ThreatLocker Upload Request API
The UploadRequest API from ThreatLocker — 2 operation(s) for uploadrequest.
ThreatLocker VDI Hyper V API
The VDIHyperV API from ThreatLocker — 1 operation(s) for vdihyperv.
Scroll within the panel for all 18 ·
Open Collections 20
Open, tool-agnostic collections carry the same runnable value as Postman without locking you to one client — the portable, forkable form of the same exercise.
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
API Collection
OPEN COLLECTIONPortal Action Log API
OPEN COLLECTIONPortal Application API
OPEN COLLECTIONPortal Approval Request API
OPEN COLLECTIONPortal Computer API
OPEN COLLECTIONPortal Computer Checkin API
OPEN COLLECTIONPortal Computer Group API
OPEN COLLECTIONPortal Maintenance Mode API
OPEN COLLECTIONPortal Online Devices API
OPEN COLLECTIONPortal Organization API
OPEN COLLECTIONPortal Policy API
OPEN COLLECTIONPortalAPI
OPEN COLLECTIONPortal Report API
OPEN COLLECTIONPortal Save Search API
OPEN COLLECTIONPortal Scheduled Agent Action API
OPEN COLLECTIONPortal System Audit API
OPEN COLLECTIONPortal Tag API
OPEN COLLECTIONPortal Threat Locker Version API
OPEN COLLECTIONPortal Upload Request API
OPEN COLLECTIONPortal VDI Hyper V API
OPEN COLLECTIONScroll within the panel for all 20 ·
MCP Servers 1
Model Context Protocol servers expose these APIs directly to AI agents. We profile them because agent-native access is the fastest-growing way this provider's capabilities actually get used.
Model Context Protocol servers that expose these APIs to AI agents.
threatlocker-mcp.yml
MCP SERVEREvent Specifications 1
Not every API is request/response. AsyncAPI describes the event-driven and streaming side — the webhooks and channels — so the asynchronous half of the interface is documented the same way the synchronous half is.
AsyncAPI definitions for this provider's event-driven and streaming APIs.
Threatlocker Webhooks
ASYNCAPISecurity Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Agentic Access 1
An x-agentic-access contract marks which operations are safe for an agent to run on its own and which need a human in the loop. It is the difference between an API an agent can use and one it can use safely.
Recommended x-agentic-access execution contracts for AI agents.
Resources
Every other property we hold for ThreatLocker — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 4
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 6
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 5
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 1
Properties that don't map to a standard resource type
← All providers · Data indexed from github.com/api-evangelist/threatlocker · machine-readable index on apis.io
This is an independent, third-party profile of ThreatLocker, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.