The Censorship API is a powerful tool designed to help developers effectively manage and moderate user-generated content by identifying and filtering offensive or inappropriate language. With its comprehensive set of features, this API enables companies to create safer and more respectful online environments.
At the core of the Censorship API is a sophisticated algorithm that analyzes text input and detects potentially offensive words. It leverages an extensive database of profanity, racial slurs, vulgar language and other inappropriate content to accurately identify and flag such cases. By integrating this API into their applications, websites or platforms, developers can automatically scan and sanitize user-generated content in real time, mitigating the risk of offensive or harmful language.
This ensures that the API adapts to the context and sensitivities of different applications or industries. Whether it is a social networking platform, a messaging application, a gaming community or an e-commerce website, the profanity filter API can adapt to the various content moderation needs.
Integrating the profanity filter API is a breeze, thanks to its developer-friendly documentation and robust SDKs (software development kits). The API can be seamlessly integrated into various programming languages, frameworks and platforms, allowing developers to quickly implement content moderation functions without extensive coding. It provides simple yet powerful methods for text analysis, allowing developers to easily identify and manage instances of offensive language in their applications.
To improve efficiency and performance, the Censorship API is designed to handle large volumes of content with minimal latency. It leverages advanced machine learning techniques and cloud infrastructure to ensure fast and accurate analysis, even under high load conditions. This enables companies to expand their content moderation capabilities to meet the demands of growing user bases and increasingly dynamic online environments.
It will receive parameters and provide you with a JSON.
Social media platforms: Implement the profanity filter API to automatically scan and block offensive language in user comments, posts and messages, creating a more positive and respectful online community.
Online forums and discussion boards: Ensure discussions remain civil and respectful by filtering out profanity and offensive language in user-generated content.
Chat applications: Enhance the user experience by filtering and hiding offensive language in conversations, fostering a friendly and inclusive chat environment.
Gaming communities: Maintain a safe and welcoming environment for gamers by automatically filtering out profanity, hate speech and inappropriate language in game chats or user-generated content.
E-commerce websites: Implement the API to scan and block offensive language in product reviews, comments or user feedback, helping to maintain a professional and trustworthy image for your brand.
Besides the number of API calls, there are no other limitations.
To use this endpoint, simply enter a text in the parameter (maximum 1,000 characters).
Censure Text - Endpoint Features
Object | Description |
---|
{"original": "go to hell", "censored": "go to ****", "has_profanity": true}
curl --location --request GET 'https://zylalabs.com/api/2092/censorship+api/1872/censure+text' --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 commitments. One click upgrade/downgrade or cancellation. No questions asked.
The Censure Text endpoint returns a JSON object containing the original text, the censored version, and a boolean indicating whether profanity was detected. This allows developers to easily identify and manage offensive language in user-generated content.
The key fields in the response data include "original" (the input text), "censored" (the modified text with profanity replaced), and "has_profanity" (a boolean indicating the presence of offensive language).
The response data is structured as a JSON object. It includes three main fields: "original," "censored," and "has_profanity," making it easy for developers to parse and utilize the information in their applications.
The Censure Text endpoint accepts a single parameter: the text to be analyzed, with a maximum length of 1,000 characters. This allows users to customize their requests based on the content they wish to filter.
Users can utilize the returned data by checking the "has_profanity" field to determine if action is needed. The "censored" field can be displayed to users, ensuring a clean and respectful environment while retaining the context of the original message.
The Censorship API uses an extensive database that includes various forms of profanity, racial slurs, and vulgar language. This database is regularly updated to maintain accuracy and relevance in identifying offensive content.
Data accuracy is maintained through continuous updates to the profanity database and the use of advanced machine learning techniques. This ensures that the API adapts to evolving language and slang, providing reliable content moderation.
Typical use cases for the Censorship API include moderating comments on social media, filtering chat messages in gaming communities, and sanitizing product reviews on e-commerce sites. These applications help create safer online environments.
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, refer to the βX-Zyla-API-Calls-Monthly-Remainingβ field in the response header. For example, if your plan allows 1,000 requests per month and you've used 100, this field in the response header will indicate 900 remaining calls.
To see the maximum number of API requests your plan allows, check the βX-Zyla-RateLimit-Limitβ response header. For instance, if your plan includes 1,000 requests per month, this header will display 1,000.
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 3,600, it means 3,600 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 give you the opportunity to experience our APIs without any commitment, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost. This trial can be used only once, so we recommend applying it to the API that interests you the most. While most of our APIs offer a free trial, some may not. The trial concludes after 7 days or once you've made 50 requests, whichever occurs first. If you reach the 50 request limit during the trial, you will need to "Start Your Paid Plan" to continue making requests. You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab. Alternatively, if you don't cancel your subscription before the 7th day, your free trial will end, and your plan will automatically be billed, granting you access to all the API calls specified in your plan. Please keep this in mind to avoid unwanted charges.
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 free trial, you can make up to 50 API calls. If you wish to make additional API calls beyond this limit, the API will prompt you to perform an "Start Your Paid Plan." You can find the "Start Your Paid Plan" button in your profile under Subscription -> Choose the API you are subscribed to -> Pricing tab.
Payout Orders are processed between the 20th and the 30th of each month. If you submit your request before the 20th, your payment will be processed within this timeframe.
Service Level:
100%
Response Time:
21ms
Service Level:
100%
Response Time:
988ms
Service Level:
100%
Response Time:
377ms
Service Level:
100%
Response Time:
1,294ms
Service Level:
100%
Response Time:
297ms
Service Level:
100%
Response Time:
130ms
Service Level:
100%
Response Time:
198ms
Service Level:
100%
Response Time:
1,107ms
Service Level:
100%
Response Time:
852ms
Service Level:
100%
Response Time:
2,201ms
Service Level:
100%
Response Time:
4,692ms
Service Level:
100%
Response Time:
5,605ms
Service Level:
100%
Response Time:
591ms
Service Level:
100%
Response Time:
607ms
Service Level:
97%
Response Time:
293ms
Service Level:
85%
Response Time:
454ms
Service Level:
100%
Response Time:
527ms
Service Level:
100%
Response Time:
695ms
Service Level:
100%
Response Time:
655ms
Service Level:
100%
Response Time:
2,038ms