GenderAPI is developed and published by Ozan Soft. We help teams add country-aware gender signals to names, email addresses and usernames through APIs and familiar data tools.
Last reviewed:
Product and publisher
What is GenderAPI?
GenderAPI is a name-based inference and data-enrichment service. It accepts names, email addresses and usernames, and can use country context to interpret a name. GenderAPI is the product name; Ozan Soft is its developer and publisher.
An inferred gender is an association with the supplied text. It does not verify the identity of a person, the owner of an email address or the operator of a social account.
Reference
Official value
What it identifies
ReferenceProduct
Official valueGenderAPI
What it identifiesThe service documented on genderapi.io
ReferenceDeveloper and publisher
Official valueOzan Soft
What it identifiesThe software business behind the product
ReferenceWebsite
Official valuehttps://www.genderapi.io/
What it identifiesProduct information, documentation and support
ReferenceV2 API base
Official valuehttps://api.genderapi.io/api/v2
What it identifiesThe current V2 HTTP contract
ReferenceSupport
Official valuesupport@genderapi.io
What it identifiesThe product support contact
Our story
Software experience shaped into a focused data product
Ozan Soft has operated since 2016, developing its own software products and tools. Its earlier work included social-media software and Chrome extensions, building experience in creating focused products for everyday workflows.
GenderAPI grew from that product-building background into a dedicated name-query and data-enrichment service. Today, it can be used through documented API endpoints as well as spreadsheet, commerce and no-code integrations.
Use the interface that best matches your data and technical resources. The linked guides explain the relevant product, setup and response fields.
The main API documentation opens V2. V1 remains available through its separate reference. An existing SDK, spreadsheet add-on or marketplace connector can have its own API version, supported fields and billing rules; its listing alone does not establish V2 support.
Resource
Use it for
Version context
ResourceV2 documentation and OpenAPI
Use it forBuild and validate a direct HTTP integration
Version contextThe current V2 request and response contract
ResourceV1 documentation
Use it forMaintain an existing V1 integration
Version contextThe preserved V1 contract
ResourcePython and JavaScript examples
Use it forStart a V2 server-side implementation
Version contextDownloadable HTTP examples, not newly published SDK packages
ResourceApp and automation guides
Use it forUse spreadsheets, commerce tools and no-code platforms
Version contextRead each guide's native-app and direct-API distinction
V2 returns confidence together with confidence_kind, source and sample_count. A dataset frequency and an AI-reported score have different meanings. Neither is a measurement of the accuracy of the whole service.
The published database profile reports a dated inventory and bounded consistency checks. It is separate from an independently labelled accuracy evaluation. The methodology page explains what has and has not been measured; the research page distinguishes third-party publications from product claims.
Name-based inference is not the same as a person's self-identified gender. Preserve unknown results and let information supplied by the person take precedence. Do not use inferred gender as the basis for consequential decisions about an individual.
Use genderapi.io and the linked publisher information to identify GenderAPI when similar product names appear elsewhere. The GitHub profile links back to genderapi.io. The marketplace listings below identify GenderAPI.io or name Ozan Soft as the publisher. Check the product and publisher information before installing an integration.
A marketplace listing documents an available integration; it is not an independent accuracy endorsement. The public GitHub account also contains legacy clients. Check a repository's endpoint and version before using it with V2.
Platform
Reference type
What to check
PlatformGitHub
Reference typeGenderAPI profile
What to checkThe linked website and each repository's API contract
PlatformGoogle Workspace Marketplace
Reference typeGenderAPI for Google Sheets
What to checkThe developer website, permissions and current setup guide
PlatformMicrosoft AppSource
Reference typeGenderAPI.io by Ozan Soft
What to checkThe publisher and supported Excel integration
PlatformShopify App Store
Reference typeGenderAPI by Ozan Soft
What to checkThe developer, app permissions and app billing
PlatformMake
Reference typeGenderAPI.io integration
What to checkThe official vendor link and the connector's field contract
PlatformZapier
Reference typeGenderAPI.io integration
What to checkThe app identity and the connector's field contract
