Sentiment AnalysisSentiment Analysis API

OnlineCredit Usage:1 per callRefreshed 1 month ago
avg: 1033ms|p50: 940ms|p75: 1095ms|p90: 1281ms|p99: 1653ms

Sentiment Analysis is a simple tool for analyzing the sentiment of a text. It returns the sentiment score and the sentiment label.

The Sentiment Analysis API provides reliable and fast access to sentiment analysis data through a simple REST interface. Built for developers who need consistent, high-quality results with minimal setup time.

To use Sentiment Analysis, you need an API key. You can get one by creating a free account and visiting your dashboard.

POST Endpoint

URL
https://api.apiverve.com/v1/sentimentanalysis

Code Examples

Here are examples of how to call the Sentiment Analysis API in different programming languages:

cURL Request
curl -X POST \
  "https://api.apiverve.com/v1/sentimentanalysis" \
  -H "X-API-Key: your_api_key_here" \
  -H "Content-Type: application/json" \
  -d '{
  "text": "I'm so excited that tomorrow is going to be sunny! Can't wait!"
}'
JavaScript (Fetch API)
const response = await fetch('https://api.apiverve.com/v1/sentimentanalysis', {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({
    "text": "I'm so excited that tomorrow is going to be sunny! Can't wait!"
})
});

const data = await response.json();
console.log(data);
Python (Requests)
import requests

headers = {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
}

payload = {
    "text": "I'm so excited that tomorrow is going to be sunny! Can't wait!"
}

response = requests.post('https://api.apiverve.com/v1/sentimentanalysis', headers=headers, json=payload)

data = response.json()
print(data)
Node.js (Native HTTPS)
const https = require('https');
const url = require('url');

const options = {
  method: 'POST',
  headers: {
    'X-API-Key': 'your_api_key_here',
    'Content-Type': 'application/json'
  }
};

const postData = JSON.stringify({
  "text": "I'm so excited that tomorrow is going to be sunny! Can't wait!"
});

const req = https.request('https://api.apiverve.com/v1/sentimentanalysis', options, (res) => {
  let data = '';
  res.on('data', (chunk) => data += chunk);
  res.on('end', () => console.log(JSON.parse(data)));
});

req.write(postData);
req.end();
PHP (cURL)
<?php

$ch = curl_init();

curl_setopt($ch, CURLOPT_URL, 'https://api.apiverve.com/v1/sentimentanalysis');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_CUSTOMREQUEST, 'POST');
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'X-API-Key: your_api_key_here',
    'Content-Type: application/json'
]);

curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode({
    'text': 'I'm so excited that tomorrow is going to be sunny! Can't wait!'
}));

$response = curl_exec($ch);
curl_close($ch);

$data = json_decode($response, true);
print_r($data);

?>
Go (net/http)
package main

import (
    "fmt"
    "io"
    "net/http"
    "bytes"
    "encoding/json"
)

func main() {
    payload := map[string]interface{}{
        "text": "I'm so excited that tomorrow is going to be sunny! Can't wait!"
    }

    jsonPayload, _ := json.Marshal(payload)
    req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/sentimentanalysis", bytes.NewBuffer(jsonPayload))

    req.Header.Set("X-API-Key", "your_api_key_here")
    req.Header.Set("Content-Type", "application/json")

    client := &http.Client{}
    resp, err := client.Do(req)
    if err != nil {
        panic(err)
    }
    defer resp.Body.Close()

    body, _ := io.ReadAll(resp.Body)
    fmt.Println(string(body))
}
Ruby (Net::HTTP)
require 'net/http'
require 'json'

uri = URI('https://api.apiverve.com/v1/sentimentanalysis')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true

payload = {
  "text": "I'm so excited that tomorrow is going to be sunny! Can't wait!"
}

request = Net::HTTP::Post.new(uri)
request['X-API-Key'] = 'your_api_key_here'
request['Content-Type'] = 'application/json'

request.body = payload.to_json

response = http.request(request)
puts JSON.pretty_generate(JSON.parse(response.body))
C# (HttpClient)
using System;
using System.Net.Http;
using System.Text;
using System.Threading.Tasks;

class Program
{
    static async Task Main(string[] args)
    {
        using var client = new HttpClient();
        client.DefaultRequestHeaders.Add("X-API-Key", "your_api_key_here");

        var jsonContent = @"{
        ""text"": ""I'm so excited that tomorrow is going to be sunny! Can't wait!""
}";
        var content = new StringContent(jsonContent, Encoding.UTF8, "application/json");

        var response = await client.PostAsync("https://api.apiverve.com/v1/sentimentanalysis", content);
        response.EnsureSuccessStatusCode();

        var responseBody = await response.Content.ReadAsStringAsync();
        Console.WriteLine(responseBody);
    }
}

Authentication

The Sentiment Analysis API requires authentication via API key. Include your API key in the request header:

Required Header
X-API-Key: your_api_key_here

Learn more about authentication →

Interactive API Playground

Test the Sentiment Analysis API directly in your browser with live requests and responses.

Parameters

The following parameters are available for the Sentiment Analysis API:

Analyze Sentiment

ParameterTypeRequiredDescriptionDefaultExample
textstringrequired
The text to analyze the sentiment of
-I'm so excited that tomorrow is going to be sunny! Can't wait!

Response

The Sentiment Analysis API returns responses in JSON, XML, YAML, and CSV formats:

Example Responses

JSON Response
200 OK
{
  "status": "ok",
  "error": null,
  "data": {
    "comparative": 0.25,
    "sentimentText": "positive",
    "sentiment": 3,
    "isPositive": true,
    "isNegative": false,
    "normalizedScore": 0.3
  }
}
XML Response
200 OK
<?xml version="1.0" encoding="UTF-8"?>
<response>
  <status>ok</status>
  <error xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
  <data>
    <comparative>0.25</comparative>
    <sentimentText>positive</sentimentText>
    <sentiment>3</sentiment>
    <isPositive>true</isPositive>
    <isNegative>false</isNegative>
    <normalizedScore>0.3</normalizedScore>
  </data>
</response>
YAML Response
200 OK
status: ok
error: null
data:
  comparative: 0.25
  sentimentText: positive
  sentiment: 3
  isPositive: true
  isNegative: false
  normalizedScore: 0.3
CSV Response
200 OK
keyvalue
comparative0.25
sentimentTextpositive
sentiment3
isPositivetrue
isNegativefalse
normalizedScore0.3

Response Structure

All API responses follow a consistent structure with the following fields:

FieldTypeDescriptionExample
statusstringIndicates whether the request was successful ("ok") or failed ("error")ok
errorstring | nullContains error message if status is "error", otherwise nullnull
dataobject | nullContains the API response data if successful, otherwise null{...}

Learn more about response formats →

Response Data Fields

When the request is successful, the data object contains the following fields:

Response fields marked with Premium are available exclusively on paid plans.View pricing
FieldTypeSample ValueDescription
comparativenumber0.25-
sentimentTextstring"positive"-
sentimentnumber3-
isPositivebooleantrueWhether the sentiment is positive
isNegativebooleanfalseWhether the sentiment is negative
normalizedScorePremiumnumber0.3Sentiment score normalized to -1 to 1 range

Headers

Required and optional headers for Sentiment Analysis API requests:

Header NameRequiredExample ValueDescription
X-API-Keyrequiredyour_api_key_hereYour APIVerve API key. Found in your dashboard under API Keys.
Acceptoptionalapplication/jsonSpecify response format: application/json (default), application/xml, or application/yaml
User-AgentoptionalMyApp/1.0Identifies your application for analytics and debugging purposes
X-Request-IDoptionalreq_123456789Custom request identifier for tracking and debugging requests
Cache-Controloptionalno-cacheControl caching behavior for the request and response

Learn more about request headers →

GraphQL AccessALPHA

Access Sentiment Analysis through GraphQL to combine it with other API calls in a single request. Query only the sentiment analysis data you need with precise field selection, and orchestrate complex data fetching workflows.

Test Sentiment Analysis in the GraphQL Explorer to confirm availability and experiment with queries.

Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.

GraphQL Endpoint
POST https://api.apiverve.com/v1/graphql
GraphQL Query Example
query {
  sentimentanalysis(
    input: {
      text: "I'm so excited that tomorrow is going to be sunny! Can't wait!"
    }
  ) {
    comparative
    sentimentText
    sentiment
    isPositive
    isNegative
    normalizedScore
  }
}

Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.

CORS Support

The Sentiment Analysis API supports Cross-Origin Resource Sharing (CORS) with wildcard configuration, allowing you to call Sentiment Analysis directly from browser-based applications without proxy servers.

CORS HeaderValueDescription
Access-Control-Allow-Origin*Accepts requests from any origin
Access-Control-Allow-Methods*Accepts any HTTP method
Access-Control-Allow-Headers*Accepts any request headers

Browser Usage: You can call Sentiment Analysis directly from JavaScript running in the browser without encountering CORS errors. No proxy server or additional configuration needed.

Learn more about CORS support →

Rate Limiting

Sentiment Analysis API requests are subject to rate limiting based on your subscription plan. These limits ensure fair usage and maintain service quality for all Sentiment Analysis users.

PlanRate LimitDescription
Free5 requests/minHard rate limit enforced - exceeding will return 429 errors
StarterNo LimitProduction ready - standard traffic priority
ProNo LimitProduction ready - preferred traffic priority
MegaNo LimitProduction ready - highest traffic priority

Learn more about rate limiting →

Rate Limit Headers

When rate limits apply, each Sentiment Analysis response includes headers to help you track your usage:

HeaderDescription
X-RateLimit-LimitMaximum number of requests allowed per time window
X-RateLimit-RemainingNumber of requests remaining in the current window
X-RateLimit-ResetUnix timestamp when the rate limit window resets

Handling Rate Limits

Free Plan: When you exceed your rate limit, Sentiment Analysis returns a 429 Too Many Requests status code. Your application should implement appropriate backoff logic to handle this gracefully.

Paid Plans: No rate limiting or throttling applied. All paid plans (Starter, Pro, Mega) are production-ready.

Best Practices for Sentiment Analysis:

  • Monitor the rate limit headers to track your Sentiment Analysis usage (Free plan only)
  • Cache sentiment analysis responses where appropriate to reduce API calls
  • Upgrade to Pro or Mega for guaranteed no-throttle Sentiment Analysis performance

Note: Sentiment Analysis rate limits are separate from credit consumption. You may have credits remaining but still hit rate limits when using Sentiment Analysis on Free tier.

Error Codes

The Sentiment Analysis API uses standard HTTP status codes to indicate success or failure:

CodeMessageDescriptionSolution
200OKRequest successful, data returnedNo action needed - request was successful
400Bad RequestInvalid request parameters or malformed requestCheck required parameters and ensure values match expected formats
401UnauthorizedMissing or invalid API keyInclude x-api-key header with valid API key from dashboard
403ForbiddenAPI key lacks permission or insufficient creditsCheck credit balance in dashboard or upgrade plan
429Too Many RequestsRate limit exceeded (Free: 5 req/min)Implement request throttling or upgrade to paid plan
500Internal Server ErrorServer error occurredRetry request after a few seconds, contact support if persists
503Service UnavailableAPI temporarily unavailableWait and retry, check status page for maintenance updates

Learn more about error handling →

Need help? Contact support with your X-Request-ID for assistance.

Integrate Sentiment Analysis with SDKs

Get started quickly with official Sentiment Analysis SDKs for your preferred language. Each library handles authentication, request formatting, and error handling automatically.

Available for Node.js, Python, C#/.NET, and Android/Java. All SDKs are open source and regularly updated.

Integrate Sentiment Analysis with No-Code API Tools

Connect the Sentiment Analysis API to your favorite automation platform without writing code. Build workflows that leverage sentiment analysis data across thousands of apps.

All platforms use your same API key to access Sentiment Analysis. Visit our integrations hub for step-by-step setup guides.

Frequently Asked Questions

How do I get an API key for Sentiment Analysis?
Sign up for a free account at dashboard.apiverve.com. Your API key will be automatically generated and available in your dashboard. The same key works for Sentiment Analysis and all other APIVerve APIs. The free plan includes 1,000 credits plus a 500 credit bonus.
How many credits does Sentiment Analysis cost?

Each successful Sentiment Analysis API call consumes credits based on plan tier. Check the pricing section above for the exact credit cost. Failed requests and errors don't consume credits, so you only pay for successful sentiment analysis lookups.

Can I use Sentiment Analysis in production?

The free plan is for testing and development only. For production use of Sentiment Analysis, upgrade to a paid plan (Starter, Pro, or Mega) which includes commercial use rights, no attribution requirements, and guaranteed uptime SLAs. All paid plans are production-ready.

Can I use Sentiment Analysis from a browser?
Yes! The Sentiment Analysis API supports CORS with wildcard configuration, so you can call it directly from browser-based JavaScript without needing a proxy server. See the CORS section above for details.
What happens if I exceed my Sentiment Analysis credit limit?

When you reach your monthly credit limit, Sentiment Analysis API requests will return an error until you upgrade your plan or wait for the next billing cycle. You'll receive notifications at 80% and 95% usage to give you time to upgrade if needed.

What's Next?

Continue your journey with these recommended resources

Was this page helpful?