Create Child-and-Parents Relationship Conclusion

This example request illustrates how to create a conclusion on a child-and-parents relationship. This describes the lineage between a child and his parents, such as biological, adopted, guardianship, or step. If you're adding a new conclusion, such as the lineage type to the parent2, the conclusion is provided without an ID. If anexistingconclusion is to be updated on the child-and-parents relationship, the ID of the conclusion must be provided.

JSON

Request

POST /platform/tree/child-and-parents-relationships/12345
Content-Type: application/x-fs-v1+json
Authorization: Bearer YOUR_ACCESS_TOKEN_HERE{
  "childAndParentsRelationships" : [ {
    "parent2Facts" : [ {
      "attribution" : {
        "changeMessage" : "...change message..."
      },
      "type" : "http://gedcomx.org/BiologicalParent"
    } ]
  } ]
}

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
Content-location: /platform/tree/child-and-parents-relationships/12345
Date: Sun, 03 Apr 1836 10:00:00 GMT-5
Cache-control: no-transform, must-revalidate, max-age=0

XML

Request

POST /platform/tree/child-and-parents-relationships/12345
Content-Type: application/x-fs-v1+xml
Authorization: Bearer YOUR_ACCESS_TOKEN_HERE<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<fs:familysearch xmlns:fs="http://familysearch.org/v1/" xmlns="http://gedcomx.org/v1/" xmlns:atom="http://www.w3.org/2005/Atom">
    <fs:childAndParentsRelationship>
        <fs:parent2Fact type="http://gedcomx.org/BiologicalParent">
            <attribution>
                <changeMessage>...change message...</changeMessage>
            </attribution>
        </fs:parent2Fact>
    </fs:childAndParentsRelationship>
</fs:familysearch>

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
Content-location: /platform/tree/child-and-parents-relationships/12345
Date: Sun, 03 Apr 1836 10:00:00 GMT-5
Cache-control: no-transform, must-revalidate, max-age=0