Baby Name API & Open Dataset

A free, key-free JSON API over 219,846 given names compiled from 34 official sources — national birth registries, statistical agencies and open datasets covering 1880–2025. No signup, no API key, no rate-limit wall.

Figures are read live from the database, not hand-maintained. Last refreshed within 12 hours.

Quick start

No key, no headers, no signup. Every endpoint is a plain GET returning JSON:

curl "https://babynamesuggestion.com/wp-json/bns/v1/names/Olivia"

Or filter the whole dataset:

curl "https://babynamesuggestion.com/wp-json/bns/v1/names?per_page=5&gender=F&region=IN&sort=rank"

Endpoints

Base URL: https://babynamesuggestion.com/wp-json/bns/v1

Where the data comes from

Every figure traces back to a named source. Most are national statistical agencies publishing open data; each row links to the original so you can verify any number yourself, or go straight to the primary source when you need to cite it.

Licence & citation

Two different things live in this dataset, and they carry different rights. We are explicit about that rather than claiming a blanket licence we are not in a position to grant.

• Our compilation — the API, the unified schema, our name meanings, origins and derived fields. Free to use, including commercially, with attribution to babynamesuggestion.com.
• The underlying registry figures — birth counts and ranks belong to the statistical agencies listed above, each under its own terms. We do not own them and cannot relicense them. If you republish those figures, cite the originating agency as well as us.
• Name meanings are partly AI-assisted and are labelled as such on the site wherever they have not been human-verified. Treat them as a compiled reference, not a peer-reviewed etymological authority.

Suggested citation

babynamesuggestion.com Baby Name Dataset (2026).
219,846 given names from 34 sources, 1880-2025.
https://babynamesuggestion.com/baby-name-api/

Fair use

• There is no hard rate limit today, which we would like to keep true. Keep requests to a sensible pace and cache what you fetch.
• Bulk-mirroring the whole dataset by walking /names is not what the API is for. If you need the data in bulk, get in touch — that is a conversation, not a scrape.
• If your project gets popular, tell us so we can plan capacity rather than discover it from a load spike.
• We may add rate limiting later if the API is abused. Documented endpoints will not change shape without notice.

Get in touch about bulk access or a project using this data →