Overview
Love Calculator works by analyzing the names provided and calculating the love compatibility percentage. It uses advanced algorithms to calculate the love compatibility between two names and returns the love compatibility percentage.
Live Test Love Calculator API →
Endpoint
One host, one path per API. The block below shows this call in four languages; every one of them is the same HTTP request. Making requests covers the timeouts, retries and parameter rules that apply to all of them. The SDKs wrap the same call in a typed client.
curl "https://api.apiverve.com/v1/lovecalculator?name1=John&name2=Jane" \
-H "x-api-key: your_api_key_here"const res = await fetch('https://api.apiverve.com/v1/lovecalculator?name1=John&name2=Jane', {
headers: { 'x-api-key': 'your_api_key_here' },
});
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const { data } = await res.json();
console.log(data);import requests
res = requests.get(
"https://api.apiverve.com/v1/lovecalculator?name1=John&name2=Jane",
headers={"x-api-key": "your_api_key_here"},
timeout=15,
)
res.raise_for_status()
print(res.json()["data"])package main
import (
"fmt"
"io"
"net/http"
)
func main() {
req, _ := http.NewRequest("GET", "https://api.apiverve.com/v1/lovecalculator?name1=John&name2=Jane", nil)
req.Header.Set("x-api-key", "your_api_key_here")
res, err := http.DefaultClient.Do(req)
if err != nil {
panic(err)
}
defer res.Body.Close()
out, _ := io.ReadAll(res.Body)
fmt.Println(string(out))
}Replace your_api_key_here with the key from your dashboard. When the inputs arrive as a list rather than one at a time, batch requests run up to 200 of them through this same API in a single call.
Authentication
Send your key in the x-api-key header. That is the only auth step — there is no token exchange and no per-endpoint scope to configure. Authentication covers creating, rotating and revoking keys.
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.
Parameters
Sent in the query string. Premium parameters are accepted on every plan but only take effect on plans that include them.
| Parameter | Type | Description |
|---|---|---|
name1Required | string | The first name to calculate love compatibility length 0–100 |
name2Required | string | The second name to calculate love compatibility length 0–100 |
Response
Every API returns the same three top-level keys, so one response handler covers your whole integration: status, error and data. Only data changes shape. Response format covers the envelope, the other output formats and how premium fields are withheld.
{
"status": "ok",
"error": null,
"data": {
"name1": "Jane",
"name2": "John",
"lovePercentage": "62%",
"response": "You have good chemistry. Keep getting to know each other and see where it leads.",
"additionalText": "The love percentage between Jane and John is 62%."
}
}
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 |
|---|---|---|---|
name1 | string | "Jane" | The first name provided for compatibility calculation |
name2 | string | "John" | The second name provided for compatibility calculation |
lovePercentage | string | "62%" | Calculated love compatibility percentage between two names |
responsePremium | string | "You have good chemistry. Keep getting to know each other and see where it leads." | Detailed compatibility analysis and advice for the couple |
additionalText | string | "The love percentage between Jane and John is 62%." | Additional information and summary about love percentage |
Errors
Read the HTTP status first, then error for the specific reason. The body names the parameter that has to change. Error handling covers the full status list and which of them are worth retrying.
| Status | Meaning | What to do |
|---|---|---|
400 | Input was rejected | Read error; it names the parameter. |
401 | Key missing or invalid | Check the header name and the key value. |
403 | Key valid, but not permitted | A key restriction or IP allow-list; see key scoping. |
429 | Rate limited, or out of credits | Read error to tell them apart; see rate limits. |
Use cases
- Dating App Icebreakers
- To spark new conversations, dating apps show compatibility percentages between mutual matches before users send their first message.
- Interactive Social Quizzes
- Digital publishers generate viral couple tests where readers enter two names to receive a match percentage and shareable relationship summary.
- Community Discord Bots
- When server members run pairing commands, chat bots calculate instant compatibility percentages to create lighthearted engagement across social channels.
- Holiday Marketing Campaigns
- Drive seasonal traffic around Valentine's Day by letting shoppers test name pairings on promotional landing pages before revealing discount codes.
Other ways to use Love Calculator
Set up Love Calculator on APIVerve, or reach the same source a different way. Your APIVerve account and credits work on all of them — one key, one balance.
Related
More in Entertainment: