Sentiment Analysis is a simple tool for analyzing the sentiment of a text. It returns the sentiment score and the sentiment label.
Try it — live request, no key required
No key required to try it. Get a key to use it in your app.
{
"status": "ok",
"error": null,
"data": {
// Sentiment Analysis response payload
}
}
About the Sentiment Analysis API
Sentiment Analysis works by analyzing the text and comparing it to a large database of sentiment analysis models. It uses advanced algorithms to analyze the sentiment of the text and returns the sentiment score and the sentiment label.
What people use it for
- Social Media Monitoring
- Use the Sentiment Analysis API to analyze text sentiment for social media monitoring. Use the data to track brand sentiment, monitor customer feedback, and identify trends
- Customer Feedback
- Analyze customer feedback by using the Sentiment Analysis API to evaluate text sentiment. Use the data to measure customer satisfaction, improve products, and enhance customer experience
- Market Research
- Conduct market research by using the Sentiment Analysis API to analyze text sentiment. Use the data to study consumer behavior, identify market trends, and make data-driven decisions
- Brand Reputation
- Monitor brand reputation by using the Sentiment Analysis API to analyze text sentiment. Use the data to assess brand sentiment, manage public relations, and respond to feedback
Ways to call it
One endpoint, many ways in — REST with JSON, XML, YAML and CSV, plus GraphQL and an MCP interface for AI agents.
- JSON
- Default REST response
- XML
- Markup format
- YAML
- Human-readable
- CSV
- Tabular export
- GraphQL
- Query language
- MCP
- For AI agents
Other ways to use Sentiment Analysis
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Sentiment Analysis API do?
How do I authenticate Sentiment Analysis API requests?
How much does the Sentiment Analysis API cost?
How fast is the Sentiment Analysis API?
What response formats does the Sentiment Analysis API support?
What HTTP method does the Sentiment Analysis API use?
Request parameters — POST /v1/sentimentanalysis
Sent as JSON in the request body. Premium parameters are accepted on every plan but only take effect on plans that include them. Anything not listed here is dropped rather than passed through.
Required
| Parameter | Type | Example | Description |
|---|---|---|---|
textRequired | string | I absolutely love this product! It exceeded all my expectations. | The text to analyze the sentiment of length 0-50000 |
curl -X POST "https://api.apiverve.com/v1/sentimentanalysis" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"I'\''m so excited that tomorrow is going to be sunny! Can'\''t wait!"}'Authentication
Send your key in the x-api-key header. That is the only auth step — no token exchange, and no per-endpoint scope to configure.
| Header | When | Value |
|---|---|---|
x-api-keyRequired | Every request | Your API key. Header names are case-insensitive, so X-API-Key is the same header. |
AuthorizationAlternate | Instead of the above | Bearer <key> — for clients that only expose bearer auth. Resolves to the same account and the same billing. |
content-typeRequired | POST body | application/json |
A 401 means the key is missing, invalid or expired. A 403 means the key is valid but not permitted here — blocked by a key restriction or an IP allow-list. Running out of credits is a 429.
Response — POST /v1/sentimentanalysis
Every APIVerve endpoint returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape.
{
"status": "ok",
"error": null,
"data": {
"comparative": 0.25,
"sentimentText": "positive",
"sentiment": 3,
"isPositive": true,
"isNegative": false,
"normalizedScore": 0.3
}
}
Response fields
Paths are relative to data. Premium fields are absent rather than zeroed on plans that do not include them, so check for presence instead of comparing to 0.
| Field | Type | Example | Description |
|---|---|---|---|
comparative | number | 0.25 | |
sentimentText | string | "positive" | |
sentiment | number | 3 | |
isPositive | boolean | true | Whether the sentiment is positive |
isNegative | boolean | false | Whether the sentiment is negative |
normalizedScorePremium | number | 0.3 | Sentiment score normalized to -1 to 1 range |
Response headers
Every response carries your balance, so your own code always knows where it stands without polling anything. All four are exposed to browsers through CORS.
| Header | What it carries |
|---|---|
x-api-remaining-credits | Credits left in the current cycle |
x-api-credits-used | Credits spent in the current cycle |
x-api-max-credits | The allowance for the cycle |
x-api-version | Version of the endpoint that answered |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter that has to change. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted here | A key restriction or an IP allow-list — never a bad key. |
429 | Rate limited, or out of credits | Read error to tell them apart, then back off or top up. |
What a call costs — 10 credits per call
Credits are shared across every APIVerve API — one balance, one key, one bill. Failed requests never count against it, so a rejected input costs nothing.
| Plan | Per month | Credits | Sentiment Analysis calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 20 | Free |
| Starter | $29.99 | 200,000 | 20,000 | $1.50 |
| Pro | $99.99 | 1,000,000 | 100,000 | $1.00 |
| Mega | $299.99 | 4,000,000 | 400,000 | $0.75 |
Calls are what the credits buy at this API's rate — spend them here, on any of the other APIs, or across both. Nothing is reserved per endpoint.
Call it from cURL — POST /v1/sentimentanalysis
No SDK to install — this is a plain HTTPS call to /v1/sentimentanalysis with your key in the x-api-key header. Swap in a real key and it runs as-is.
curl "https://api.apiverve.com/v1/sentimentanalysis" \
-H "x-api-key: YOUR_API_KEY"Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Node.js — POST /v1/sentimentanalysis
Install the Node.js SDK, then call the Sentiment Analysis API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/sentimentanalysisconst res = await fetch("https://api.apiverve.com/v1/sentimentanalysis", {
headers: { "x-api-key": "YOUR_API_KEY" },
});
const { data } = await res.json();
console.log(data);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Python — POST /v1/sentimentanalysis
Install the Python SDK, then call the Sentiment Analysis API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-sentimentanalysisimport requests
res = requests.get(
"https://api.apiverve.com/v1/sentimentanalysis",
headers={"x-api-key": "YOUR_API_KEY"},
)
print(res.json()["data"])Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from C# / .NET — POST /v1/sentimentanalysis
Install the C# / .NET SDK, then call the Sentiment Analysis API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
dotnet add package APIVerve.API.SentimentAnalysisusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/sentimentanalysis");
Console.WriteLine(json);Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Go — POST /v1/sentimentanalysis
No SDK to install — this is a plain HTTPS call to /v1/sentimentanalysis with your key in the x-api-key header. Swap in a real key and it runs as-is.
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/sentimentanalysis", nil)
req.Header.Set("x-api-key", "YOUR_API_KEY")
res, _ := http.DefaultClient.Do(req)
defer res.Body.Close()
body, _ := io.ReadAll(res.Body)
fmt.Println(string(body))Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from PHP — POST /v1/sentimentanalysis
No SDK to install — this is a plain HTTPS call to /v1/sentimentanalysis with your key in the x-api-key header. Swap in a real key and it runs as-is.
$ch = curl_init("https://api.apiverve.com/v1/sentimentanalysis");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-api-key: YOUR_API_KEY"]);
$response = curl_exec($ch);
echo $response;Resources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Call it from Ruby — POST /v1/sentimentanalysis
No SDK to install — this is a plain HTTPS call to /v1/sentimentanalysis with your key in the x-api-key header. Swap in a real key and it runs as-is.
require "net/http"
uri = URI("https://api.apiverve.com/v1/sentimentanalysis")
req = Net::HTTP::Get.new(uri)
req["x-api-key"] = "YOUR_API_KEY"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |h| h.request(req) }
puts res.bodyResources
Also published for
Only the languages APIVerve ships a client for are listed — the rest call the endpoint directly over HTTPS.
Zero-code embed — one snippet, no backend
Drop an interactive Sentiment Analysis form onto any page. The widget calls the API for you, so no key ever appears in your markup and there is nothing to deploy.
Changelog — Sentiment Analysis API
Every change to this endpoint, newest first. Breaking changes ship as a new version and the previous one keeps serving — response fields are added, never removed or retyped in place, so an integration written against v1 keeps working.
Entries are picked up from dated catalog snapshots, so the first one appears after the next snapshot that moves something. A period where nothing changed produces no entry — silence is a valid changelog for the Sentiment Analysis API.
AI/Computer Vision
Related articles
All articles →
Summarize Text with AI: A Practical GuideUse AI to summarize articles, documents, and user content. Tutorial with code for content platforms, research tools, and dashboards.Read
Why Your Sentiment Analysis Is WrongSentiment analysis is powerful but often misused. Here's how to use sentiment data effectively.Read
Sentiment Analysis: Read Customer Feedback at ScaleProcess thousands of reviews, support tickets, and social mentions automatically. Find the signal in the noise.Read