Content Filter API POST

Content Filter checks URLs against a comprehensive blocklist of 200,000+ domains categorized as ads-malware, fake news, gambling, adult content, or social media. Returns the specific category for blocked domains.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/contentfilter

Verification

Format

No key required to try it. Get a key to use it in your app.

200 OK

{
  "status": "ok",
  "error": null,
  "data": {
    // Content Filter response payload
  }
}

About the Content Filter API

Content Filter uses the StevenBlack hosts project which aggregates blocklists from multiple reputable sources. Each domain is categorized into one of five categories: ads-malware, fakenews, gambling, porn, or social. Updated daily.

What people use it for

Parental Controls: Block inappropriate content for children including adult sites, gambling, and fake news
Workplace Filtering: Keep employees focused by detecting social media and entertainment sites
Safe Browsing Apps: Build family-friendly browsers that warn users about unsafe content
Content Moderation: Screen user-submitted URLs before allowing them on your platform

Ways to call it

One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.

JSON: Default REST response
XML: Markup format
YAML: Human-readable
CSV: Tabular export
GraphQL: Query language
MCP: For AI agents

View all integrations →

Questions.

Common questions about the Content Filter API.

Read the docs →

What does the Content Filter API do?

How do I authenticate Content Filter API requests?

Pass your API key in the x-api-key header over HTTPS. One key works across all 300+ APIVerve APIs — there are no per-endpoint credentials.

How much does the Content Filter API cost?

Each call spends 2 credits from your shared pool. The free tier includes 200 credits every month, and paid plans add more headroom.

How fast is the Content Filter API?

Response time depends on the endpoint — the p50 through p99 latency for this API is published on this page. Requests are served over HTTPS through a global edge network.

What response formats does the Content Filter API support?

JSON by default, plus XML and YAML via the format parameter. GraphQL and an MCP interface for AI agents are available across the catalog.

What HTTP method does the Content Filter API use?

POST over HTTPS, following standard REST conventions with a consistent { status, error, data } response envelope.

Request parameters — POST /v1/contentfilter

Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.

Required

Parameter	Type	Example	Description
`url`Required	string	`https://example-gambling-site.com/play`	The URL or domain to check url

Example request

curl -X POST "https://api.apiverve.com/v1/contentfilter" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"url":"https://www.pornhub.com/video/123"}'

Authentication

Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.

Header	When	Value
`x-api-key`Required	Every request	Your API key. Header names are case-insensitive, so `X-API-Key` is the same header.
`Authorization`Alternate	Instead of the above	`Bearer <key>` — for clients that only expose bearer auth. Resolves to the same account and the same billing.
`content-type`Required	POST body	`application/json`

401 is the only auth verdict

A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.

Response — POST /v1/contentfilter

Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.

Sample response

{
  "status": "ok",
  "error": null,
  "data": {
    "url": "https://www.pornhub.com/video/123",
    "domain": "www.pornhub.com",
    "isBlocked": true,
    "category": "porn",
    "matchedDomain": "pornhub.com",
    "safetyRating": "unsafe"
  }
}

Response fields

Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.

Field	Type	Example	Description
`url`	string	`"https://www.pornhub.com/video/123"`	The full URL that was checked for safety
`domain`	string	`"www.pornhub.com"`	The extracted domain from the URL checked
`isBlocked`	boolean	`true`	Whether the domain appears on blocklist
`category`Premium	string	`"porn"`	Content category: ads-malware, fakenews, gambling, porn, social
`matchedDomain`	string	`"pornhub.com"`	The specific blocklisted domain that matched
`safetyRating`	string	`"unsafe"`	Safety assessment: safe or unsafe

Response headers

Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.

Header	What it carries
`x-api-remaining-credits`	Credits left in the current cycle
`x-api-credits-used`	Credits spent in the current cycle
`x-api-max-credits`	The allowance for the cycle
`x-api-version`	Version of the endpoint that answered

Errors

Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.

Status	Meaning	What to do
`400`	Input was rejected	Read `error`; it names the parameter that has to change.
`401`	Key missing or invalid	Check the header name and the key value.
`403`	Key valid, but not permitted here	A key restriction or an IP allow-list — never a bad key.
`429`	Rate limited, or out of credits	Read `error` to tell them apart, then back off or top up.

What a call costs — 2 credits per call

Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.

Plan	Per month	Credits	Content Filter calls	Per 1,000 calls
Free	Free	200	100	Free
Starter	$29.99	200,000	100,000	$0.30
Pro	$99.99	1,000,000	500,000	$0.20
Mega	$299.99	4,000,000	2,000,000	$0.15

Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.

Compare all pricing tiers →

Call it from cURL — POST /v1/contentfilter

No SDK to install — this is a plain HTTPS call to /v1/contentfilter with your key in the x-api-key header. Swap in a real key and it runs as-is.

cURL

1
2

curl "https://api.apiverve.com/v1/contentfilter" \
  -H "x-api-key: YOUR_API_KEY"

Resources

GitHubapiverve/contentfilter-apiSource, issues and the examples this page is built from.ReferenceContent Filter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/contentfilternpm APIVerve.API.ContentFilterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Node.js — POST /v1/contentfilter

Install the Node.js SDK, then call the Content Filter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — npm

npm install @apiverve/contentfilter

Node.js

const res = await fetch("https://api.apiverve.com/v1/contentfilter", {
  headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);

Resources

npm@apiverve/contentfilterThe published Node.js client, versioned and signed.GitHubapiverve/contentfilter-apiSource, issues and the examples this page is built from.ReferenceContent Filter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

APIVerve.API.ContentFilterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Python — POST /v1/contentfilter

No SDK to install — this is a plain HTTPS call to /v1/contentfilter with your key in the x-api-key header. Swap in a real key and it runs as-is.

Python

import requests

res = requests.get(
    "https://api.apiverve.com/v1/contentfilter",
    headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])

Resources

Also published for

@apiverve/contentfilternpm APIVerve.API.ContentFilterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from C# / .NET — POST /v1/contentfilter

Install the C# / .NET SDK, then call the Content Filter API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.

Install — NuGet

dotnet add package APIVerve.API.ContentFilter

C# / .NET

using var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");

var json = await client.GetStringAsync("https://api.apiverve.com/v1/contentfilter");
Console.WriteLine(json);

Resources

NuGetAPIVerve.API.ContentFilterThe published C# / .NET client, versioned and signed.GitHubapiverve/contentfilter-apiSource, issues and the examples this page is built from.ReferenceContent Filter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/contentfilternpm

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Go — POST /v1/contentfilter

No SDK to install — this is a plain HTTPS call to /v1/contentfilter with your key in the x-api-key header. Swap in a real key and it runs as-is.

req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/contentfilter", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")

res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))

Resources

Also published for

@apiverve/contentfilternpm APIVerve.API.ContentFilterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from PHP — POST /v1/contentfilter

No SDK to install — this is a plain HTTPS call to /v1/contentfilter with your key in the x-api-key header. Swap in a real key and it runs as-is.

PHP

$ch = curl_init("https://api.apiverve.com/v1/contentfilter");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);

$response = curl_exec($ch);
echo $response;

Resources

Also published for

@apiverve/contentfilternpm APIVerve.API.ContentFilterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

Call it from Ruby — POST /v1/contentfilter

No SDK to install — this is a plain HTTPS call to /v1/contentfilter with your key in the x-api-key header. Swap in a real key and it runs as-is.

Ruby

require "net/http"

uri = URI("https://api.apiverve.com/v1/contentfilter")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"

res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.body

Resources

Also published for

@apiverve/contentfilternpm APIVerve.API.ContentFilterNuGet

Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.

All articles →

7 SSL Certificate Problems That Kill TrustExpired certs, mismatched domains, weak encryption. A practical checklist for catching SSL issues before your users do.Read

How to Detect VPN and Proxy UsersIdentify VPN, proxy, and datacenter IPs to prevent fraud and enforce geo-restrictions. Complete tutorial with code examples.Read

Preventing Fake Signups: Registration Fraud GuideLearn how to stop bots and fraudsters while maintaining conversion rates for legitimate users.Read

Content Filter API POST

Try it — live request, no key required

About the Content Filter API

What people use it for

Ways to call it

Other ways to use Content Filter

Questions.

Request parameters — POST /v1/contentfilter

Required

Authentication

Response — POST /v1/contentfilter

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — POST /v1/contentfilter

Resources

Also published for

Call it from Node.js — POST /v1/contentfilter

Resources

Also published for

Call it from Python — POST /v1/contentfilter

Resources

Also published for

Call it from C# / .NET — POST /v1/contentfilter

Resources

Also published for

Call it from Go — POST /v1/contentfilter

Resources

Also published for

Call it from PHP — POST /v1/contentfilter

Resources

Also published for

Call it from Ruby — POST /v1/contentfilter

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Content Filter API

Networking

Related articles

Ready to build with Content Filter? Start with 200 free credits — one key unlocks all 300+ APIs.

Explore the catalog