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

News

26.04.2024

Enhanced NameAPI Database

We've updated our NameAPI database to better handle names that include professions. We have added...


12.04.2024

Bosnian names: Echoes of Diversity and Heritage

Bosnia and Herzegovina stands out in Europe for its remarkable diversity, being a country where...


29.03.2024

Larger Name Database

We are pleased to announce a new update to our database, which now features a broader range of...


01.03.2024

Diving Deeper into Latin American Names

From the indigenous communities of the Andes to the Afro-Caribbean rhythms of the Caribbean coast,...


16.02.2024

Swagger-UI: The New and Improved Way to Use Our REST API

We are happy to announce that we have added a new feature to our REST API: Swagger-UI, which allows...


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
  } ]
}