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

News

30.11.2017

Version 5.3 Deployed

New version 5.3 available.


15.11.2017

Version 5.3 release candidate is online

More names, more cultures and a new web service: Risk Detector.


16.03.2017

Version 5.2 Deployed

As announced, the new version has been installed.


02.03.2017

Version 5.2 release candidate is online

More names, more cultures.


01.11.2016

Version 5.1 Deployed

As announced, the new version has been installed.


Email Name Parser


       
Analyzes the email address and attempts to extract a person's name.
See also the Swagger specification.
            
john.doe@example.com => [john, doe]
            
The service attempts to detect several kinds of syntax, such as:
  • peter.johnson@example.com
  • peter.a.johnson@example.com
  • peterjohnson@example.com
  • pjohnson@example.com
  • peterj@example.com
  • peter@example.com
  • johnson@example.com
  • johnson.peter@example.com
  • johnsonpeter@example.com
Names are not formatted to correct case, they are left the way they appeared in the input.    
               
GET
       

   

Input

       
A syntactically valid email address.
Example: "john.doe@example.com"
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. accounting@example.com) or is technical (e.g. hostmaster@example.com)

The email address contains a person's initials such as ab@example.com.
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 john.doe@example.com.

The email address uses a pseudonym as the user name such as maverick1986@example.com or happyhippo@example.com.

There is no name in the address, for example x2000@example.com
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
  } ]
}