Allow Person Merge

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.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

The id of the survivor. Can be a person from the main FamilySearch tree or from a user tree. To find an example person ID, see Search Tree Persons.

string
required

The id of the duplicate. Can be a person from the main FamilySearch tree or from a user tree. To find an example person ID, see Search Tree Persons.

Responses
200

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

404

If the person is not found.

410

If the person has been deleted.

429

If the request has been throttled.

Language
Credentials
Bearer
LoadingLoading…
Response
Click Try It! to start a request and see the response here!