---
title: "Allow Person Merge"
method: OPTIONS
path: "/tree/persons/{pid}/merges/{dpid}"
tags: ["Persons"]
---

# Allow Person Merge

`OPTIONS /tree/persons/{pid}/merges/{dpid}`

The OPTIONS method supplies information about the viability of this merge, using the `Allow` HTTP header. If this merge is viable, the Allow will indicate that both GET, POST may be applied. If the merge is available when the roles of the survivor and non-survivor are switched, a `Link` header will be supplied linking to the "merge mirror." When the merge is NOT viable, the `Allow` header will NOT include a GET or POST. The `Warning` header will contain details as to the reason the merge is not viable.

## Path parameters

- `pid` string, required
- `dpid` string, required

## Response `200`

The merge is viable. When unable to merge - expect a 450 warning header with details in the warning message.

## Other responses

- `404` — If the person is not found.
- `410` — If the person has been deleted.
- `429` — If the request has been 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)