Read Person Merge Constraint (Can Merge Any Order)

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

JSON

Request

OPTIONS /platform/tree/persons/P12-345/merges/P54-321?access_token=ZZZZZ
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
Vary: Accept,Accept-Language,Accept-Encoding,Expect
Date: Sun, 03 Apr 1836 10:00:00 GMT-5
Cache-control: no-transform, must-revalidate, max-age=0
Transfer-encoding: chunked
Allow: OPTIONS, HEAD, GET, POST
                
              

XML

Request

OPTIONS /platform/tree/persons/P12-345/merges/P54-321?access_token=ZZZZZ
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
Vary: Accept,Accept-Language,Accept-Encoding,Expect
Date: Sun, 03 Apr 1836 10:00:00 GMT-5
Cache-control: no-transform, must-revalidate, max-age=0
Transfer-encoding: chunked
Allow: OPTIONS, HEAD, GET, POST