Update Not-a-Match Declaration

Add or edit a not-a-match declaration, indicating that the two referenced persons are separate and distinct individuals and should not be merged together. This operation will fail if there already exists a not-a-match declaration for the person(s).A reason string can be provided indicating why the user believes the two persons to be distinct individuals. The reason is sent as an 'X-Reason' value in the HTTP Headers on the request. This reason can have a maximum length of 2000 characters, and if the reason supplied is more than 2000 characters, the request will fail as an invalid request.

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

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

Body Params

Gedcomx object containing person(s) to declare as not a match with the specified person

persons
array of objects
required
length ≥ 1

Array of persons to declare as not a match. Each person represents someone who should NOT be merged with the primary person.

persons*
string
required

The ID of the person to declare as not a match. Can be a person from the main FamilySearch tree or from a user tree. To find an example person ID, see Search Tree Persons.

attribution
object

Attribution information for the not-a-match declaration

Headers
string

The header giving the reason for adding/removing a not-a-match declaration.

Responses
204

The update was successful.

404

If the requested person is not found.

410

If the requested person has been merged or deleted.

429

The request was throttled.

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