Genderize API reference

A simple API that predicts the gender of a person based on a first name

The Genderize API allows you to check the statistical probability of a name being male or female.

The API exposes a single endpoint that accepts a name and returns a payload with the prediction. It uses query parameters for requests and returns JSON-encoded responses.

The API is free for up to 100 names/day. No sign-up or API key is needed. So go ahead and try it out. You can sign up for an API key if you need more requests.

We support batch processing to reduce the overhead of many HTTP calls.

The endpoint also supports localization, allowing you to scope the gender prediction to a single country for higher accuracy.

The API is built for high-volume processing, and as such, there is no rate limiting except your daily or monthly limit. You can keep track of that through rate-limiting headers or your account.

Client libraries

Not looking to write your own client code? Our amazing community has open sourced libraries and SDK's for almost every programming language.

Python icon


R icon


Javascript icon


PHP icon


Go icon


C# icon


Ruby icon


Scala icon


Java icon


Basic Usage

Predicting the gender of a single name

You should use a single first name as the name parameter. There are many approaches to splitting names, and none are perfect. To keep things transparent, the API will make no such attempts.

The response includes a gender, probability, and a count. The probability indicates the ratio of males to females in our dataset, and the count indicates the amount of data rows examined for the response. You can read more about our data here.

It's worth noting that demographics can influence naming conventions, so check out how to classify genders from a specific country.

Request Try me

name string

The processed name.

gender string

Whether the predicted gender is male or female.

probability float

The certainty with which the gender was predicted.

count integer

The amount of datapoints examined for the prediction.


Classification in the scope of a specific country

Naming conventions can rely heavily on demographics, so specifying a country for the lookup will, in many cases, make the prediction better.

The API accepts an optional country_id parameter. The API will return a prediction specifically for the provided country when used. We recommend using it whenever you have the data available.

The dataset might be smaller for some countries, so it is worth checking the count and redoing the request globally if it's too low.

The service follows ISO 3166-1 alpha-2 for country codes. See our list of supported countries to understand the coverage for each country.

Request Try me
Request Try me
Batch Usage

Checking the gender of multiple names in a request

The API allows you to infer the gender of up to ten names per request. To do so, send a list of names as the name parameter. The response will be a list of predictions.

Using localization on a batch request will apply the given country_id to every name in the batch.

Each name will count as a request towards rate limiting. If you don't have enough requests to process every name, an error will be returned.

Request[]=peter&name[]=lois&name[]=stewie Try me
Rate Limiting

Managing the rate limits of the API

The API is free to use for up to 100 requests/day. If you need to do more predictions than that, you can obtain an API key from the store.

You should append the key to every request using the apikey parameter.

To keep track of the number of requests you have left for a given period, you can use the following HTTP headers returned in the response. If you're using an API key, you can also check your account to keep track of your usage.

Header Description
The total amount of names available in the current time window. For free usage, this will be 100 predictions and for subscriptions it will follow your tier.
The remaining amount of names available in the current time window.
Seconds remaining until a new time window open. Free usage runs on a daily window and subscriptions follow the monthly billing period.{YOUR_API_KEY}
Responses & Errors

How to understand your gender checking requests

All responses wil be in content-type: application/json, charset=utf-8.

Here's a list of possible error codes and their explanation.

Code Description Response
{ "error": "Invalid API key" }
Payment Required
{ "error": "Subscription is not active" }
Unprocessable Content
{ "error": "Missing 'name' parameter" }
Unprocessable Content
{ "error": "Invalid 'name' parameter" }
Too many requests
{ "error": "Request limit reached" }
Too many requests
{ "error": "Request limit too low to process request" }