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



Bosnian names: Echoes of Diversity and Heritage

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


Larger Name Database

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


Diving Deeper into Latin American Names

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


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...


Software Version 10.2.0 Deployed

A software update has been installed on our servers which can handle more personal names and detect...


Generic Person Genderizer

Attempts to detect the person's gender based on the inputs, especially the person's name.



See person.
See context.
(todo: add example)



Possible values:

The person is clearly 'male'.

The person is clearly 'female'.

Can be either male or female. See malePercent.

No gender could be computed, but better intelligence should be able to tell the gender. An example is a name input of which we have never heard before.

From the given data it is or seems impossible to tell the gender.
For example all terms are gender-inapplicable, or there are no names at all. Thus this differs from NEUTRAL where something is clearly known to be neutral.

There are conflicting genders in the given data.
Example: "Mr Daniela Miller" (salutation vs. given name).
The input data must be manually reviewed. It is impossible and useless to make a guess (garbage in would only cause garbage out).

If neutral (otherwise null) then this may be specified (but does not have to be), 0-100, the remaining % are for female.
0-100 where 100 is the best.
(todo: add example)