Love Calculator is a simple tool for calculating love compatibility. It returns the love compatibility percentage between two names.
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": {
// Love Calculator response payload
}
}
About the Love Calculator API
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.
What people use it for
- Relationships
- Use the Love Calculator API to calculate love compatibility for relationships. Use the data to assess compatibility, strengthen bonds, and improve communication
- Dating Apps
- Calculate love compatibility by using the Love Calculator API for dating apps. Use the data to match users, suggest partners, and enhance user experience
- Social Media
- Use the Love Calculator API to calculate love compatibility for social media. Use the data to engage users, create content, and drive interactions
- Entertainment
- Calculate love compatibility by using the Love Calculator API for entertainment. Use the data to create quizzes, generate results, and entertain audiences
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 Love Calculator
Same data, same APIVerve account, same credit balance — one key works on all of them.
What does the Love Calculator API do?
How do I authenticate Love Calculator API requests?
How much does the Love Calculator API cost?
How fast is the Love Calculator API?
What response formats does the Love Calculator API support?
What HTTP method does the Love Calculator API use?
Request parameters — GET /v1/lovecalculator
Sent in the query string. 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 |
|---|---|---|---|
name1Required | string | John | The first name to calculate love compatibility |
name2Required | string | Jane | The second name to calculate love compatibility |
curl "https://api.apiverve.com/v1/lovecalculator?name1=John&name2=Jane" \
-H "x-api-key: YOUR_API_KEY"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. |
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 — GET /v1/lovecalculator
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": {
"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 |
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 — 2 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 | Love Calculator calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 100 | Free |
| Starter | $29.99 | 200,000 | 100,000 | $0.30 |
| Pro | $99.99 | 1,000,000 | 500,000 | $0.20 |
| Mega | $299.99 | 4,000,000 | 2,000,000 | $0.15 |
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 — GET /v1/lovecalculator
No SDK to install — this is a plain HTTPS call to /v1/lovecalculator 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/lovecalculator" \
-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 — GET /v1/lovecalculator
Install the Node.js SDK, then call the Love Calculator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/lovecalculatorconst res = await fetch("https://api.apiverve.com/v1/lovecalculator", {
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 — GET /v1/lovecalculator
Install the Python SDK, then call the Love Calculator API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
pip install apiverve-lovecalculatorimport requests
res = requests.get(
"https://api.apiverve.com/v1/lovecalculator",
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 — GET /v1/lovecalculator
Install the C# / .NET SDK, then call the Love Calculator 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.LoveCalculatorusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/lovecalculator");
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 — GET /v1/lovecalculator
No SDK to install — this is a plain HTTPS call to /v1/lovecalculator 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/lovecalculator", 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 — GET /v1/lovecalculator
No SDK to install — this is a plain HTTPS call to /v1/lovecalculator 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/lovecalculator");
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 — GET /v1/lovecalculator
No SDK to install — this is a plain HTTPS call to /v1/lovecalculator 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/lovecalculator")
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 Love Calculator 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 — Love Calculator 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 Love Calculator API.
Entertainment
- Advice Generator
- Bucket List
- Charades Generator
- Chess Move Validator
- Chuck Norris Jokes
- Compliment Generator
- D&D Generator
- Dad Jokes
- Fortune Teller
- Historical Events
- Love Calculator
- Magic 8-Ball
- Music Note Generator
- Never Have I Ever
- Pictionary Generator
- Random Facts
- Random Joke
- Random Pun
- Random Quote
- Scrabble Word Scorer
- Sudoku Generator
- Trivia Generator
- Truth or Dare
- Wordle Helper
Related articles
All articles →
Python API Tutorial: Your First APIVerve Call10 lines of Python. That's all it takes to call 300+ APIs. Here's the complete quickstart for Python developers.Read
REST vs GraphQL: Which Should You Use?Skip the theory. Here's when to use REST endpoints and when GraphQL actually makes sense.Read
Complete Guide to API Testing with PostmanMaster API testing with Postman. Learn collections, environments, automated tests, and debugging techniques.Read