Profanity Filter API
Overview
To use Profanity Filter, you need an API key. You can get one by creating a free account and visiting your dashboard.
POST Endpoint
https://api.apiverve.com/v1/profanityfilterExample
How to call the Profanity Filter API in different programming languages.
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": "*"
}'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);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)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))
}{
"status": "ok",
"error": null,
"data": {
"isProfane": true,
"filteredText": "Today is so **** hot! Why the **** would anyone go outside?",
"mask": "*",
"trimmed": false,
"profaneWords": 2
}
}Authentication
The Profanity Filter API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive 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
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
text | string | required | The text to filter profanity words from | - | |
mask | string | optional | 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. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?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>
status: ok
error: null
data:
isProfane: true
filteredText: Today is so **** hot! Why the **** would anyone go outside?
mask: '*'
trimmed: false
profaneWords: 2
| key | value |
|---|---|
| isProfane | true |
| filteredText | Today is so **** hot! Why the **** would anyone go outside? |
| mask | * |
| trimmed | false |
| profaneWords | 2 |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains 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:
| Field | Type | Sample Value | Description |
|---|---|---|---|
isProfane | boolean | - | |
filteredText | string | - | |
mask | string | - | |
trimmed | boolean | - | |
profaneWords | number | - |
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 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.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
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 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
Profanity 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 Profanity 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 Profanity Filter
Official Profanity Filter packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Profanity 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 Profanity Filter?
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?
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.








