Profanity FilterProfanity Filter API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 1063ms|p50: 967ms|p75: 1127ms|p90: 1318ms|p99: 1701ms

Profanity Filter is a simple tool for filtering out profanity words from a text. It returns the text with the profanity words replaced by placeholders.

The Profanity Filter API provides reliable and fast access to profanity filter data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.

To use Profanity 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/profanityfilter

Code Examples

Here are examples of how to call the Profanity Filter API in different programming languages:

cURL Request
curl -X POST \
  "https://api.apiverve.com/v1/profanityfilter" \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "text": "Today is so damn hot! Why the hell would anyone go outside?",
  "mask": "*"
}'
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/profanityfilter', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "text": "Today is so damn hot! Why the hell would anyone go outside?",
    "mask": "*"
})
});

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 = {
    "text": "Today is so damn hot! Why the hell would anyone go outside?",
    "mask": "*"
}

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

data = response.json()
print(data)
Node.js (Native HTTPS)
const https = require('https');
const url = require('url');

const options = {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
};

const postData = JSON.stringify({
  "text": "Today is so damn hot! Why the hell would anyone go outside?",
  "mask": "*"
});

const req = https.request('https://api.apiverve.com/v1/profanityfilter', options, (res) => {
  let data = '';
  res.on('data', (chunk) => data += chunk);
  res.on('end', () => console.log(JSON.parse(data)));
});

req.write(postData);
req.end();
PHP (cURL)
<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/profanityfilter');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'POST');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'X-API-Key: your_api_key_here',
    'Content-Type: application/json'
]);

curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode({
    'text': 'Today is so damn hot! Why the hell would anyone go outside?',
    'mask': '*'
}));

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

$data = json_decode($response, true);
print_r($data);

?>
Go (net/http)
package main

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

func main() {
    payload := map[string]interface{}{
        "text": "Today is so damn hot! Why the hell would anyone go outside?",
        "mask": "*"
    }

    jsonPayload, _ := json.Marshal(payload)
    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/profanityfilter", 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))
}
Ruby (Net::HTTP)
require 'net/http'
require 'json'

uri = URI('https://api.apiverve.com/v1/profanityfilter')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

payload = {
  "text": "Today is so damn hot! Why the hell would anyone go outside?",
  "mask": "*"
}

request = Net::HTTP::Post.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'

request.body = payload.to_json

response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))
C# (HttpClient)
using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;

class Program
{
    static async Task Main(string[] args)
    {
        using var client = new HttpClient();
        client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");

        var jsonContent = @"{
        ""text"": ""Today is so damn hot! Why the hell would anyone go outside?"",
        ""mask"": ""*""
}";
        var content = new StringContent(jsonContent, Encoding.UTF8, "application/json");

        var response = await client.PostAsync("https://api.apiverve.com/v1/profanityfilter", content);
        response.EnsureSuccessStatusCode();

        var responseBody = await response.Content.ReadAsStringAsync();
        Console.WriteLine(responseBody);
    }
}

Authentication

The Profanity 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 Profanity Filter API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Profanity Filter API:

Filter Profanity

ParameterTypeRequiredDescriptionDefaultExample
textstringrequired
The text to filter profanity words from
-This is a sample text that may contain inappropriate words
maskstringoptional
The mask to replace the profanity words with. Should be a Single Character (e.g., *)
**

Response

The Profanity Filter API returns responses in JSON, XML, YAML, and CSV formats:

Example Responses

JSON Response
200 OK
{
  "status": "ok",
  "error": null,
  "data": {
    "isProfane": true,
    "filteredText": "Today is so **** hot! Why the **** would anyone go outside?",
    "mask": "*",
    "trimmed": false,
    "profaneWords": 2
  }
}
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>
    <isProfane>true</isProfane>
    <filteredText>Today is so **** hot! Why the **** would anyone go outside?</filteredText>
    <mask>*</mask>
    <trimmed>false</trimmed>
    <profaneWords>2</profaneWords>
  </data>
</response>
YAML Response
200 OK
status: ok
error: null
data:
  isProfane: true
  filteredText: Today is so **** hot! Why the **** would anyone go outside?
  mask: '*'
  trimmed: false
  profaneWords: 2
CSV Response
200 OK
keyvalue
isProfanetrue
filteredTextToday is so **** hot! Why the **** would anyone go outside?
mask*
trimmedfalse
profaneWords2

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:

FieldTypeSample ValueDescription
isProfanebooleantrue-
filteredTextstring"Today is so **** hot! Why the **** would anyone go outside?"-
maskstring"*"-
trimmedbooleanfalse-
profaneWordsnumber2-

Headers

Required and optional headers for Profanity Filter API requests:

Header NameRequiredExample ValueDescription
X-API-Keyrequiredyour_api_key_hereYour APIVerve API key. Found in your dashboard under API Keys.
Acceptoptionalapplication/jsonSpecify response format: application/json (default), application/xml, or application/yaml
User-AgentoptionalMyApp/1.0Identifies your application for analytics and debugging purposes
X-Request-IDoptionalreq_123456789Custom request identifier for tracking and debugging requests
Cache-Controloptionalno-cacheControl caching behavior for the request and response

Learn more about request headers →

GraphQL AccessALPHA

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

Test Profanity 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 {
  profanityfilter(
    input: {
      text: "Today is so damn hot! Why the hell would anyone go outside?"
      mask: "*"
    }
  ) {
    isProfane
    filteredText
    mask
    trimmed
    profaneWords
  }
}

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

CORS Support

The Profanity Filter API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call Profanity Filter directly from browser-based applications without proxy servers.

CORS HeaderValueDescription
Access-Control-Allow-Origin*Accepts requests from any origin
Access-Control-Allow-Methods*Accepts any HTTP method
Access-Control-Allow-Headers*Accepts any request headers

Browser Usage: You can call Profanity Filter directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.

Learn more about CORS support →

Rate Limiting

Profanity Filter API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all Profanity Filter users.

PlanRate LimitDescription
Free5 requests/minHard rate limit enforced - exceeding will return 429 errors
StarterNo LimitProduction ready - standard traffic priority
ProNo LimitProduction ready - preferred traffic priority
MegaNo LimitProduction ready - highest traffic priority

Learn more about rate limiting →

Rate Limit Headers

When rate limits apply, each Profanity Filter response includes headers to help you track your usage:

HeaderDescription
X-RateLimit-LimitMaximum number of requests allowed per time window
X-RateLimit-RemainingNumber of requests remaining in the current window
X-RateLimit-ResetUnix timestamp when the rate limit window resets

Handling Rate Limits

Free Plan: When you exceed your rate limit, Profanity Filter returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.

Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.

Best Practices for Profanity Filter:

  • Monitor the rate limit headers to track your Profanity Filter usage (Free plan only)
  • Cache profanity filter responses where appropriate to reduce API calls
  • Upgrade to Pro or Mega for guaranteed no-throttle Profanity Filter performance

Note: Profanity Filter rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using Profanity Filter on Free tier.

Error Codes

The Profanity Filter API uses standard HTTP status codes to indicate success or failure:

CodeMessageDescriptionSolution
200OKRequest successful, data returnedNo action needed - request was successful
400Bad RequestInvalid request parameters or malformed requestCheck required parameters and ensure values match expected formats
401UnauthorizedMissing or invalid API keyInclude x-api-key header with valid API key from dashboard
403ForbiddenAPI key lacks permission or insufficient creditsCheck credit balance in dashboard or upgrade plan
429Too Many RequestsRate limit exceeded (Free: 5 req/min)Implement request throttling or upgrade to paid plan
500Internal Server ErrorServer error occurredRetry request after a few seconds, contact support if persists
503Service UnavailableAPI temporarily unavailableWait and retry, check status page for maintenance updates

Learn more about error handling →

Need help? Contact support with your X-Request-ID for assistance.

Integrate Profanity Filter with SDKs

Get started quickly with official Profanity Filter SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.

Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.

Integrate Profanity Filter with No-Code API Tools

Connect the Profanity Filter API to your favorite automation platform without writing code. Build workflows that leverage profanity filter data across thousands of apps.

All platforms use your same API key to access Profanity Filter. Visit our integrations hub for step-by-step setup guides.

Frequently Asked Questions

How do I get an API key for Profanity 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 Profanity Filter and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does Profanity Filter cost?

Each successful Profanity 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 profanity filter lookups.

Can I use Profanity Filter in production?

The free plan is for testing and development only. For production use of Profanity 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 Profanity Filter from a browser?
Yes! The Profanity 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 Profanity Filter credit limit?

When you reach your monthly credit limit, Profanity 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?