Read Person Merge Constraint (Can Merge Other Order Only)

This example request illustrates how to read the constraints for a merge between two persons that can be merged only in the other order.

JSON

Request

OPTIONS /platform/tree/persons/P12-345/merges/P54-321
Accept: application/x-fs-v1+json
Authorization: Bearer YOUR_ACCESS_TOKEN_HERE
                
              

Response

HTTP/1.1 200 OK
Content-type: application/x-fs-v1+json
X-processing-time: 3
Warning: 450 FamilySearch "Can merge, but must switch order"
Vary: Accept,Accept-Language,Accept-Encoding,Expect
Link: <https://api.familysearch.org/platform/tree/persons/P54-321/merges/P12-345>; rel="merge-mirror"
Date: Sun, 03 Apr 1836 10:00:00 GMT-5
Cache-control: no-transform, must-revalidate, max-age=0
Transfer-encoding: chunked
Allow: OPTIONS
                
              

XML

Request

OPTIONS /platform/tree/persons/P12-345/merges/P54-321
Accept: application/x-fs-v1+xml
Authorization: Bearer YOUR_ACCESS_TOKEN_HERE
                
              

Response

HTTP/1.1 200 OK
Content-type: application/x-fs-v1+xml
X-processing-time: 3
Warning: 450 FamilySearch "Can merge, but must switch order"
Vary: Accept,Accept-Language,Accept-Encoding,Expect
Link: <https://api.familysearch.org/platform/tree/persons/P54-321/merges/P12-345>; rel="merge-mirror"
Date: Sun, 03 Apr 1836 10:00:00 GMT-5
Cache-control: no-transform, must-revalidate, max-age=0
Transfer-encoding: chunked
Allow: OPTIONS