GuidesAPI ReferenceChangelogHelp
Guides

Read Genealogies Merged Person

Suggest Edits

This example request illustrates what happens during a read of a person that has been merged. Note the 301 Moved Permanently status code and the Location header indicating where the person has been forwarded.

JSON

Request

GET /platform/genealogies/persons/2:2:PPPJ-MYZ
Accept: application/x-gedcomx-v1+json
Authorization: Bearer YOUR_ACCESS_TOKEN_HERE

Response

HTTP/1.1 301 Moved Permanently
Content-type: application/x-gedcomx-v1+json
X-processing-time: 3
Vary: Accept,Accept-Language,Accept-Encoding,Expect
X-entity-forwarded-id: 67890
Content-location: /platform/genealogies/persons/2:2:PPPJ-MYZ
Date: Sun, 03 Apr 1836 10:00:00 GMT-5
Cache-control: no-transform, must-revalidate, max-age=0
Location: https://api.familysearch.org/platform/genealogies/persons/67890
Transfer-encoding: chunked

XML

Request

GET /platform/genealogies/persons/2:2:PPPJ-MYZ
Accept: application/x-gedcomx-v1+xml
Authorization: Bearer YOUR_ACCESS_TOKEN_HERE

Response

HTTP/1.1 301 Moved Permanently
Content-type: application/x-gedcomx-v1+xml
X-processing-time: 3
Vary: Accept,Accept-Language,Accept-Encoding,Expect
X-entity-forwarded-id: 67890
Content-location: /platform/genealogies/persons/2:2:PPPJ-MYZ
Date: Sun, 03 Apr 1836 10:00:00 GMT-5
Cache-control: no-transform, must-revalidate, max-age=0
Location: https://api.familysearch.org/platform/genealogies/persons/67890
Transfer-encoding: chunked

Updated 5 days ago