Changelog

1. Added Bulk OrdinanceStatusRollup endpoint.

A new endpoint lets you quickly check whether sources have been changed since a given timestamp. This is especially useful if your application stores local copies of sources and needs to keep that data up to date.

• Issue where Tree search returned link with duplicate query parameters that caused errors.
• Tree Change History now supports custom events.
• Various optimizations and improvements to infrastructure.

A new API feature is now available to link matching persons across FamilySearch trees. See the Tree to Tree Linking guide to learn more. This feature is in beta, and the interface may change over the next 60 days.

• Added support for tree person reference in Tree Change History and Person Change History.
• Updated OpenAPI Identity endpoints documentation.

We’re excited to announce the launch of a modernized API Reference experience on the FamilySearch Developer website. This update is designed to make it easier than ever for developers to explore, understand, and interact with the FamilySearch API.

• Update dependencies
• Internal updates and improvements.

Implement tree to tree match endpoint.

OpenAPI tag updates and examples.

This quarter’s newsletter highlights exciting updates to our developer documentation and recommends using an API client to simplify integration and troubleshooting.