BLOG

Watch our short video and learn how to upload an Excel file for genderization.

Find a sample Excel file here.

The file can contain up to 50 columns, which means that you can also add custom columns to the Excel file, e.g. with a unique ID. All columns are copied into the target file one by one.

After the file upload, you can chose the column that you need to be checked against our name checker database.

Before the entire Excel file gets processed, you receive a preview of the genderized results.

After the processing of the file against our name checker database has been completed, the file can be downloaded with a single click.

The genderized file will contain an additional column called ga_gender which contains the gender of every row.

Just recently we were mentioned in a comprehensive benchmark and comparison of several available gender inference services.

The team of Gender Gap in Science who conducted the survey assembled a list with more than 7,000 people and their gender and used this list as a basis for the comparison. They combined different error metrics and constraints to define benchmarks for realistic situations (e.g.minimize the proportion of all inaccuracies while keeping the mix-ups between female and male assignments under the threshold of 5%). In all benchmarks, and on almost all sources comprising the test data set, Gender API shows the best results.

"In all our benchmarks, and on almost all sources comprising our test data set, Gender API shows the best results."

This outcome makes us very proud and confirms that conducting not just a simple database lookup, but working with data in detail is the best service we can offer to our customers.

In our third announcement, we would like to introduce our next improvement: Enhanced support for variant forms of spelling.

Sometimes customers enjoy writing their names in different ways. A very common way to do this is using Leetspeak to replace chars with similar glyphs.

For example, the name John is written as J0hn.

To enhance support for names spelt like this, we added a new field called name_sanitized to the API response.

This field gives you the name we found and used for genderization after the name was sanitized in different ways.

The new European General Data Protection Regulation (GDPR) goes into effect on May 25, 2018. We can assure you that all Gender-API.com services will be in full compliance with GDPR by this date.

Gender-API.com provides a Data Processing Agreement (DPA), which enables you to comply with your GDPR obligations.

In addition, we have updated our Privacy Policy and General Terms and Conditions to comply with the new requirements of GDPR.

Good news, during the last couple of months, our team has worked very hard on a full rewrite of our name lookup engine.

We improved so many great details that we couldn't just put them into one single announcement anymore.

So here is our first improvement, we would like to share with you: Reduced split call failure rate.

Our split API is one of our customers' most used features. However, we understand that it can be very tricky to split a full name into its parts.

With the new API version, we are able to reduce the failure rate of all split calls by about 40%. With the old API version, about 90% of the calls returned the correct result. The new version improves this performance to 94% as internal tests show.

To achieve this improvement, we completely refactored our codebase and developed specific micro-services, which can also be more easily improved in the future.

The advancement also includes improved support for countries where Gender-API.com is already heavily in use, for example Germany or the Netherlands. Names with an affix like "Thomas van der Weijden" are now properly resolved into their consisting parts.