The filter uses natural language processing (NLP) to decode the content into logical words ignoring punctuation, case, formatting, etc. We also apply word transformations to detect obfuscation of bad words like repeating characters, spurious whitespace, and special characters. As well as detection and extraction of bad words you can also use this API to censor bad words from the supplied text.
The API will receive a string text or a URL and it will return a list of all the bad words recognized. Also, you can select a character that will be replacing these bad words. It could be an asterisk or a different word of your choice.
This API is ideal for those users that want to filter any content that has bad words in it. It could be an article by your content creators that you want to upload on your site. Maybe you want to extract text from a blog or post and want to avoid bad words.
This API is excellent for those who want to maintain a bad-words-free environment on their site. Prevent users from setting any offensive nicknames, if you have an integrated chat on your site, avoid toxicity with ease with this API. Censor any bad behavior right away!
Besides API call limitations per month, there are no other limitations. Do not worry about characters.
Pass any URL of a post or article you want to check its content for bad words.
It also receives text strings directly. Check and censor, if you want, any bad words found in the texts.
You can select a "censor-character" that will be shown instead of the censorable word detected. You will be one step ahead!
Also, you can choose a "catalog":
Content Filter - Endpoint Features
| Object | Description |
|---|---|
content |
[Required] The URL or text string that will be checked and filtered. |
censor-character |
Optional Insert any character that will be shown instead of the bad word detected. |
catalog |
Optional Strict or Obscene. Use the one that fits the most your current objectives. |
{"censored-content":"**** you","is-bad":true,"bad-words-list":["fuck"],"bad-words-total":1}
curl --location --request POST 'https://zylalabs.com/api/58/bad+words+filter+api/136/content+filter?content=Isthisabadword?&censor-character=*&catalog=strict' --header 'Authorization: Bearer YOUR_API_KEY'
| Header | Description |
|---|---|
Authorization
|
[Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed. |
No long-term commitment. Upgrade, downgrade, or cancel anytime. Free Trial includes up to 50 requests.
The Content Filter endpoint returns a JSON object containing the censored content, a boolean indicating if bad words were found, a list of identified bad words, and the total count of bad words detected.
The key fields in the response data include "censored-content" (the text with bad words replaced), "is-bad" (true/false if bad words were found), "bad-words-list" (array of detected bad words), and "bad-words-total" (count of bad words).
Users can pass a text string or a URL to the endpoint. Additionally, they can specify a "censor-character" for replacing bad words and choose a "catalog" type (strict or obscene) to customize the filtering.
The response data is structured as a JSON object. It includes fields for the censored content, a boolean for detection status, a list of bad words, and a total count, making it easy to parse and utilize in applications.
The endpoint provides information on detected bad words, the censored version of the input text, and categorization of the bad words based on the selected catalog (strict or obscene).
Users can display the "censored-content" to maintain a safe environment, analyze the "bad-words-list" for moderation purposes, and use "bad-words-total" for reporting or logging bad behavior.
The API employs natural language processing (NLP) techniques to accurately detect and censor bad words, including handling obfuscation methods like repeated characters and special symbols, ensuring high-quality filtering.
Common use cases include filtering user-generated content in forums, moderating chat applications, ensuring clean articles for publication, and preventing offensive usernames in online platforms.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
Service Level:
100%
Response Time:
5,657ms
Service Level:
100%
Response Time:
264ms
Service Level:
100%
Response Time:
332ms
Service Level:
100%
Response Time:
10,171ms
Service Level:
100%
Response Time:
301ms
Service Level:
100%
Response Time:
185ms
Service Level:
100%
Response Time:
5,059ms
Service Level:
100%
Response Time:
255ms
Service Level:
100%
Response Time:
324ms
Service Level:
100%
Response Time:
152ms
Service Level:
100%
Response Time:
4,163ms
Service Level:
100%
Response Time:
727ms
Service Level:
100%
Response Time:
1,102ms
Service Level:
100%
Response Time:
6,739ms
Service Level:
100%
Response Time:
28ms
Service Level:
100%
Response Time:
100ms
Service Level:
100%
Response Time:
20ms
Service Level:
100%
Response Time:
4,391ms
Service Level:
100%
Response Time:
3,694ms
Service Level:
100%
Response Time:
50ms