This API offers an advanced system for automatically detecting offensive language in texts, allowing for the accurate identification of inappropriate words, insults, and potentially harmful expressions. Its main objective is to help evaluate texts in real time, improving the safety and quality of user-generated content. When a text is sent as input, the API returns a structured analysis that includes several indicators essential for understanding the level of toxicity present in the message.
One of the most important attributes is isProfanity, a Boolean value that indicates whether the text contains offensive or inappropriate language. It also provides a score, a quantitative metric that represents the estimated probability that the text will be considered profane. This value is especially useful in environments where moderation thresholds need to be adjusted for different contexts or audiences.
The API also includes a severity field, which classifies the level of severity of the detected language. This classification allows for distinguishing between mild cases, such as colloquial expressions, and more serious situations, such as direct insults or highly toxic language. For clarity, the response also specifies flaggedFor, a set of categories that explains the exact reason why the text was flagged, allowing automated systems to make more informed decisions.
Analyzes text and detects offensive language, returning severity, score, marked category, language, and whether the content should be considered profane or inappropriate.
Text Analyzer - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{"isProfanity":true,"score":0.8,"severity":70,"flaggedFor":["insult"],"language":"en","dialect":"general"}
curl --location --request POST 'https://zylalabs.com/api/11453/text+content+censoring+api/21613/text+analyzer' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw '{
"message": "I hate you"
}'
| 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 Text Analyzer endpoint returns structured data that includes indicators of offensive language in the analyzed text. Key outputs include whether the text contains profanity, a severity score, a risk score, flagged categories, the language of the text, and the identified dialect.
The key fields in the response data are `isProfanity` (Boolean), `score` (numeric), `severity` (numeric), `flaggedFor` (array of categories), `language` (string), and `dialect` (string). These fields provide insights into the nature and severity of the detected offensive language.
The response data is organized in a JSON format, with each key representing a specific aspect of the analysis. For example, `isProfanity` indicates if the text is offensive, while `flaggedFor` lists the reasons for flagging, allowing for easy parsing and interpretation by automated systems.
The Text Analyzer endpoint provides information on the presence of offensive language, severity levels, risk scores, categories of flagged content, and the language and dialect of the text. This comprehensive analysis aids in understanding the toxicity of user-generated content.
Users can customize their data requests by adjusting the input text they send to the Text Analyzer endpoint. While the endpoint does not accept additional parameters, the content of the text itself can vary to test different scenarios and analyze various types of language.
Typical use cases for the Text Analyzer data include content moderation for social media platforms, filtering user comments on websites, enhancing chat applications to prevent harassment, and ensuring compliance with community guidelines by identifying toxic language.
Data accuracy is maintained through continuous updates to the underlying language models and regular evaluations against diverse datasets. This ensures that the API can effectively recognize and classify offensive language across different contexts and dialects.
Standard data patterns in the response include a clear indication of whether the text is profane (`isProfanity`), a numeric score reflecting the severity of the language, and a list of categories in `flaggedFor`. Users can expect consistent formatting and structure in the JSON response.
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:
1,648ms
Service Level:
100%
Response Time:
1,648ms
Service Level:
100%
Response Time:
1,648ms
Service Level:
100%
Response Time:
292ms
Service Level:
100%
Response Time:
1,648ms
Service Level:
100%
Response Time:
21ms
Service Level:
100%
Response Time:
315ms
Service Level:
100%
Response Time:
13,440ms
Service Level:
100%
Response Time:
315ms
Service Level:
100%
Response Time:
315ms