In today's era of digital communication, the exchange of text-based content has become an integral component of our daily interactions. While this medium undeniably enhances communication and connectivity, it also exposes users to the possibility of encountering offensive, harmful or inappropriate content. The Online Safety API is emerging as an essential tool to address this challenge, as it enables real-time evaluation and filtering of text content, thus promoting safe and inclusive digital spaces.
The Online Safety API is a robust computing service meticulously designed to evaluate textual data and identify the presence of offensive or inappropriate language. Leveraging advanced natural language processing (NLP) techniques and machine learning algorithms, it calibrates the offensive potential of text, providing organizations and individuals with ratings or scores to maintain a respectful and safe digital environment.
Fundamentally, this API offers real-time content evaluation, streamlining the recognition of offensive or harmful language. Seamlessly integrated into chat applications, social media platforms or content moderation systems, the API acts as an effective filter that quickly highlights and resolves offensive content.
The Online Safety API plays a key role in creating safe and inclusive digital environments. By leveraging advanced natural language processing and machine learning capabilities, it enables organizations and individuals to proactively detect and address offensive content in real time. In a digital landscape where the importance of respectful and safe interactions cannot be overstated, this API is an invaluable asset for social media platforms, chat applications, content providers and many others. By addressing ethical considerations related to data privacy and bias mitigation, it stands as a strong advocate for digital security and inclusion.
This API will help you with the immediate detection of offensive words.
Social media monitoring: Automatically filter and remove offensive language and content from users' social media posts and comments.
Chat and messaging security: Ensure a safe and courteous environment in chat rooms and messaging applications by detecting and filtering offensive language in real time.
Comment control: Streamline moderation of user-generated comments on websites, blogs and forums to prevent the posting of offensive or harmful content.
Brand image protection: Protect your brand's reputation by monitoring and addressing offensive content or mentions of your products or services on the Internet.
Gaming community integrity: Keep online gaming communities free of offensive language and behavior, improving the overall gaming experience.
Besides the number of API calls available for the plan, there are no other limitations.
To use this endpoint you must specify a word or text in the parameter.
Detect hate text - Endpoint Features
Object | Description |
---|
["Non-offensive text."]
curl --location --request GET 'https://zylalabs.com/api/2857/online+safety+api/2973/detect+hate+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 Online Safety API is an application programming interface designed to analyze and categorize text content to determine if it contains offensive or inappropriate language.
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.
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.
To use this API you must specify a word or text.
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]
Service Level:
100%
Response Time:
2,452ms
Service Level:
100%
Response Time:
154ms
Service Level:
100%
Response Time:
291ms
Service Level:
100%
Response Time:
1,610ms
Service Level:
100%
Response Time:
302ms
Service Level:
100%
Response Time:
6ms
Service Level:
100%
Response Time:
318ms
Service Level:
100%
Response Time:
1,451ms
Service Level:
100%
Response Time:
290ms
Service Level:
100%
Response Time:
873ms
Service Level:
100%
Response Time:
224ms
Service Level:
100%
Response Time:
7ms
Service Level:
100%
Response Time:
238ms
Service Level:
100%
Response Time:
1,040ms
Service Level:
100%
Response Time:
593ms
Service Level:
100%
Response Time:
665ms
Service Level:
100%
Response Time:
120ms