GenderAPI.io · REST API v2
Estimate gender from a first name, full name, email address or username. GenderAPI.io V2 returns structured JSON with the prediction source, a confidence score and optional country context.
GenderAPI.io V2
https://api.genderapi.io/api/v2/gender?type=name&value=OnurIllustrative V2 response — run a lookup for live data.
{
"data": {
"input": {
"type": "name",
"value": "Onur",
"country": null
},
"name": "onur",
"gender": "male",
"country": "TR",
"confidence": 0.9,
"confidence_kind": "observed_frequency",
"sample_count": 100,
"source": "dataset",
"result_status": "identified",
"reason": null,
"country_source": "dataset",
"match": {
"name": "onur",
"method": "normalized",
"scope": "global",
"country": null
}
},
"meta": {
"request_id": "11111111-1111-4111-8111-111111111111",
"duration_ms": 12,
"access": {
"mode": "ip_trial",
"reason": "api_key_missing"
},
"usage": {
"charged_credits": 1,
"remaining_credits": 9,
"billing_status": "confirmed",
"resets_at": "2026-09-26T12:00:00.000Z",
"limit": 10,
"period_seconds": 86400
}
}
}Name to gender API
Look up one record, send a batch or use our spreadsheet tools. V2 distinguishes identified and unknown results, so your workflow can preserve uncertainty instead of forcing a prediction.
Name to gender
Analyze a first or full name and receive an estimate with a confidence score, prediction source and an explicit unknown result when no prediction is available.
Email to gender
Extract useful name signals from common email formats and add gender information to customer, lead and analytics records.
Username to gender
Analyze usernames that contain names, initials or common separators and return the most likely gender when enough signal is available.
Bulk enrichment
Upload a spreadsheet, select the source column and download an enriched file containing gender, country and confidence fields.
Works with your stack
Start with a simple REST request or connect GenderAPI to spreadsheets, ecommerce platforms and automation workflows.
Frequently asked questions
Review the essentials, then explore the documentation for request formats and implementation examples.
View all FAQsGenderAPI.io estimates gender from a name, email address or username. V2 returns the prediction, confidence, source and credit usage as JSON. These are estimates from naming patterns, not a verification of a person's identity.
A single lookup checks the dataset first and uses AI if no result is found. This default fallback costs one credit in total. Batch items default to AI off. You can choose the AI mode or enable forceToGenderize for nickname and alias inference.
V2 confidence is a score from 0 to 1, or null. The confidence_kind field distinguishes observed dataset frequency from a model-reported estimate; it is not a promise of accuracy. Unknown results return gender: null and result_status: unknown.
A standard V2 lookup costs one credit, including ordinary AI fallback and successful unknown results. Always-AI costs two credits. With forceToGenderize, a resolved dataset result costs one credit; using AI costs two in total. Batch costs add up per item.
Yes. A V2 batch accepts up to 50 records with a valid API key, or 10 in an IP trial. One HTTP request can consume multiple credits. Excel, CSV and other integrations are also available for larger workflows.
The public V2 demo shares 10 trial credits per IP in a 24-hour window. Registering for a free account gives 200 daily credits. These are credit allowances; modes that cost two credits use them faster.
Yes. V1 and V2 share the same API key and account balance. Existing V1 integrations remain available. New integrations should use V2 documentation because its endpoints, response fields and error format differ from V1.
Start building
Create an account, test your first requests and move from individual lookups to complete datasets.