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



Slovene names: Unraveling a Fascinating Blend of Cultures

Did you know that Slovenian’s great variety of names reflects the country’s fascinating blend of...


Expanding Horizons: Introducing Fresh Additions to Our Name Database!

Collaborating diligently with natives worldwide, our research team has successfully integrated new...


Introducing the Latest Version: Java Client Library 6.0.0

The new and noteworthy feature of the Java™ Client Library 6.0.0 is its migration to Java 17.


Discover Our Name Parser Service

Efficiently and accurately analyze personal names, regardless of cultural or linguistic variations,...


Bulgarian Names: Stories of Tradition and Identity

Did you know that within the Bulgarian culture, name days often hold greater significance and are...



The ping command simply pings the server and, on success, gets a "pong" back.
See also the Swagger specification.
Ping can be used either manually or by code to check for service availability and response time.
The command passes through all interceptors (authentication, load balancing etc.) to a target server that actually executes nameapi requests. All standard behavior applies including request prioritization and request limits per contract. The only difference is that the minimal response time used on free accounts is not applied.



The api-key also known as user-id. Authentication and accounting is performed on the server for this key.
Example: "32d21gc5071d7463ef6064c07ea98cb2-user1"