{"original": "shit", "censored": "****", "has_profanity": true}
curl --location --request GET 'https://zylalabs.com/api/3030/expletive+detection+api/3202/detector?text=shit' --header 'Authorization: Bearer YOUR_API_KEY'
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 Expletive Detection API simply include your bearer token in the Authorization header.
| 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.
(Save 2 months with annual billing 🎉)
Trusted by leading companies
The Expletive Detection API is an indispensable tool designed to enhance the content moderation capabilities of applications, platforms and websites by automatically identifying and filtering offensive language and inappropriate content. This API acts as a robust safeguard, ensuring that user-generated text adheres to community standards, maintaining a positive and respectful digital environment.
In essence, the profanity filtering API works by analyzing the text entered and detecting the presence of profanity, hate speech or any content that violates predefined linguistic guidelines. This process involves a combination of linguistic analysis, pattern recognition and contextual understanding to accurately identify and flag instances of inappropriate language.
Real-time processing is a key aspect of the Expletive Detection API. The ability to analyze and filter text content in real time is crucial for applications involving live chat, instant messaging or dynamic content generation. This ensures that offensive language is identified and addressed immediately, contributing to a fast and responsive moderation mechanism.
Seamless integration of the Expletive Detection API into existing applications is facilitated by its well-documented endpoint and compatibility with popular programming languages. This ease of integration streamlines the implementation process, allowing developers to quickly deploy the profanity filter and enhance the content moderation capabilities of their platforms.
In summary, the Expletive Detection API is an essential tool for applications and platforms looking to maintain a high level of content moderation. This API enables platform users to effectively filter out inappropriate language, ensuring a positive and respectful digital space for users. Its ease of integration and ability to adapt to various content moderation needs make it a valuable asset for any online platform committed to fostering a respectful and inclusive online community.
It will receive parameters and provide you with a JSON.
Social Media Moderation: Integrate the Expletive Detection API to automatically moderate and filter offensive language in comments, posts, and user interactions on social media platforms.
Enhance chat applications by implementing real-time profanity filtering, ensuring a positive and respectful communication environment.
Online Forums and Communities: Use the API to moderate discussions on forums and community websites, preventing the use of offensive language and maintaining a civil discourse.
Gaming Platforms: Integrate the Expletive Detection API in online gaming platforms to moderate in-game chat, ensuring a pleasant gaming experience for players.
E-learning Platforms: Apply profanity filtering in discussion forums and chat features of e-learning platforms to create a respectful and focused learning environment.
Besides the number of API calls, there is no other limitation
To use this API the user must specify a text to filter profanity.
The Expletive Detection API is a powerful tool designed to automatically identify and filter out offensive language, including profanity and inappropriate content, from text input.
Zyla provides a wide range of integration methods for almost all programming languages. You can use these codes to integrate with your project as you need.
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 GET Detector endpoint returns a JSON object containing the original text, a censored version of the text with profanity replaced by asterisks, and a boolean indicating whether profanity was detected.
The key fields in the response data are "original" (the input text), "censored" (the filtered text), and "has_profanity" (a boolean indicating the presence of offensive language).
The response data is structured as a JSON object with three fields: "original," "censored," and "has_profanity," allowing for easy parsing and utilization in applications.
The primary parameter for the GET Detector endpoint is "text," which should contain the user-generated content to be analyzed for offensive language.
Users can customize their requests by varying the input text parameter to analyze different strings for profanity, allowing for flexible content moderation across various contexts.
Typical use cases include moderating comments on social media, filtering chat messages in gaming platforms, and ensuring respectful discourse in online forums and e-learning environments.
Data accuracy is maintained through a combination of linguistic analysis, pattern recognition, and contextual understanding, ensuring reliable identification of offensive language.
If the input text is empty, the API will return a response indicating no profanity detected. Users should implement checks to handle such cases gracefully in their applications.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key 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.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
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. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
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.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund