The Text Emotion Retrieval API allows you to identify and quantify the emotions present in any piece of text. Its goal is to help understand the emotional tone behind written language, offering valuable information to optimize human interactions, improve communication, and enrich content analysis.
Upon receiving a text, the API analyzes its linguistic content and returns a set of basic emotions, such as happiness, anger, sadness, surprise, and fear, each accompanied by a numerical value indicating its intensity or level of presence. These values, expressed as scores from 0 to 1, allow you to accurately determine the predominant emotion in the text and the extent to which the others are manifested.
This service is particularly useful for applications in the fields of sentiment analysis, customer service, marketing, social research, social media monitoring, chatbot development, and review analysis. Companies can use it to assess the emotional state of their customers, measure the reaction to advertising campaigns, or adjust automated communication according to the detected tone.
In short, the Text Emotion Retrieval API is a powerful and flexible solution for transforming text into meaningful emotional information. With it, developers and analysts can better understand the emotions behind words and make more informed decisions based on the emotional state of users or audiences.
It analyzes a text and returns levels of emotions such as happiness, anger, sadness, surprise, and fear, indicating the intensity of each one.
Emotion Detection - Endpoint Features
| Object | Description |
|---|---|
Request Body |
[Required] Json |
{
"Happy": 1.0,
"Angry": 0.0,
"Surprise": 0.0,
"Sad": 0.0,
"Fear": 0.0
}
curl --location --request POST 'https://zylalabs.com/api/10878/text+emotion+retrieval+api/20583/emotion+detection' --header 'Authorization: Bearer YOUR_API_KEY'
--data-raw 'I am very happy to use this API.'
| 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 Emotion Detection endpoint returns a JSON object containing scores for five basic emotions: happiness, anger, sadness, surprise, and fear. Each emotion is represented by a numerical value ranging from 0 to 1, indicating its intensity in the analyzed text.
The key fields in the response data are "Happy," "Angry," "Sad," "Surprise," and "Fear." Each field corresponds to an emotion and contains a score that reflects the intensity of that emotion in the provided text.
The response data is organized as a JSON object with emotion labels as keys and their corresponding intensity scores as values. This structure allows for easy parsing and interpretation of the emotional content of the text.
Typical use cases include sentiment analysis for customer feedback, enhancing chatbot interactions based on user emotions, monitoring social media sentiment, and analyzing emotional responses to marketing campaigns or content.
Users can customize their data requests by providing different text inputs to the Emotion Detection endpoint. The API analyzes the specific text submitted, allowing for tailored emotional insights based on varying content.
Data accuracy is maintained through advanced natural language processing algorithms that analyze linguistic patterns and context. Continuous updates and improvements to the model ensure that it adapts to evolving language use and emotional expression.
Standard data patterns include varying intensity scores for emotions based on the text's tone. For instance, a text expressing joy may yield a high happiness score and low scores for other emotions, while a text with conflict may show higher anger and fear scores.
Users can utilize the returned data by interpreting the scores to gauge the emotional tone of the text. For example, a high happiness score can indicate positive sentiment, guiding responses in customer service or content creation strategies.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
To obtain your API key, you first need to sign in to your account and subscribe to the API you want to use. Once subscribed, go to your Profile, open the Subscription section, and select the specific API. Your API key will be available there and can be used 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.
If you don’t cancel before the 7th day, your free trial will end automatically and your subscription will switch to a paid plan under the same plan you originally subscribed to, meaning you will be charged and gain access to the API calls included in that plan.
The free trial ends when you reach 50 API requests or after 7 days, whichever comes first.
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, we offer a 7-day free trial that allows you to make up to 50 API calls at no cost, so you can test our APIs without any commitment.
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.
Service Level:
100%
Response Time:
19ms
Service Level:
100%
Response Time:
1,768ms
Service Level:
100%
Response Time:
9,212ms
Service Level:
100%
Response Time:
8,667ms
Service Level:
100%
Response Time:
16ms
Service Level:
100%
Response Time:
149ms
Service Level:
100%
Response Time:
20ms
Service Level:
100%
Response Time:
216ms
Service Level:
100%
Response Time:
17ms
Service Level:
100%
Response Time:
8,644ms
Service Level:
100%
Response Time:
726ms
Service Level:
100%
Response Time:
1,134ms
Service Level:
100%
Response Time:
10,154ms
Service Level:
100%
Response Time:
830ms
Service Level:
75%
Response Time:
1,498ms
Service Level:
100%
Response Time:
11,971ms
Service Level:
100%
Response Time:
2,560ms
Service Level:
100%
Response Time:
796ms
Service Level:
100%
Response Time:
3,497ms
Service Level:
100%
Response Time:
1,585ms