BLOG

If you're an advanced user with a high request volume, you can switch to our new API V2.0 endpoint. The unified API offers way more speed and a more robust interface when querying multiple names in a single request.

Query up to 100 names in a single request

You can query up to 100 names in a single request and you can even mix the input data. For example, one name can be submitted with a country code, whereas another name can be submitted without a country code - all in a single query.

Up to 200 times faster

We developed this new endpoint with a handfull of our biggest customers to met their requirements in speed, stability and scaling. Compared to requests querying a single name only, this API endpoint is up to 200 times faster.

More secure

You can now generate unique authentication tokens for all your projects. These tokens can be revoked at any time if necessary. You can manage your authentication tokens here.

Take a test drive

To give you an idea of how easy it is to communicate with this JSON API endpoint, you can find an example on codepen.io.

Codepen.io will connect to your Gender-API.com account and give you a basic example of how the input data looks like and what the response will be.

Query a single name

Query multiple names

Wasn't that easy? We just added square brackets around the two name objects and this tells our API "please also return the result as an array". You can query up to 100 names in a single REST API call.

You can also mix up gender queries for email addresses and for name. Genderizing an email address is as simple as genderizing a first name. Simply add an email field to the request JSON instead of a first_name field. The technology behind determining the gender of an email address is much mor difficult, though. Different processing algorithms work together to give you the best results possible.

Is the existing V1.0 API deprecated now?

No, V1.0 delivers a very easy to integrate interface while V2.0 better suites customers with a large request volume need. Both will be developed and maintained equally.

View the API docs

We hope we were able to give you a short overview and a quick introduction to our new Genderize API. You can find all the technical information, advanced functions und examples in our API docs section. If you have some questions feel free to contact our team.

On 14 September 2019, new requirements for authenticating online payments will be introduced in Europe as part of the second Payment Services Directive (PSD2) to make online payments more secure.

We have taken all steps to make the transition as easy as possible for you. Most customers do not need to do anything, but for some customers banks will require additional authentication.

In this case you will receive an additional email from us asking you to add your credit card again using a second factor for authentication (e.g. SMS, Tan, App). Payments will then work as before.