Register a third-party app and query historical death records via the FamilySearch API

domain: developers.familysearch.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Submit a Third-Party Service Provider Application via the Microsoft Forms link on developers.familysearch.org
  2. Wait for FamilySearch approval and receive your API client credentials
  3. Authenticate using the OAuth2 Authorization Code grant; the Client Credentials grant requires a separate special-permission request emailed to devsupport@familysearch.org
  4. Build against the documented REST endpoints for Trees, Historical Records, Places, Memories, and Ordinances
  5. Pass FamilySearch's Compatibility Checklist review before launching to production

Known gotchas

Related routes

Integrate a third-party app with a funeral home's case data via the Passare API and webhooks
passare.com · 6 steps · unrated
authenticate via oauth2 and read a person record from the familysearch family tree api
familysearch.org · 6 steps · unrated
Read and write people, family, and contribution records in ChMeetings via its Developer API
chmeetings.com · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans