---
title: "Search Tree Persons"
method: GET
path: "/tree/search"
tags: ["Search"]
---

# Search Tree Persons

`GET /tree/search`

This operation enables you to search tree persons using a variety of query parameters such as name, event dates and places, sex, and more. This operation returns person summaries that match the search criteria.

For a detailed explanation of all supported query parameters, including formatting examples, filtering tips, and usage guidelines, see the [Family Tree Search](https://developers.familysearch.org/main/docs/family-tree-search) guide.

## Filter and Facet Parameters

This endpoint supports dynamic `f.*` (filter) and `c.*` (facet) parameters controlled by the underlying search service. Due to the large number of possible combinations and their dynamic nature, only commonly-used examples are shown below.

**⚠️ Parameter Format:** Filter and facet parameters follow the pattern:
- **Filters:** `f.[parameter]=[value]` (e.g., `f.birthPlace0=3,Canada`)
- **Facets:** `c.[parameter]=on` (e.g., `c.sex=on`)

**Multiple Facets:** You can enable multiple facet parameters simultaneously (e.g., `c.sex=on&c.birthYear0=on`) to see distribution across different dimensions.

**Hierarchical Parameters:** For hierarchical data like places (birthYear0, birthYear1, birthYear2), you can jump directly to any level without filtering intermediate levels. For example, you can use `c.birthPlace1=on` without setting `f.birthPlace0` to see all state-level distributions.

For the list of common parameters and detailed faceting workflows, see the [Search/Faceting/Filter Guide](https://developers.familysearch.org/main/docs/search-queries-faceting-filtering).
For information on Family Tree Search specifically, see the [Family Tree Search Guide](https://developers.familysearch.org/main/docs/family-tree-search).

You can explore this endpoint interactively by setting sample query parameters below.

> ⚠️ "Try It!" Limitations
> 
> The built-in API explorer has limited support for this operation due to the complexity of the query parameter structure. While you can run simple queries using `q.` parameters and the example `f.` / `c.` parameters shown below, it does not support all possible filter and facet combinations.
> 
> **For full testing capabilities**, we recommend using an external API client tool such as [Bruno](https://www.usebruno.com/) or [Postman](https://www.postman.com/), which offer more control over request construction and parameter encoding.
> 
> **To discover available parameters dynamically**, use faceting: enable `c.[parameter]=on` in your request, and the response will include valid filter values you can use.

## Query parameters

- `q.givenName` string
- `q.surname` string
- `q.sex` string
- `q.birthLikeDate` string
- `q.birthLikePlace` string
- `q.deathLikeDate` string
- `q.deathLikePlace` string
- `q.marriageLikeDate` string
- `q.marriageLikePlace` string
- `q.residenceDate` string
- `q.residencePlace` string
- `q.fatherGivenName` string
- `q.fatherSurname` string
- `q.fatherBirthLikePlace` string
- `q.motherGivenName` string
- `q.motherSurname` string
- `q.motherBirthLikePlace` string
- `q.parentGivenName` string
- `q.parentSurname` string
- `q.parentBirthLikePlace` string
- `q.spouseGivenName` string
- `q.spouseSurname` string
- `m.defaultFacets` string
- `c.collectionId` string
- `c.treeId` string
- `c.sex` string
- `f.sex` string
- `c.birthYear0` string
- `f.birthYear0` string
- `c.birthPlace2` string
- `f.birthPlace2` string
- `c.*` string
- `f.*` string
- `offset` integer
- `count` integer

## Headers

- `Accept` 'application/x-gedcomx-atom+json' | 'application/json' | 'application/atom+xml' | 'application/xml', required

## Response `200`

The read was successful. See <a href="https://developers.familysearch.org/main/docs/json-schema#person" target="_blank">Person Schema (JSON)</a>

## Other responses

- `204` — Upon a successful search with no results.
- `400` — The request was unable to be understood by the application. See response warning headers for details.
- `429` — The request was throttled.

---

[API](https://skmtc.net/familysearch/apis/authentication-endpoints.md) · [All operations](https://skmtc.net/familysearch/apis/authentication-endpoints/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/familysearch/authentication-endpoints/revisions/2b5020574a62/schema)