FamilySearch
Family trees for Worldwide. Access: Your own OAuth sign in, key needed. Terms checked November 1, 2026.
Access and terms
| Slug | familysearch |
|---|---|
| Records | Family trees |
| Places | Worldwide |
| Years | Not stated by the source |
| Access | Your own OAuth sign in |
| Key | Needed, and supplied through your own sign in to the source. |
| Rate limit | None stated by the source. |
| robots.txt | Not checked. |
| Homepage | www.familysearch.org/ |
| API docs | developers.familysearch.org/main/docs/getting-started |
| Terms | developers.familysearch.org/main/docs/compatibility-review-process |
| Checked by hand | November 1, 2026 |
Notes
Reached only through the user's own FamilySearch sign in, over OAuth, with an app key the user registers. Lineage never holds FamilySearch passwords and never uses its own FamilySearch credentials. Every request needs an access token. Production keys need acceptance into the Compatible Solution Program and signed agreements, and only a registered business or non-profit is eligible. The health probe reads the developer docs.
Evidence read on November 1, 2026
Status: Live
Live at the last check, 2026-11-01 22:02 UTC. HTTP 200 in 86 ms. One check a day.
JSON: /v1/sources/familysearch. For agents: /sources/familysearch/llms.txt.