The Profanity Block API is a robust solution designed to analyze text input and identify instances of offensive or inappropriate language. Using state-of-the-art algorithms and an extensive library of profanity words and phrases, the API can accurately detect and filter offensive content in real time.
Essentially, the Profanity Block API scans submitted text for matches against predefined lists of offensive terms and expressions, ensuring that harmful language is filtered out.
In an online world where interactions significantly influence social, professional and personal relationships, the Profanity Block API is an essential tool for promoting positive and respectful communication. By leveraging its advanced features, businesses, developers and online communities can create safer, more inclusive environments where people can interact without encountering inappropriate content. With its accurate profanity detection, real-time processing and seamless integration capabilities, the Profanity Block API helps build online spaces based on mutual respect, professionalism and civility.
To use this endpoint you must enter a text in the parameter.
Filter words - Endpoint Features
| Object | Description |
|---|---|
check_word |
[Required] |
{"total_words_checked":1,"checked_word":"damn","contains_offensive_word":true,"censor_replacement_string":"*","filtering_range":"low","profanities":["damn"],"total_using_low":1,"word_filtered":"da*n"}
curl --location --request GET 'https://zylalabs.com/api/5562/profanity+block+api/7205/filter+words?check_word=damn' --header 'Authorization: Bearer YOUR_API_KEY'
To use this endpoint, you must specify text in the parameter.
["I *** you"]
curl --location --request GET 'https://zylalabs.com/api/5562/profanity+block+api/19636/profanity+detector&text=Required' --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.
To use the API you must specify a text to filter out inappropriate words.
Profanity Block API designed to control and filter offensive language in text-based communications, ensuring a safe and respectful environment.
There are different plans suits everyone including a free trial for small amount of requests, but it’s rate is limit to prevent abuse of the service.
The Profanity Block API is a robust tool designed to monitor and filter offensive language in text-based communications. You would need it to ensure a safe and respectful online environment for your users or customers.
The API uses API keys for authentication. To access the API, include your API key in the request header. The API key is provided upon registration and should be kept secure.
The Filter words endpoint returns a JSON object containing information about the text analyzed, including whether it contains offensive words, the total words checked, and the filtered output.
Key fields in the response include "total_words_checked," "contains_offensive_word," "profanities," and "word_filtered," which provide insights into the analysis results and the specific offensive terms detected.
The primary parameter for the Filter words endpoint is the text input that you want to analyze for offensive language. Users can customize their requests by varying the text submitted.
The response data is organized in a structured JSON format, with key-value pairs that clearly indicate the analysis results, such as the number of words checked and any offensive terms found.
Typical use cases include moderating user-generated content on forums, filtering chat messages in gaming platforms, and ensuring respectful communication in customer service interactions.
Data accuracy is maintained through the use of advanced algorithms and an extensive library of profanity terms, regularly updated to reflect current language trends and variations.
Users can utilize the returned data to implement real-time filtering in applications, customize user experiences by censoring offensive content, and generate reports on language usage trends.
Users can expect consistent patterns in the response, such as a boolean value for "contains_offensive_word" and a list of detected profanities, which helps in quickly assessing the text's appropriateness.
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:
173ms
Service Level:
100%
Response Time:
270ms
Service Level:
100%
Response Time:
377ms
Service Level:
100%
Response Time:
5,059ms
Service Level:
100%
Response Time:
332ms
Service Level:
100%
Response Time:
921ms
Service Level:
100%
Response Time:
152ms
Service Level:
100%
Response Time:
21ms
Service Level:
100%
Response Time:
185ms
Service Level:
100%
Response Time:
264ms