For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Support
API ReferenceDocsRelease notes
API ReferenceDocsRelease notes
  • Analytics API Reference
        • POSTMatch names
        • GETMatch names supported languages
Support
LogoLogo
Login
Login
Analytics API ReferenceMatch NamesName Similarity

Match names

POST
/name-similarity
POST
/rest/v1/name-similarity
$curl -X POST https://analytics.babelstreet.com/rest/v1/name-similarity \
> -H "X-BabelStreetAPI-Key: <apiKey>" \
> -H "Content-Type: application/json" \
> -d '{
> "name1": {
> "text": "Michael Jackson"
> },
> "name2": {
> "text": "迈克尔·杰克逊"
> }
>}'
200Successful
1{
2 "score": 1.1
3}
Names are complex to match because of the large number of variations that occur within a language and across languages. Match can identify variations between names including, but not limited to, typographical errors, phonetic spelling variations, transliteration differences, initials, and nicknames. Name Similarity compares two entity names (Person, Location, or Organization) and returns a match score from 0 to 1. The match score is a relative indication of how similar the match is; it is not an absolute value. When comparing different name matches, the relative values of the scores are more relevant than the actual score. Similar name matches in different languages may generate different match scores. You should always specify the entity type when known. Name Similarity applies parameter override tables and other tools specific to the entuty type. If you con't specify an entity type, the type PERSON will be used. > Although not required, we strongly recommend specifying the source language when known, for better accuracy. If you do not specify the source language, the name similarity algorithm will guess the language.
Was this page helpful?

Match names supported languages

Next
Built with

Names are complex to match because of the large number of variations that occur within a language and across languages. Match can identify variations between names including, but not limited to, typographical errors, phonetic spelling variations, transliteration differences, initials, and nicknames.

Name Similarity compares two entity names (Person, Location, or Organization) and returns a match score from 0 to 1.

The match score is a relative indication of how similar the match is; it is not an absolute value. When comparing different name matches, the relative values of the scores are more relevant than the actual score. Similar name matches in different languages may generate different match scores.

You should always specify the entity type when known. Name Similarity applies parameter override tables and other tools specific to the entuty type. If you con’t specify an entity type, the type PERSON will be used.

Although not required, we strongly recommend specifying the source language when known, for better accuracy. If you do not specify the source language, the name similarity algorithm will guess the language.

Authentication

X-BabelStreetAPI-Keystring
API Key authentication via header
OR
X-RosetteAPI-Keystring
API Key authentication via header

Request

This endpoint expects an object.
name1objectRequired
name2objectRequired
parameterslist of objectsOptional
Parameter name and value to change score calculation.

Response

OK
scoredouble
a name matcher result