Name Match API — Fuzzy Name Comparison
Compare two names and get a confidence score using fuzzy matching. Handles transliterations, abbreviations, and spelling variations.
curl -X GET "https://production.deepvue.tech/v1/name-match?name1=John Doe&name2=John Doe" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer YOUR_API_TOKEN (JWT)" \
-H "x-api-key: YOUR_API_KEY"
import requests
import json
url = "https://production.deepvue.tech/v1/name-match?name1=John Doe&name2=John Doe"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN (JWT)",
"x-api-key": "YOUR_API_KEY"
}
response = requests.get(url, headers=headers)
print(response.json())
const response = await fetch("https://production.deepvue.tech/v1/name-match?name1=John Doe&name2=John Doe", {
method: "GET",
headers: {
"Content-Type": "application/json",
"Authorization": "Bearer YOUR_API_TOKEN (JWT)",
"x-api-key": "YOUR_API_KEY"
}
});
const data = await response.json();
console.log(data);
package main
import (
"fmt"
"net/http"
)
func main() {
req, err := http.NewRequest("GET", "https://production.deepvue.tech/v1/name-match?name1=John Doe&name2=John Doe", nil)
if err != nil {
panic(err)
}
req.Header.Set("Content-Type", "application/json")
req.Header.Set("Authorization", "Bearer YOUR_API_TOKEN (JWT)")
req.Header.Set("x-api-key", "YOUR_API_KEY")
client := &http.Client{}
resp, err := client.Do(req)
if err != nil {
panic(err)
}
defer resp.Body.Close()
fmt.Println("Response Status:", resp.Status)
}
require 'net/http'
require 'json'
uri = URI('https://production.deepvue.tech/v1/name-match?name1=John Doe&name2=John Doe')
http = Net::HTTP.new(uri.host, uri.port)
http.use_ssl = true
request = Net::HTTP::Get.new(uri)
request['Content-Type'] = 'application/json'
request['Authorization'] = 'Bearer YOUR_API_TOKEN (JWT)'
request['x-api-key'] = 'YOUR_API_KEY'
response = http.request(request)
puts response.body
{
"code": 200,
"sub_code": "SUCCESS",
"message": "Request processed successfully",
"timestamp": 1711688769712,
"transaction_id": "b6b95b94-2c58-4dc3-8de5-969d52d57938",
"data": {
"cleaned_name1": "Chandra Shekhar Kandpal",
"cleaned_name2": "Chandra Shekhar Kandppal",
"score": 98,
"tokenwise_match": [
{
"first_name1": "Chandra",
"first_name2": "Chandra",
"score": 100
},
{
"middle_name1": "Shekhar",
"middle_name2": "Shekhar",
"score": 100
},
{
"last_name1": "Kandpal",
"last_name2": "Kandppal",
"score": 93
}
]
}
}
{
"detail": "Inactive client_id"
}
{
"detail": "Not authenticated"
}
{
"detail": "Not a valid token"
}
{
"code": 422,
"timestamp": 1711688769712,
"transaction_id": "b6b95b94-2c58-4dc3-8de5-969d52d57938",
"sub_code": "EMPTY_NAME",
"message": "Name1 or Name2 is empty"
}
{
"detail": "Internal Server Error"
}
{
"code": null,
"timestamp": null,
"transaction_id": "string",
"message": "Source Unavailable"
}
/v1/name-match
ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .
The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.
Request Preview
Response
Response will appear here after sending the request
Authentication
Bearer token (JWT). ACCESS_TOKEN generated from the authorize endpoint. Should be included in the header as Bearer .
API Key for authentication. The CLIENT_SECRET provided to you. This header parameter is required for authentication purposes.
Query Parameters
Responses
Overview
The Name Match API involves comparing patterns against the text to identify matches or similarities, and gives a score for that. This tool addresses scenarios involving substantial name variations. You submit pairs of names for verification and receive a matching determination plus numerical scoring.
How it works
The API processes two name inputs and returns:
- Cleaned and standardized versions of both names
- Overall match score
- Token-wise analysis breaking down individual name components (first, middle, last names) with individual scores
Last updated 4 weeks ago
Built with Documentation.AI