NameAPI is a web API
to handle people's names
in your software.

News

15.05.2026

Identifying Titles in Global Name Data

We have updated our NameAPI database with titles from more than 80 cultures. Our services identify...


20.04.2026

Database Update: Georgian Names Added

We are pleased to announce the latest expansion of our name database with a comprehensive...


26.02.2026

Enhanced NameAPI Database

We are excited to announce a major update to the NameAPI database, reflecting the extensive...


11.02.2026

Software Version 11.2.0 Deployed

NameMatcher: More resilient matching for real-world names

Previously, if an input could not be...


05.01.2026

2025 Around the World

2025 marked another remarkable year for Optimaize, characterized by significant progress in our...


Email Name Parser


       
Analyzes the email address and attempts to extract a person's name.
See also the Swagger specification.
            
[email protected] => [john, doe]
            
The service attempts to detect several kinds of syntax, such as: Names are not formatted to correct case, they are left the way they appeared in the input.    
               
GET
       
We have integrated Swagger directly into our API.
Visit https://api.nameapi.org/rest/swagger-ui/.

   

Input

       
A syntactically valid email address.
Example: "[email protected]"
An invalid input exception is thrown if the address does not look like an email address.
        
The api-key also known as user-id. Authentication and accounting is performed on the server for this key.
Example: "32d21gc5071d7463ef6064c07ea98cb2-user1"

   

Output

       
Possible values:

The email address belongs to a department (e.g. [email protected]) or is technical (e.g. [email protected])

The email address contains a person's initials such as [email protected].
Note that this answer is a guess, the 2 letters could also have another meaning such as a short given name or surname, or something completely different.

The email address contains a person's name such as [email protected].

The email address uses a pseudonym as the user name such as [email protected] or [email protected].

There is no name in the address, for example [email protected]
The address may be personal or non-personal, can't say (as in UNKNOWN) but it is clear that no name can be found in it.

The email address could not be classified and hence the service failed to extract a name.

       
This is only filled if resultType is PERSON_NAME or INITIALS.
0-n ways of extracting a person's name.
The first entry (if any) is the best, they are ordered by likeliness in descending order.
See EmailNameParserMatch.
{
  "resultType" : "PERSON_NAME",
  "nameMatches" : [ {
    "givenNames" : [ {
      "name" : "peter",
      "nameType" : "NAME"
    } ],
    "surnames" : [ {
      "name" : "johnson",
      "nameType" : "NAME"
    } ],
    "confidence" : 0.9519329699093173
  } ]
}