Content FilterContent Filter API

OnlineCredit Usage:1 per callRefreshed 12 hours ago
avg: 120ms|p50: 116ms|p75: 123ms|p90: 132ms|p99: 149ms

Overview

To use Content Filter, you need an API key. You can get one by creating a free account and visiting your dashboard.

POST Endpoint

URL
https://api.apiverve.com/v1/contentfilter

Example

How to call the Content Filter API in different programming languages.

cURL Request
curl -X POST \
  "https://api.apiverve.com/v1/contentfilter" \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "url": "https://www.pornhub.com/video/123"
}'
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/contentfilter', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "url": "https://www.pornhub.com/video/123"
})
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

payload = {
    "url": "https://www.pornhub.com/video/123"
}

response = requests.post('https://api.apiverve.com/v1/contentfilter', headers=headers, json=payload)

data = response.json()
print(data)
Go (net/http)
package main

import (
    "fmt"
    "io"
    "net/http"
    "bytes"
    "encoding/json"
)

func main() {
    payload := map[string]interface{}{
        "url": "https://www.pornhub.com/video/123"
    }

    jsonPayload, _ := json.Marshal(payload)
    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/contentfilter", bytes.NewBuffer(jsonPayload))

    req.Header.Set("X-API-Key", "your_api_key_here")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}
Example 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"
  }
}

Authentication

The Content Filter API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the Content Filter API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Content Filter API:

Check URL Safety

ParameterTypeRequiredDescriptionDefaultExample
urlstringrequired
The URL or domain to check
Format: url (e.g., https://example-gambling-site.com/play)
-https://example-gambling-site.com/play

Response

The Content Filter API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.

Other Response Formats

XML Response
200 OK
<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <url>https://www.pornhub.com/video/123</url>
    <domain>www.pornhub.com</domain>
    <isBlocked>true</isBlocked>
    <category>porn</category>
    <matchedDomain>pornhub.com</matchedDomain>
    <safetyRating>unsafe</safetyRating>
  </data>
</response>
YAML Response
200 OK
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
CSV Response
200 OK
keyvalue
urlhttps://www.pornhub.com/video/123
domainwww.pornhub.com
isBlockedtrue
categoryporn
matchedDomainpornhub.com
safetyRatingunsafe

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains the API response data if successful, otherwise null{...}

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

Response fields marked with Premium are available exclusively on paid plans.View pricing
FieldTypeSample ValueDescription
urlstring"https://www.pornhub.com/video/123"
The full URL that was checked for safety
domainstring"www.pornhub.com"
The extracted domain from the URL checked
isBlockedbooleantrue
Whether the domain appears on blocklist
categoryPremiumstring"porn"
Content category: ads-malware, fakenews, gambling, porn, social
matchedDomainstring"pornhub.com"
The specific blocklisted domain that matched
safetyRatingstring"unsafe"
Safety assessment: safe or unsafe

Headers

Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →

GraphQL AccessALPHA

Access Content Filter through GraphQL to combine it with other API calls in a single request. Query only the content filter data you need with precise field selection, and orchestrate complex data fetching workflows.

Test Content Filter in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  contentfilter(
    input: {
      url: "https://www.pornhub.com/video/123"
    }
  ) {
    url
    domain
    isBlocked
    category
    matchedDomain
    safetyRating
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The Content Filter API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →

Rate Limiting

Content Filter requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →

Error Codes

The Content Filter API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →

SDKs for Content Filter

Official Content Filter packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →

No-Code Integrations

Content Filter works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →

Frequently Asked Questions

How do I get an API key for Content Filter?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for Content Filter and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does Content Filter cost?

Each successful Content Filter API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful content filter lookups.

Can I use Content Filter in production?

The free plan is for testing and development only. For production use of Content Filter, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.

Can I use Content Filter from a browser?
Yes! The Content Filter API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my Content Filter credit limit?

When you reach your monthly credit limit, Content Filter API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?