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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Malwarebytes

Malwarebytes Content Filtering API

The Content Filtering APIs are for managing content filtering rules used by the DNS module. These rules control what domains or categories of domains your endpoints have access to.

Documentation Provider Profile APIs.io OpenAPI GitHub

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

Tagged areas include Content Filtering. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 34 operations across 26 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.

34 operations 26 paths 0 schemas 2 DELETE16 GET6 POST10 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 Content Filtering 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 34

Across 26 paths, the API surfaces 34 operations — 2 DELETE, 16 GET, 6 POST, 10 PUT. Each is listed below with its method, path, parameters, and response codes.

Content Filtering 34

The Content Filtering APIs are for managing content filtering rules used by the DNS module. These rules control what domains or categories of domains your endpoints have access to.

POST
/nebula/v1/content-filtering
Create content filtering rule
api.nebula.post.content_filtering_rule 2 params body → 200
DELETE
/nebula/v1/content-filtering/{id}
Delete content filtering rule
api.nebula.delete.content_filtering_rule 3 params → 200
GET
/nebula/v1/content-filtering/{id}
Get a content filtering rule details
api.nebula.get.content_filtering_rule.id 3 params → 200
PUT
/nebula/v1/content-filtering/{id}
Update content filtering rule
api.nebula.put.content_filtering_rule 3 params body → 200
PUT
/nebula/v1/content-filtering/{id}/enable
Enable/Disable content filtering rule
api.nebula.enable.content_filtering_rule 2 params body → 200
PUT
/nebula/v1/content-filtering/{id}/enable-for-policy
Enable/Disable content filtering rule for policy
api.nebula.enable.content_filtering_rule.policy 2 params body → 200
GET
/nebula/v1/content-filtering/categories
Get list of categories
api.nebula.get.content_filtering_categories 2 params → 200
POST
/nebula/v1/content-filtering/search
Get a list of content filtering rules
api.nebula.get.content_filtering_rules 2 params body → 200
GET
/nebula/v1/content-filtering/blockpage
Get DNS BlockPage Settings
api.nebula.get.content_filtering_blockpage 3 params → 200
PUT
/nebula/v1/content-filtering/blockpage
Save DNS BlockPage Settings
api.nebula.put.content_filtering_blockpage 3 params body → 200
GET
/nebula/v1/content-filtering/exclusions
Get DNS Global Exclusions
api.nebula.get.content_filtering_exclusions 3 params → 200
PUT
/nebula/v1/content-filtering/exclusions
Save DNS Global Exclusions
api.nebula.put.content_filtering_exclusions 3 params body → 200
GET
/nebula/v1/content-filtering/domain
Get domain details
api.nebula.get.domain 2 params → 200
GET
/nebula/v1/content-filtering/frequent-domains
Get frequently used domain names
api.nebula.get.frequent.domains 2 params → 200
GET
/nebula/v1/content-filtering/policies
Get list of policies
api.nebula.get.content_filtering_rule_policies 2 params → 200
GET
/nebula/v1/content-filtering/tlds
Get Top Level Domains
api.nebula.get.content_filtering_tlds 2 params → 200
POST
/oneview/v1/accounts/{account_id}/content-filtering
Create content filtering rule
api.rmm.post.content_filtering_rule 2 params body → 200
DELETE
/oneview/v1/accounts/{account_id}/content-filtering/{id}
Delete content filtering rule
api.rmm.delete.content_filtering_rule 3 params → 200
GET
/oneview/v1/accounts/{account_id}/content-filtering/{id}
Get a content filtering rule details
api.rmm.get.content_filtering_rule.id 3 params → 200
PUT
/oneview/v1/accounts/{account_id}/content-filtering/{id}
Update content filtering rule
api.rmm.put.content_filtering_rule 3 params body → 200
PUT
/oneview/v1/accounts/{account_id}/content-filtering/{id}/enable
Enable/Disable content filtering rule
api.rmm.enable.content_filtering_rule 3 params body → 200
PUT
/oneview/v1/accounts/{account_id}/content-filtering/{id}/enable-for-policy
Enable/Disable content filtering rule for policy
api.rmm.enable.content_filtering_rule.policy 3 params body → 200
GET
/oneview/v1/accounts/{account_id}/content-filtering/categories
Get list of categories
api.rmm.get.content_filtering_categories 2 params → 200
POST
/oneview/v1/content-filtering
Get a list of content filtering rules
api.rmm.get.content_filtering_rules 1 param body → 200
GET
/oneview/v1/accounts/{account_id}/content-filtering/blockpage
Get DNS BlockPage Settings
api.rmm.get.content_filtering_blockpage 3 params → 200
PUT
/oneview/v1/accounts/{account_id}/content-filtering/blockpage
Save DNS BlockPage Settings
api.rmm.put.content_filtering_blockpage 2 params body → 200
GET
/oneview/v1/accounts/{account_id}/content-filtering/exclusions
Get DNS Global Exclusions
api.rmm.get.content_filtering_exclusions 3 params → 200
PUT
/oneview/v1/accounts/{account_id}/content-filtering/exclusions
Save DNS Global Exclusions
api.rmm.put.content_filtering_exclusions 2 params body → 200
GET
/oneview/v1/accounts/{account_id}/content-filtering/domain
Get domain details
api.rmm.get.domain 2 params → 200
GET
/oneview/v1/accounts/{account_id}/content-filtering/frequent-domains
Get frequently used domain names
api.rmm.get.frequent.domains 2 params → 200
GET
/oneview/v1/accounts/{account_id}/content-filtering/policies
Get list of policies
api.rmm.get.content_filtering_rule_policies 2 params → 200
GET
/oneview/v1/accounts/{account_id}/content-filtering/tlds
Get Top Level Domains
api.rmm.get.content_filtering_tlds 2 params → 200
POST
/oneview/v1/content-filtering/blockpage
Search DNS blockPages for accounts
api.v2.rmm.search.content_filtering.blockpage 1 param body → 200
POST
/oneview/v1/content-filtering/exclusions
Search DNS global exclusions for accounts
api.v2.rmm.search.content_filtering.exclusions 1 param body → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

malwarebytes-content-filtering-api-openapi.yml Raw ↑

Other APIs Malwarebytes publishes across the network.

Malwarebytes Account API
AE Profile APIs.io
Malwarebytes AI Detection & Response API
AE Profile APIs.io
Malwarebytes App Block API
AE Profile APIs.io
Malwarebytes Assets API
AE Profile APIs.io
Malwarebytes Authentication API
AE Profile APIs.io
Malwarebytes Case Management API
AE Profile APIs.io
Malwarebytes Copilot API
AE Profile APIs.io
Malwarebytes Detections API
AE Profile APIs.io
Malwarebytes Device Control API
AE Profile APIs.io
Malwarebytes DNS API
AE Profile APIs.io
Malwarebytes DNS Logs API
AE Profile APIs.io
Malwarebytes Drive Encryption API
AE Profile APIs.io
#Content Filtering
← Back to M APIs
API Details
ID
malwarebytes:malwarebytes-content-filtering-api
Base URL
https://api.threatdown.com
Docs
https://api.threatdown.com/nebula/v1/docs
Provider
Malwarebytes
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=malwarebytes-content-filtering-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/malwarebytes-content-filtering-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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