Example Requests

Introduction

This guide provides example API requests to help you get started quickly with the FamilySearch API. It aims to shorten the time between learning about the API and making your first successful call.

Each example provides a complete HTTP request and response pair, giving you a realistic view of what to send and what to expect in return. You’ll find these examples helpful for debugging, learning, or demonstrating FamilySearch API capabilities.

Anatomy of an Example Request

Every example in this guide is structured with the following components:

HTTP Request Block

• Endpoint Path – The relative URL path of the API endpoint (no domain or protocol).

• Required Headers – Standard headers such as:

  • Accept: application/json
  • Authorization: Bearer <your_access_token>

Sample Request Body

If the request is not a GET method, you’ll see a sample JSON or XML payload that illustrates the expected structure.

Sample Response

Each request example includes a successful response payload. Some examples also include a common error response (e.g., 401 Unauthorized or 400 Bad Request) for quick troubleshooting.

Supported Formats

FamilySearch API supports multiple response and request formats, with JSON being the default and most commonly used. XML is also supported for clients with legacy requirements.

• JSON – Recommended for all new integrations.
• XML – Supported where specified.

Common Use-Case Examples (Quick Links)

These represent the most frequent developer tasks, based on support analytics and integration patterns:

Authentication & Session

• Initiate Authorization
• Obtain Access Token

Tree Persons

• Read a Person
• Create a Person
• Update a Person
• Delete a Person

Memories & Media

• Upload a Photo
• Attach a Memory to a Person

Search & Tree Navigation

• Search Tree Persons
• Read Ancestral Pedigree

Additional Resources

• API Reference Console – Explore and test each endpoint with live credentials.
• Authentication Guide – Learn how to authenticate securely using OAuth 2.0.
• Support – Contact our developer support team.

Disclaimer: This documentation includes content generated by AI tools and has been reviewed and edited by humans.