NameMatcher: More resilient matching for real-world names
Previously, if an input could not be parsed into a valid name structure, NameMatcher would fail the request. With Version 11.2.0, NameMatcher now applies an additional, resilient matching step for these edge cases. This results in fewer failed requests and more stable behavior when names are incomplete, oddly formatted, or outside expected patterns.
Examples Below are a few real-world style examples that previously would have caused an exception but can now still produce a reliable match result:
-
"John Doe john.doe99@gmail.com" vs "John Doe"
-
"Anita Gonzales" vs "—, Anita Gonzales"
-
"Jorik Diesinger" vs "und Svea Diesinger, Dr. J"
Overall, 11.2.0 improves operational robustness by handling parsing edge cases gracefully while still returning a match only when the outcome is reliable.
More from the team
Expanded Hungarian Coverage in the NameAPI Database
Few European naming traditions pack as much structure into a name as Hungarian. Besides using the Eastern name order — the family name comes first, the given name second, Hungarian routinely folds honorifics, marital status, and generational markers directly into the name string. That makes accurate parsing both a challenge and a rewarding one, and we've expanded our NameAPI database to meet it.
Read postSoftware Version 11.4.0 released – NameAPI's New Business Detection Module
Telling a company from a person sounds trivial, until you have to do it reliably across millions of real-world names that arrive in every format imaginable. This release is the result of that work: NameAPI now…
Read postIdentifying Titles in Global Name Data
We have updated our NameAPI database with titles from more than 80 cultures. Our services identify and classify academic degrees, official positions, military ranks, and religious honorifics when they appear in a…
Read postTalk to the team
Building name matching, parsing or detection into your stack? We're happy to walk you through how it fits.
Schedule a 30-min call