Text Similarity API
Overview
To use Text Similarity, you need an API key. You can get one by creating a free account and visiting your dashboard.
POST Endpoint
https://api.apiverve.com/v1/textsimilarityExample
How to call the Text Similarity API in different programming languages.
curl -X POST \
"https://api.apiverve.com/v1/textsimilarity" \
-H "X-API-Key: your_api_key_here" \
-H "Content-Type: application/json" \
-d '{
"text1": "I'm so excited that tomorrow is going to be sunny! Can't wait!",
"text2": "We're pretty excited about the weather tomorrow. It's going to be sunny!"
}'const response = await fetch('https://api.apiverve.com/v1/textsimilarity', {
method: 'POST',
headers: {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
},
body: JSON.stringify({
"text1": "I'm so excited that tomorrow is going to be sunny! Can't wait!",
"text2": "We're pretty excited about the weather tomorrow. It's going to be sunny!"
})
});
const data = await response.json();
console.log(data);import requests
headers = {
'X-API-Key': 'your_api_key_here',
'Content-Type': 'application/json'
}
payload = {
"text1": "I'm so excited that tomorrow is going to be sunny! Can't wait!",
"text2": "We're pretty excited about the weather tomorrow. It's going to be sunny!"
}
response = requests.post('https://api.apiverve.com/v1/textsimilarity', headers=headers, json=payload)
data = response.json()
print(data)package main
import (
"fmt"
"io"
"net/http"
"bytes"
"encoding/json"
)
func main() {
payload := map[string]interface{}{
"text1": "I'm so excited that tomorrow is going to be sunny! Can't wait!",
"text2": "We're pretty excited about the weather tomorrow. It's going to be sunny!"
}
jsonPayload, _ := json.Marshal(payload)
req, _ := http.NewRequest("POST", "https://api.apiverve.com/v1/textsimilarity", 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))
}{
"status": "ok",
"error": null,
"data": {
"simiarity": 45.83,
"similarityCaseSensitive": 47.22,
"difference": {
"count": 7,
"percentage": 58.33
}
}
}Authentication
The Text Similarity API requires authentication via API key. Include your API key in the request header:
X-API-Key: your_api_key_hereInteractive API Playground
Test the Text Similarity API directly in your browser with live requests and responses.
Parameters
The following parameters are available for the Text Similarity API:
Check Similarity
| Parameter | Type | Required | Description | Default | Example |
|---|---|---|---|---|---|
text1 | string | required | The first text to compare. Must be less than 1000 characters | - | |
text2 | string | required | The second text to compare. Must be less than 1000 characters | - |
Response
The Text Similarity API returns responses in JSON, XML, YAML, and CSV formats. The JSON response is shown in the Example section above; alternative formats below.
Other Response Formats
<?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>
<simiarity>45.83</simiarity>
<similarityCaseSensitive>47.22</similarityCaseSensitive>
<difference>
<count>7</count>
<percentage>58.33</percentage>
</difference>
</data>
</response>
status: ok
error: null
data:
simiarity: 45.83
similarityCaseSensitive: 47.22
difference:
count: 7
percentage: 58.33
| key | value |
|---|---|
| simiarity | 45.83 |
| similarityCaseSensitive | 47.22 |
| difference | {count:7,percentage:58.33} |
Response Structure
All API responses follow a consistent structure with the following fields:
| Field | Type | Description | Example |
|---|---|---|---|
status | string | Indicates whether the request was successful ("ok") or failed ("error") | ok |
error | string | null | Contains error message if status is "error", otherwise null | null |
data | object | null | Contains 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:
| Field | Type | Sample Value | Description |
|---|---|---|---|
simiarity | number | - | |
similarityCaseSensitive | number | - | |
difference | object | - | |
â”” count | number | - | |
â”” percentage | number | - |
Headers
Only X-API-Key is required. Optional headers include Accept for response format negotiation (JSON, XML, or YAML), User-Agent, and X-Request-ID for request tracing. See all request headers →
GraphQL AccessALPHA
Access Text Similarity through GraphQL to combine it with other API calls in a single request. Query only the text similarity data you need with precise field selection, and orchestrate complex data fetching workflows.
Credit Cost: Each API called in your GraphQL query consumes its standard credit cost.
POST https://api.apiverve.com/v1/graphqlquery {
textsimilarity(
input: {
text1: "I'm so excited that tomorrow is going to be sunny! Can't wait!"
text2: "We're pretty excited about the weather tomorrow. It's going to be sunny!"
}
) {
simiarity
similarityCaseSensitive
difference {
count
percentage
}
}
}Note: Authentication is handled via the x-api-key header in your GraphQL request, not as a query parameter.
CORS Support
The Text Similarity API accepts cross-origin requests from any origin, so it can be called directly from browser-based applications without a proxy. See CORS support →
Rate Limiting
Text Similarity requests are throttled per minute on the Free plan and unthrottled on paid plans. Exceeding the limit returns 429 Too Many Requests; rate-limit usage is reported in the X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset response headers. See per-plan limits and best practices →
Error Codes
The Text Similarity API uses standard HTTP status codes — 200 on success, 400 for invalid parameters, 401 for missing or invalid keys, 403 for insufficient credits, 429 for rate-limit exhaustion, and 500/503 for server-side issues. Each error response includes an X-Request-ID header you can quote when contacting support. See full error handling guide →
SDKs for Text Similarity
Official Text Similarity packages on npm, PyPI, NuGet, and JitPack — plus a Postman collection and an OpenAPI spec. See the SDK guide →
No-Code Integrations
Text Similarity works with Zapier, Make, Pipedream, n8n, and Power Automate using the same API key. See setup guides →
Frequently Asked Questions
How do I get an API key for Text Similarity?
How many credits does Text Similarity cost?
Each successful Text Similarity 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 text similarity lookups.
Can I use Text Similarity in production?
The free plan is for testing and development only. For production use of Text Similarity, 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 Text Similarity from a browser?
What happens if I exceed my Text Similarity credit limit?
When you reach your monthly credit limit, Text Similarity 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.








