Merge Genealogies Person
This example illustrates how to merge two persons. In this case, a conclusion and a source reference on the survivor person (P12-345) is replaced with the information on the duplicate person (P54-321).
JSON
Request
POST /platform/genealogies/persons/2:2:P12-345/merges/2:2:P54-321
X-Reason: Reason for merge
Content-Type: application/x-fs-v1+json
Authorization: Bearer YOUR_ACCESS_TOKEN_HERE
Response
HTTP/1.1 204 No Content
Content-type: text/html
X-processing-time: 3
Vary: Accept,Accept-Language,Accept-Encoding,Expect
Content-length: 0
Link: <https://api.familysearch.org/platform/genealogies/persons/2:2:P12-345?flag=fsh>; rel="person"
Link: <https://api.familysearch.org/platform/genealogies/persons/2:2:P12-345/merges/2:2:P54-321?flag=fsh>; rel="merge"
Date: Sun, 03 Apr 1836 10:00:00 GMT-5
Cache-control: no-transform, must-revalidate, max-age=0
XML
Request
POST /platform/genealogies/persons/2:2:P12-345/merges/2:2:P54-321
X-Reason: Reason for merge
Content-Type: application/x-fs-v1+xml
Authorization: Bearer YOUR_ACCESS_TOKEN_HERE
Response
HTTP/1.1 204 No Content
Content-type: text/html
X-processing-time: 3
Vary: Accept,Accept-Language,Accept-Encoding,Expect
Content-length: 0
Link: <https://api.familysearch.org/platform/genealogies/persons/2:2:P12-345?flag=fsh>; rel="person"
Link: <https://api.familysearch.org/platform/genealogies/persons/2:2:P12-345/merges/2:2:P54-321?flag=fsh>; rel="merge"
Date: Sun, 03 Apr 1836 10:00:00 GMT-5
Cache-control: no-transform, must-revalidate, max-age=0
Updated 5 days ago