How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Malwarebytes Endpoints API

## Endpoints IntroductionAn Endpoint is a device which has the ThreatDown Endpoint Agent installed. Currently, there are available Endpoint Agents for Windows, macOS, and Linux. Refer to the installation guide for more information on registering a new Endpoint.Using the Endpoint API, you can search your registered endpoints and retrieve their last known status. The API allows you to perform advanced queries and offers grouping capabilities so that you can perform deep analysis of your company's devices and the found threats, such as Detections or Suspicious Activities.You can scan, isolate, remediate, and reboot your endpoints remotely through the Job APIs.## How to deploy an endpoint agent**Endpoint software can be installed in the following ways**:- Active Directory (AD) Group Policy- System Center Configuration Manager (SCCM)- Third-party deployment tools- Manually on the endpoints- Discovery & Deployment ToolOnce the installation is complete, the endpoints will be displayed in the console.You can retrieve installers for your account through the `Installers` APIs.

Malwarebytes Endpoints API is one of 52 APIs that Malwarebytes publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 47 operations across 43 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.threatdown.com.

47 operations 43 paths 0 schemas 4 DELETE25 GET12 POST6 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.threatdown.com
Authentication
OAuth 2.0, HTTP Bearer
Resource Areas
1

Authentication & Security 2

Malwarebytes Endpoints API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (client_credentials) using the clientCredentials flow, exposing 3 scopes. It accepts HTTP bearer tokens (user_permissions).

Paths & Operations 47

Across 43 paths, the API surfaces 47 operations — 4 DELETE, 25 GET, 12 POST, 6 PUT. Each is listed below with its method, path, parameters, and response codes.

Endpoints 47

Endpoints Introduction An Endpoint is a device which has the ThreatDown Endpoint Agent installed. Currently, there are available Endpoint Agents for Windows, macOS, and Linux. Ref…

DELETE
/nebula/v1/endpoints/{id}
Delete a machine
api.v2.nebula.delete.endpoint 3 params body → 200
GET
/nebula/v1/endpoints/{id}
Get endpoint
api.v2.nebula.get.endpoint.id 4 params → 200
DELETE
/nebula/v1/endpoints
Delete multiple machines
api.v2.nebula.delete.endpoints.bulk 2 params body → 200
POST
/nebula/v1/endpoints
Search endpoints
api.v2.nebula.post.endpoints 2 params body → 200
POST
/nebula/v1/endpoints/export
Export endpoints
api.v1.nebula.post.export 2 params body → 200
POST
/nebula/v1/endpoints/export/async
Export endpoints asynchronously
api.v1.nebula.post.export.async 2 params body → 200
GET
/nebula/v1/endpoints/{id}/agent_info
Get endpoint agent info
api.v2.nebula.get.endpoint.id.agent_info 3 params → 200
GET
/nebula/v1/endpoints/{id}/assets
Get endpoint assets
api.v2.nebula.get.endpoint.id.assets 3 params → 200
GET
/nebula/v1/endpoints/{id}/drives
Get endpoint drives
api.nebula.get.endpoint.id.drives 3 params → 200
GET
/nebula/v1/endpoints/{id}/network
Network information
api.v2.nebula.get.endpoint.id.network 3 params → 200
GET
/nebula/v1/endpoints/{id}/sa
All suspicious activity of an endpoint
api.nebula.endpoint.id.sa 8 params → 200
GET
/nebula/v1/endpoints/{id}/sa/{sa_id}/exclusions
Specific suspicious activity of an endpoint
api.nebula.endpoint.id.sa.id.exclusion 4 params → 200
POST
/nebula/v1/endpoints/{id}/sa/{sa_id}/remediate
Remediate suspicious activity of an endpoint
api.nebula.endpoint.id.sa.sa_id.remediate 4 params → 201
GET
/nebula/v1/endpoints/{id}/scans/{scan_id}
Get a scan of an endpoint
api.nebula.get.endpoint.id.scans.id 5 params → 200
GET
/nebula/v1/endpoints/{id}/scans
Get scans of an endpoint
api.nebula.get.endpoint.id.scans 8 params → 200
GET
/nebula/v1/endpoints/{id}/scans/{scan_id}/detections
Get the detections of a scan
api.nebula.get.endpoint.id.scans.id.detections 6 params → 200
GET
/nebula/v1/endpoints/{id}/status
Endpoint status
api.v2.rmm.get.endpoint.id.status 3 params → 200
GET
/nebula/v1/endpoints/{id}/diag-log
Get diagnostic logs of an endpoint
api.nebula.get.endpoint.id.diag-log 3 params → 200
GET
/nebula/v1/endpoints/{id}/quarantine
Get quarantined items
api.nebula.get.quarantine 9 params → 200
POST
/nebula/v1/endpoints/{id}/drives/{volume_id}/reveal
Reveal drive recovery key
api.nebula.post.endpoint.id.drives.volume_id.reveal 4 params body → 200
PUT
/nebula/v1/endpoints/{id}/sa/{sa_id}/close
Close suspicious activity of an endpoint
api.nebula.get.endpoint.id.sa.sa_id.close 4 params → 200
PUT
/nebula/v1/endpoints/{id}/sa/{sa_id}/open
Open suspicious activity of an endpoint
api.nebula.get.endpoint.id.sa.sa_id.open 4 params → 200
PUT
/nebula/v1/endpoints/{id}/tags
Set endpoint tags
api.v2.nebula.put.endpoint.id.tags 3 params body → 200
POST
/nebula/v1/endpoints/search-groupby
Search grouped endpoints
api.nebula.v1.search.endpoints.group 2 params body → 200
DELETE
/oneview/v1/accounts/{account_id}/endpoints/{id}
Delete an endpoint
api.v2.rmm.delete.endpoint 3 params body → 200
GET
/oneview/v1/accounts/{account_id}/endpoints/{id}
Get endpoint
api.v2.rmm.get.endpoint.id 4 params → 200
DELETE
/oneview/v1/endpoints
Delete multiple endpoints across accounts
api.v2.rmm.delete.endpoints.bulk 1 param body → 200
POST
/oneview/v1/endpoints
Search endpoints across accounts
api.v2.rmm.post.endpoints 1 param body → 200
POST
/oneview/v1/endpoints/export
Export endpoints (Bulk across accounts)
api.v2.rmm.post.export 1 param body → 200
POST
/oneview/v1/endpoints/export/async
Export endpoints asynchronously
api.v2.rmm.post.export.async 1 param body → 200
GET
/oneview/v1/accounts/{account_id}/endpoints/{id}/agent_info
Get endpoint agent info
api.v2.rmm.get.endpoint.id.agent_info 3 params → 200
GET
/oneview/v1/accounts/{account_id}/endpoints/{id}/assets
Get endpoint assets
api.v2.rmm.get.endpoint.id.assets 3 params → 200
GET
/oneview/v1/accounts/{account_id}/endpoints/{id}/network
Network information
api.v2.rmm.get.endpoint.id.network 3 params → 200
GET
/oneview/v1/accounts/{account_id}/endpoints/{id}/sa
All suspicious activity of an endpoint
api.rmm.endpoint.id.sa 7 params → 200
GET
/oneview/v1/accounts/{account_id}/endpoints/{id}/sa/{sa_id}/exclusions
Specific suspicious activity of an endpoint
api.rmm.endpoint.id.sa.id.exclusion 3 params → 200
POST
/oneview/v1/accounts/{account_id}/endpoints/{id}/sa/{sa_id}/remediate
Remediate suspicious activity of an endpoint
api.rmm.endpoint.id.sa.sa_id.remediate 3 params → 201
GET
/oneview/v1/accounts/{account_id}/endpoints/{id}/scans/{scan_id}
Get a scan of an endpoint
api.rmm.get.endpoint.id.scans.id 5 params → 200
GET
/oneview/v1/accounts/{account_id}/endpoints/{id}/scans
Get scans of an endpoint
api.rmm.get.endpoint.id.scans 8 params → 200
GET
/oneview/v1/accounts/{account_id}/endpoints/{id}/scans/{scan_id}/detections
Get the detections of a scan
api.rmm.get.endpoint.id.scans.id.detections 6 params → 200
GET
/oneview/v1/accounts/{account_id}/endpoints/{id}/status
Endpoint status
api.v2.rmm.get.endpoint.id.status 3 params → 200
GET
/oneview/v1/accounts/{account_id}/endpoints/{id}/diag-log
Generate a diagnostic log
api.rmm.get.endpoint.id.diag-log 3 params → 200
GET
/oneview/v1/accounts/{account_id}/endpoints/{id}/quarantine
Get quarantined items
api.rmm.get.quarantine 9 params → 200
PUT
/oneview/v1/accounts/{account_id}/endpoints/{id}/sa/{sa_id}/close
Close suspicious activity of an endpoint
api.rmm.get.endpoint.id.sa.sa_id.close 3 params → 200
PUT
/oneview/v1/accounts/{account_id}/endpoints/{id}/sa/{sa_id}/open
Open suspicious activity of an endpoint
api.rmm.get.endpoint.id.sa.sa_id.open 3 params → 200
PUT
/oneview/v1/accounts/{account_id}/endpoints/{id}/tags
Set endpoint tags
api.v2.nebula.rmm.endpoint.id.tags 3 params body → 200
POST
/oneview/v1/accounts/{account_id}/endpoints
Search endpoints
api.v2.rmm.search.account.endpoints 1 param body → 200
POST
/oneview/v1/endpoints/search-groupby
Search grouped endpoints
api.rmm.search.endpoints.group 1 param body → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

malwarebytes-endpoints-api-openapi.yml Raw ↑

Other APIs Malwarebytes publishes across the network.

Malwarebytes Account API
Malwarebytes AI Detection & Response API
Malwarebytes App Block API
Malwarebytes Assets API
Malwarebytes Authentication API
Malwarebytes Case Management API
Malwarebytes Content Filtering API
Malwarebytes Copilot API
Malwarebytes Detections API
Malwarebytes Device Control API
Malwarebytes DNS API
Malwarebytes DNS Logs API
Where this information came from

This is an independent, third-party profile of Malwarebytes Endpoints API, 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.