Profanity Filter API POST

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.

Try it — live request, no key required

Request

POSTapi.apiverve.com/v1/profanityfilter

Verification

Format

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

200 OK

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

About the Profanity Filter API

Profanity Filter works by comparing the text against a predefined list of profanity words and replacing them with a defined mask. The profanity words are updated regularly to ensure accurate filtering.

What people use it for

Content Moderation: Use the Profanity Filter API to filter out profanity words for content moderation. Use the data to maintain a safe and respectful online environment
Chat Applications: Filter chat messages by using the Profanity Filter API to remove profanity words. Use the data to enhance user experience and prevent offensive content
Social Media Platforms: Moderate social media content by using the Profanity Filter API to filter out profanity words. Use the data to protect users from harmful language and maintain community standards
Text Analysis: Analyze text by using the Profanity Filter API to filter out profanity words. Use the data to study language patterns, sentiment analysis, and text classification
Game Moderation: Moderate in-game chat by using the Profanity Filter API to filter out profanity words. Use the data to create a positive gaming environment and prevent toxic behavior

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 →

Other ways to use Profanity Filter

Same data, same APIVerve account, same credit balance — one key works on all of them.

Give it to an AI agentConnect over MCP and your agent calls it as a native tool — Claude, Cursor, ChatGPT.on VerveKit Google Sheets or ExcelA =VERVE() formula fills a column — no script, no export, recalculates in place.on VerveSheets

Questions.

Common questions about the Profanity Filter API.

Read the docs →

What does the Profanity Filter API do?

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.

How do I authenticate Profanity 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 Profanity 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 Profanity 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 Profanity 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 Profanity Filter API use?

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

Request parameters — POST /v1/profanityfilter

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
`text`Required	string	`This is a sample text that may contain inappropriate words`	The text to filter profanity words from

Optional

Parameter	Type	Example	Description
`mask`Optional	string	`*`	The mask to replace the profanity words with. Should be a Single Character (e.g., ) default

Example request

curl -X POST "https://api.apiverve.com/v1/profanityfilter" \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"Today is so damn hot! Why the hell would anyone go outside?","mask":"*"}'

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/profanityfilter

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": {
    "isProfane": true,
    "filteredText": "Today is so **** hot! Why the **** would anyone go outside?",
    "mask": "*",
    "trimmed": false,
    "profaneWords": 2
  }
}

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
`isProfane`	boolean	`true`	Whether the text contained profanity words
`filteredText`	string	`"Today is so ** hot! Why the ** would anyone go outside?"`	The text with profanity words replaced by mask characters
`mask`	string	`"*"`
`trimmed`	boolean	`false`
`profaneWords`Premium	number	`2`	Number of profanity words found and filtered

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

No SDK to install — this is a plain HTTPS call to /v1/profanityfilter 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/profanityfilter" \
  -H "x-api-key: YOUR_API_KEY"

Resources

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

Also published for

@apiverve/profanityfilternpm apiverve-profanityfilterPyPI APIVerve.API.ProfanityFilterNuGet

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/profanityfilter

Install the Node.js SDK, then call the Profanity 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/profanityfilter

Node.js

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

Resources

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

Also published for

apiverve-profanityfilterPyPI APIVerve.API.ProfanityFilterNuGet

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

Call it from Python — POST /v1/profanityfilter

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

Install — PyPI

pip install apiverve-profanityfilter

Python

import requests

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

Resources

PyPIapiverve-profanityfilterThe published Python client, versioned and signed.GitHubapiverve/profanityfilter-apiSource, issues and the examples this page is built from.ReferenceProfanity Filter API docsEvery parameter, every response field, and the errors.ParametersWhat this call acceptsRequired and optional inputs, with example values.

Also published for

@apiverve/profanityfilternpm APIVerve.API.ProfanityFilterNuGet

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/profanityfilter

Install the C# / .NET SDK, then call the Profanity 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.ProfanityFilter

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/profanityfilter");
Console.WriteLine(json);

Resources

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

Also published for

@apiverve/profanityfilternpm apiverve-profanityfilterPyPI

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

Call it from Go — POST /v1/profanityfilter

No SDK to install — this is a plain HTTPS call to /v1/profanityfilter 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/profanityfilter", 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/profanityfilternpm apiverve-profanityfilterPyPI APIVerve.API.ProfanityFilterNuGet

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

Call it from PHP — POST /v1/profanityfilter

No SDK to install — this is a plain HTTPS call to /v1/profanityfilter 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/profanityfilter");
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/profanityfilternpm apiverve-profanityfilterPyPI APIVerve.API.ProfanityFilterNuGet

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

Call it from Ruby — POST /v1/profanityfilter

No SDK to install — this is a plain HTTPS call to /v1/profanityfilter 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/profanityfilter")
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/profanityfilternpm apiverve-profanityfilterPyPI APIVerve.API.ProfanityFilterNuGet

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

Text Processing

View all 45 →

All articles →

7 Content Moderation Mistakes That Sink AppsYour app allows user content. Here are the moderation mistakes that get apps pulled from stores.Read

Why Your Sentiment Analysis Is WrongSentiment analysis is powerful but often misused. Here's how to use sentiment data effectively.Read

Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read

Profanity Filter API POST

Try it — live request, no key required

About the Profanity Filter API

What people use it for

Ways to call it

Other ways to use Profanity Filter

Questions.

Request parameters — POST /v1/profanityfilter

Required

Optional

Authentication

Response — POST /v1/profanityfilter

Response fields

Response headers

Errors

What a call costs — 2 credits per call

Call it from cURL — POST /v1/profanityfilter

Resources

Also published for

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

Resources

Also published for

Call it from Python — POST /v1/profanityfilter

Resources

Also published for

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

Resources

Also published for

Call it from Go — POST /v1/profanityfilter

Resources

Also published for

Call it from PHP — POST /v1/profanityfilter

Resources

Also published for

Call it from Ruby — POST /v1/profanityfilter

Resources

Also published for

Zero-code embed — one snippet, no backend

Changelog — Profanity Filter API

Text Processing

Related articles

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

Explore the catalog