Inappropriate Text Detection API

Inappropriate Text Detection API uses machine learning algorithms to automatically identify and flag potentially offensive or inappropriate content in text. It helps companies and organizations maintain safe and respectful online communication by accurately detecting and filtering out profanity, hate speech, and other forms of harmful content.

About the API:

The Inappropriate Text Detection API is a powerful tool for identifying and flagging potentially offensive or inappropriate content in text. It utilizes machine learning algorithms to accurately detect and filter out profanity, hate speech, and other forms of harmful content, helping companies and organizations maintain safe and respectful online communication. The API is designed to be easy to integrate into existing systems, providing fast and reliable results.

With the growing concern over cyberbullying, hate speech, and other forms of online harassment, the Inappropriate Text Detection API is a crucial tool for companies and organizations looking to promote safe and respectful online communication. Whether it is used to monitor social media posts, comments, or other forms of online text, the API is designed to quickly and accurately identify potentially offensive content.

The API uses advanced machine learning algorithms to analyze text in real-time, automatically flagging potentially inappropriate content for review by a human moderator. This not only saves time and resources but also ensures that harmful content is identified and removed quickly and effectively.

Overall, the Inappropriate Text Detection API is an essential tool for companies and organizations looking to promote safe and respectful online communication. Whether you are a social media platform, a gaming company, or a business with a large online presence, this API can help you protect your users and maintain a safe and respectful online environment.

 

What this API receives and what your API provides (input/output)?

Pass the text that you want to analyze and receive its inadequate percentage. 

 

What are the most common uses cases of this API?

  1. Social Media Platforms: Social media platforms can use the API to monitor user-generated content and flag potentially offensive posts, comments, or messages. This helps ensure a safe and respectful online community and prevents cyberbullying and other forms of online harassment.

  2. Gaming Companies: Gaming companies can use the API to monitor in-game chat and flag potentially inappropriate or offensive language. This helps maintain a positive gaming experience for all players and prevent harassment and hate speech.

  3. Customer Service: Businesses can use the API to monitor customer interactions and flag potentially inappropriate or offensive messages. This helps maintain professional and respectful customer service and prevent situations that could harm the company's reputation.

  4. News Outlets: News outlets can use the API to monitor user-generated content and flag potentially offensive comments. This helps maintain a safe and respectful online community for discussion of current events.

  5. Online Marketplaces: Online marketplaces can use the API to monitor product reviews and flag potentially inappropriate or offensive language. This helps maintain a professional and respectful marketplace and prevent situations that could harm the company's reputation.

  6. Educational Institutions: Educational institutions can use the API to monitor student interactions and flag potentially inappropriate or offensive language. This helps maintain a safe and respectful learning environment and prevents bullying and harassment.

 

Are there any limitations to your plans?

Besides API call limitations per month, there is no other limitation. 

API Documentation

Endpoints


You can pass any plain text to the profanity detector API to be examined for profanity. You can also specify how sensitive you would like the profanity detector to be. Works with English content only.



                                                                            
POST https://zylalabs.com/api/1216/inappropriate+text+detection+api/1056/detector
                                                                            
                                                                        

Detector - Endpoint Features

Object Description
text [Required] The text you wish to analyse.
level [Required] The sensitivity you want to set the profanity detection systems to. 1: Highlight strong profanity only (e.g., "fuck", "arse", racism and other discriminatory language). 2: Highlight strong and medium profanity including mildly offensive words (e.g., "idiot", "dammit", "wanker"). 3: Highlight all potential profanity, including words which are usually fine but can be profane or objectionable in certain circumstances (e.g., "black", "yank", "addict").
Test Endpoint

API EXAMPLE RESPONSE

       
                                                                                                        
                                                                                                                                                                                                                            {"profanities":[{"profanity":"fucking","type":"sexual","source":"fuck","start":7,"length":7},{"profanity":"douchebag","type":"sexual","source":"douche","start":15,"length":9},{"profanity":"black","type":"racial","source":"black","start":33,"length":5},{"profanity":"faggots","type":"sexuality","source":"fagot","start":82,"length":7}],"profanity_count":4,"server_reference":"web1","result":"success","response_timestamp":1675896098}
                                                                                                                                                                                                                    
                                                                                                    

Detector - CODE SNIPPETS


curl --location --request POST 'https://zylalabs.com/api/1216/inappropriate+text+detection+api/1056/detector?text=This service is great. I will recommend it.&level=3' --header 'Authorization: Bearer YOUR_API_KEY' 

    

API Access Key & Authentication

After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Inappropriate Text Detection API REST API, simply include your bearer token in the Authorization header.
Headers
Header Description
Authorization [Required] Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.

Simple Transparent Pricing

No long term commitments. One click upgrade/downgrade or cancellation. No questions asked.

πŸš€ Enterprise

Starts at
$ 10,000/Year


  • Custom Volume
  • Specialized Customer Support
  • Real-Time API Monitoring

Customer favorite features

  • βœ”οΈŽ Only Pay for Successful Requests
  • βœ”οΈŽ Free 7-Day Trial
  • βœ”οΈŽ Multi-Language Support
  • βœ”οΈŽ One API Key, All APIs.
  • βœ”οΈŽ Intuitive Dashboard
  • βœ”οΈŽ Comprehensive Error Handling
  • βœ”οΈŽ Developer-Friendly Docs
  • βœ”οΈŽ Postman Integration
  • βœ”οΈŽ Secure HTTPS Connections
  • βœ”οΈŽ Reliable Uptime

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.

Prices are listed in USD (United States Dollar), EUR (Euro), CAD (Canadian Dollar), AUD (Australian Dollar), and GBP (British Pound). We accept all major debit and credit cards. Our payment system uses the latest security technology and is powered by Stripe, one of the world’s most reliable payment companies. If you have any trouble paying by card, just contact us at [email protected]

Additionally, if you already have an active subscription in any of these currencies (USD, EUR, CAD, AUD, GBP), that currency will remain for subsequent subscriptions. You can change the currency at any time as long as you don't have any active subscriptions.

The local currency shown on the pricing page is based on the country of your IP address and is provided for reference only. The actual prices are in USD (United States Dollar). When you make a payment, the charge will appear on your card statement in USD, even if you see the equivalent amount in your local currency on our website. This means you cannot pay directly with your local currency.

Occasionally, a bank may decline the charge due to its fraud protection settings. We suggest reaching out to your bank initially to check if they are blocking our charges. Also, you can access the Billing Portal and change the card associated to make the payment. If these does not work and you need further assistance, please contact our team at [email protected]

Prices are determined by a recurring monthly or yearly subscription, depending on the chosen plan.

API calls are deducted from your plan based on successful requests. Each plan comes with a specific number of calls that you can make per month. Only successful calls, indicated by a Status 200 response, will be counted against your total. This ensures that failed or incomplete requests do not impact your monthly quota.

Zyla API Hub works on a recurring monthly subscription system. Your billing cycle will start the day you purchase one of the paid plans, and it will renew the same day of the next month. So be aware to cancel your subscription beforehand if you want to avoid future charges.

To upgrade your current subscription plan, simply go to the pricing page of the API and select the plan you want to upgrade to. The upgrade will be instant, allowing you to immediately enjoy the features of the new plan. Please note that any remaining calls from your previous plan will not be carried over to the new plan, so be aware of this when upgrading. You will be charged the full amount of the new plan.

To check how many API calls you have left for the current month, look at the β€˜X-Zyla-API-Calls-Monthly-Remaining’ header. For example, if your plan allows 1000 requests per month and you've used 100, this header will show 900.

To see the maximum number of API requests your plan allows, check the β€˜X-Zyla-RateLimit-Limit’ header. For instance, if your plan includes 1000 requests per month, this header will display 1000.

The β€˜X-Zyla-RateLimit-Reset’ header shows the number of seconds until your rate limit resets. This tells you when your request count will start fresh. For example, if it displays 3600, it means 3600 seconds are left until the limit resets.

Yes, you can cancel your plan anytime by going to your account and selecting the cancellation option on the Billing page. Please note that upgrades, downgrades, and cancellations take effect immediately. Additionally, upon cancellation, you will no longer have access to the service, even if you have remaining calls left in your quota.

You can contact us through our chat channel to receive immediate assistance. We are always online from 8 am to 5 pm (EST). If you reach us after that time, we will get back to you as soon as possible. Additionally, you can contact us via email at [email protected]

To let you experience our APIs without any commitment, we offer a 7-day free trial that allows you to make API calls at no cost during this period. Please note that you can only use this trial once, so make sure to use it with the API that interests you the most. Most of our APIs provide a free trial, but some may not support it.

After 7 days, you will be charged the full amount for the plan you were subscribed to during the trial. Therefore, it’s important to cancel before the trial period ends. Refund requests for forgetting to cancel on time are not accepted.

When you subscribe to an API trial, you can make only 25% of the calls allowed by that plan. For example, if the API plan offers 1000 calls, you can make only 250 during the trial. To access the full number of calls offered by the plan, you will need to subscribe to the full plan.

 Service Level
100%
 Response Time
659ms

Category:

NLP

Related APIs