Score the similarity between any two pieces of text.
Levenshtein Distance calculates the minimum number of single-character edits needed to transform one string into another.
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": {
"distance": 3,
"similarity": 57.14,
"matchLevel": "medium",
"string1Length": 6,
"string2Length": 7,
"string1": "kitten",
"string2": "sitting"
}
}
About the Levenshtein Distance API
A Levenshtein distance API for measuring how different two strings are. Send any two strings and get back the edit distance between them, a similarity percentage from 0 to 100 and a plain match level you can act on without choosing thresholds yourself. Ideal for spell checking, fuzzy matching, plagiarism detection, and any application requiring string similarity measurement.
Edit distance is the number of single-character insertions, deletions and substitutions needed to turn one string into the other: "kitten" and "sitting" are three edits apart. That makes it a practical way to catch near-duplicate records, match a typed name against a list, suggest the closest valid command or product code, and flag text that has been lightly altered.
Every plan, including the Free plan, returns the distance, the similarity percentage and the match level. Paid plans also echo both input strings and return their lengths, which is useful when you log comparisons or batch them and need each result to carry its own context.
How it works
Levenshtein Distance computes the classic edit distance between string1 and string2 with dynamic programming. Each cell holds the cheapest way to turn a prefix of one string into a prefix of the other, where an insertion, a deletion and a substitution each cost 1 and a matching character costs 0. distance is the value in the final cell. Transpositions are not a single operation, so "ab" to "ba" is a distance of 2, not 1.
The comparison is exact and character-by-character: it is case-sensitive, spaces and punctuation count, and characters are compared as JavaScript string units, so an emoji or other character outside the Basic Multilingual Plane counts as two. Lowercase or trim the strings yourself if you want "Apple" and "apple " to match.
similarity is (1 minus distance divided by the length of the longer string) times 100, rounded to two decimals. matchLevel is derived from that number: exactly 100 is exact, 80 or above high, 50 or above medium, 20 or above low, and anything lower none. Because similarity is normalized by length, one edit in a long string scores higher than one edit in a short one; use distance when you need an absolute threshold such as "at most two typos".
string1Length and string2Length are the lengths of the inputs as received, and string1 and string2 echo them back; these four fields are null on the Free plan. Each string may be up to 10,000 characters; longer input returns a 400. Computation time grows with the product of the two lengths, so a pair at the limit takes a fraction of a second.
What people use it for
- Spell Checking
- Calculate similarity between misspelled words and dictionary entries
- Fuzzy Search
- Implement approximate string matching for search engines
- Plagiarism Detection
- Measure text similarity for detecting copied content
- Data Deduplication
- Identify near-duplicate records in databases
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 Levenshtein Distance
Same data, same APIVerve account, same credit balance — one key works on all of them.
How far does the Starter plan go for string comparisons?
How long can the text inputs be?
Are the input strings and character lengths included on the Free plan?
What similarity metrics does each comparison return?
Can I use this for spell checking and fuzzy search?
Request parameters — POST /v1/levenshteindistance
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 |
|---|---|---|---|
string1Required | string | kitten | First string to compare (max 10,000 characters) length 0-10000 |
string2Required | string | sitting | Second string to compare (max 10,000 characters) length 0-10000 |
curl -X POST "https://api.apiverve.com/v1/levenshteindistance" \
-H "x-api-key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"string1":"kitten","string2":"sitting"}'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/levenshteindistance
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": {
"distance": 3,
"similarity": 57.14,
"matchLevel": "medium",
"string1Length": 6,
"string2Length": 7,
"string1": "kitten",
"string2": "sitting"
}
}
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 |
|---|---|---|---|
distance | number | 3 | The Levenshtein edit distance between the two strings |
similarity | number | 57.14 | Similarity percentage from 0 to 100 |
matchLevel | string | "medium" | Similarity level: exact, high, medium, low, or none |
string1LengthPremium | number | 6 | Length of the first string |
string2LengthPremium | number | 7 | Length of the second string |
string1Premium | string | "kitten" | The first input string |
string2Premium | string | "sitting" | The second input string |
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 — 1 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 | Levenshtein Distance calls | Per 1,000 calls |
|---|---|---|---|---|
| Free | Free | 200 | 200 | Free |
| Starter | $29.99 | 200,000 | 200,000 | $0.15 |
| Pro | $99.99 | 1,000,000 | 1,000,000 | $0.10 |
| Mega | $299.99 | 4,000,000 | 4,000,000 | $0.07 |
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/levenshteindistance
No SDK to install — this is a plain HTTPS call to /v1/levenshteindistance 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/levenshteindistance" \
-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/levenshteindistance
Install the Node.js SDK, then call the Levenshtein Distance API with your key. The client wraps the same HTTPS request, so anything it returns is what the endpoint returns.
npm install @apiverve/levenshteindistanceconst res = await fetch("https://api.apiverve.com/v1/levenshteindistance", {
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/levenshteindistance
No SDK to install — this is a plain HTTPS call to /v1/levenshteindistance with your key in the x-api-key header. Swap in a real key and it runs as-is.
import requests
res = requests.get(
"https://api.apiverve.com/v1/levenshteindistance",
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/levenshteindistance
Install the C# / .NET SDK, then call the Levenshtein Distance 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.LevenshteinDistanceusing var client = new HttpClient();
client.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var json = await client.GetStringAsync("https://api.apiverve.com/v1/levenshteindistance");
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/levenshteindistance
No SDK to install — this is a plain HTTPS call to /v1/levenshteindistance 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/levenshteindistance", 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/levenshteindistance
No SDK to install — this is a plain HTTPS call to /v1/levenshteindistance 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/levenshteindistance");
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/levenshteindistance
No SDK to install — this is a plain HTTPS call to /v1/levenshteindistance 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/levenshteindistance")
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 Levenshtein Distance 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 — Levenshtein Distance 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 Levenshtein Distance API.
Text Processing
- Acronym Expander
- Anagram Detector
- Antonym Finder
- Cron Expression Parser
- Data Masking
- Did You Mean
- Emoji Decorator
- Gibberish Detector
- Grammar Check
- ISBN Validator
- JSON Schema Validator
- Keyword Extractor
- Leet Speak
- Levenshtein Distance
- Line Sorter
- Markdown Link Extractor
- Palindrome Checker
- Parts Of Speech
- Phonetic Encoder
- Pig Latin
- Profanity Filter
- Reading Time Calculator
- Regex Tester
- Remove Punctuation
- Reverse Text
- Rhyming Words
- Slugify
- Spell Checker
- Syllable Counter
- Tax ID Validator
- Tense Converter
- Text Language
- Text Lemmatizer
- Text Readability Score
- Text Similarity
- Text Styler
- Text Summarizer
- Text to Emoji
- Title Case Converter
- Translator
- Vowel Counter
- Website Readability
- Word Lexicon Analyzer
- Word Opposites
- Word Pronunciation
Related articles
All articles →
Take Your App Multilingual (No Rewrite)Add language support to an existing app without rearchitecting. Practical strategies for translation, detection, and localization.Read
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
7 Content Moderation Mistakes That Sink AppsYour app allows user content. Here are the moderation mistakes that get apps pulled from stores.Read