geneanet.org APIgeneanet.org ↗
Access Geneanet genealogical records via 4 endpoints: search individuals, retrieve family profiles, look up surname distributions, and query cemetery records.
curl -X GET 'https://api.parse.bot/scraper/ed77ac7b-ac0a-4014-8489-10e20a9badfb/search_individuals?page=1&size=3&lastname=Dupont' \ -H 'X-API-Key: $PARSE_API_KEY'
Search for individuals across all Geneanet collections. Returns paginated results with name, profile URL, and description for each match.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number for pagination. |
| size | integer | Number of results per page. |
| year | string | Year of birth, marriage, or death to filter by. |
| place | string | Location to filter results. |
| lastnamerequired | string | Last name to search for. |
| firstname | string | First name to filter results. |
| collection | string | Collection to search within. Accepted values: 'archives', 'family_trees', 'cemeteries', 'library'. |
{
"type": "object",
"fields": {
"page": "integer current page number",
"results": "array of objects with full_name, profile_url, and description",
"total_count": "integer total number of matching records"
},
"sample": {
"data": {
"page": 1,
"results": [
{
"full_name": "DUPONT Jeanne",
"description": "DUPONT Jeanne | Spouse | : | VAGNIOT François | ( | 1848 | ) | Family tree of pierrevirely | Birth | 1828 | Death | 1863 | Quincey, 21517, Côte-d'Or, France",
"profile_url": "https://gw.geneanet.org/pierrevirely?n=dupont&oc=4&p=jeanne&type=fiche"
}
],
"total_count": 3207279
},
"status": "success"
}
}About the geneanet.org API
The Geneanet API exposes 4 endpoints covering individual search, detailed family profiles, surname geographic distribution, and cemetery records from Geneanet.org's genealogical collections. The search_individuals endpoint lets you query across archives, family trees, cemeteries, and the library collection by name, place, and year. Profile results include life events, family relationships, and structured name data useful for genealogical research applications.
Individual Search and Profile Retrieval
The search_individuals endpoint accepts a required lastname parameter along with optional filters for firstname, year, place, and collection. The collection filter accepts four values: archives, family_trees, cemeteries, and library. Results are paginated via page and size parameters and return a total_count integer, a current page, and a results array where each element includes full_name, profile_url, and description.
Once you have a profile_url from search results, get_individual_profile returns a full_name string, a life_summary array of strings covering life events such as birth, death, and occupation, and a family object with three sub-arrays: parents, spouses_and_children, and siblings. This structured family tree data is suitable for building relationship graphs or populating genealogy databases.
Surname Distribution and Cemetery Records
The get_last_name_origin endpoint takes a lastname string and returns the queried surname, an optional description string containing etymology or origin notes, and a distribution_by_place array where each entry carries a place name and occurrence count. This makes it possible to map historical surname concentrations geographically.
The search_cemeteries endpoint is a targeted query into the cemeteries collection, requiring only a lastname parameter. It returns the same response shape as search_individuals—page, total_count, and a results array with full_name, profile_url, and description—but scoped specifically to grave and monument records.
- Build a surname frequency map using
distribution_by_placecounts fromget_last_name_origin - Populate a family tree viewer by chaining
search_individualsresults intoget_individual_profileto retrieveparents,siblings, andspouses_and_children - Search for ancestral grave records by surname using
search_cemeteriesand display monument descriptions - Filter historical records by birth or death year using the
yearparameter insearch_individuals - Cross-reference individuals across Geneanet collections by querying
archivesandfamily_treesseparately and merging results - Enrich a genealogy dataset with occupation and life event strings pulled from the
life_summaryarray in profile responses - Scope regional ancestry research by combining
placeandlastnamefilters insearch_individuals
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Geneanet have an official developer API?+
What does `get_individual_profile` return beyond basic name data?+
life_summary array of human-readable strings describing life events (birth, death, occupations, and similar), and a family object with three arrays: parents, spouses_and_children, and siblings. Each family member entry comes from the profile associated with the provided profile_url.Can I filter `search_individuals` to a specific collection like archives or family trees?+
collection parameter accepts four values: archives, family_trees, cemeteries, and library. Omitting it searches across all collections. The search_cemeteries endpoint is a convenience wrapper that targets the cemeteries collection specifically.Does the API return photo or document image URLs from Geneanet profiles?+
How complete is the `description` field in `get_last_name_origin`?+
description field may be empty for surnames where Geneanet does not have etymology data. The distribution_by_place array is returned regardless, but surname origin text coverage varies by name and language of origin.