---
title: "Update Match Resolution"
method: POST
path: "/tree/persons/{pid}/matches"
tags: ["Matches"]
---

# Update Match Resolution

`POST /tree/persons/{pid}/matches`

**Certification Required**

Add or modify a match resolution for the given tree person id. The status parameter should indicate if the match is Pending, Accepted, or Rejected. The
body of the POST should contain a gedcomx document with a single record persona id for the match resolution. If an Accepted or Rejected match resolution
declaration already exists for the given tree person id, an error will be returned. The current resolution should first be reset to Pending, then a new
match resolution may be set.

A reason string should be provided indicating why the user believes this is or is not a match.

## Path parameters

- `pid` string, required

## Query parameters

- `collection` 'records' | 'tree' | 'user_trees' | 'cet'
- `status` 'pending' | 'accepted' | 'rejected', 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

## Response `204`

The update was successful.

## Other responses

- `301` — If the referenced person has been merged into another person.
- `404` — If the referenced person is not found.
- `410` — If the referenced person has been 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)