---
title: "Update Not-a-Match Declaration"
method: POST
path: "/tree/persons/{pid}/not-a-match"
tags: ["Matches"]
---

# Update Not-a-Match Declaration

`POST /tree/persons/{pid}/not-a-match`

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.

## Path parameters

- `pid` string, required

## Headers

- `Content-Type` 'application/x-fs-v1+json' | 'application/x-gedcomx-v1+json' | 'application/x-fs-v1+xml' | 'application/x-gedcomx-v1+xml', required
- `X-Reason` string

## Response `204`

The update was successful.

## Other responses

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