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



Version 5.3 Deployed

New version 5.3 available.


Version 5.3 release candidate is online

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


Version 5.2 Deployed

As announced, the new version has been installed.


Version 5.2 release candidate is online

More names, more cultures.


Version 5.1 Deployed

As announced, the new version has been installed.

Service Availability


A high service uptime is one of our main goals. We aim to achieve the five nines: 99.999% availability - that is a maximum of 5.26 minutes of downtime per year. Almost all requests are served within a fraction of a second.

Every part of the service has been designed from the ground up to avoid single point of failures:

  • Multiple server locations.
    When one fails, your client program can failover to another one.
  • Multiple installations at the same server location for load balancing and automatic (transparent) failover.
    This allows us to update a system with a new version, or perform other software or hardware maintenance, while remaining operational.
  • State of the art host centers.
    The host centers we choose for our dedicated servers provide redundant power plus UPS and diesel, redundant network providers, access control, fire suppression, air conditioning. We use dedicated hardware, not cloud hosting, because we're in full control of the chosen non-shared hardware. This gives us the consistent high performance that our services need.
  • Multiple domain names with separate DNS servers. Domains registered at separate registrars with long expiration dates.
  • Our software updates go through a thorough testing cycle before being deployed.


What you can do to maximize the success rate for API calls: 

  • Use reliable internet connections
  • Auto-retry a failed request
  • Auto-retry to alternate host center (switch url).

The auto-retry feature is built into the NameAPI Java client library.