Update Couple Relationship Conclusion

This example request illustrates how to update a conclusion, such as a marriage event, on a couple relationship. If a new conclusion, such as a marriage fact, is to be added to the couple relationship, the conclusion is provided without an ID. If an existing conclusion is to be updated on the couple relationship, the ID of the conclusion must be provided.

JSON

Request

POST /platform/tree/couple-relationships/crid
Content-Type: application/x-gedcomx-v1+json
Authorization: Bearer YOUR_ACCESS_TOKEN_HERE{
  "relationships" : [ {
    "facts" : [ {
      "id" : "C123-456",
      "attribution" : {
        "changeMessage" : "...change message..."
      },
      "type" : "http://gedcomx.org/Marriage"
    } ]
  } ]
}

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/couple-relationships/crid
Date: Sun, 03 Apr 1836 10:00:00 GMT-5
Cache-control: no-transform, must-revalidate, max-age=0

XML

Request

POST /platform/tree/couple-relationships/crid
Content-Type: application/x-gedcomx-v1+xml
Authorization: Bearer YOUR_ACCESS_TOKEN_HERE<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<gedcomx xmlns:fs="http://familysearch.org/v1/" xmlns="http://gedcomx.org/v1/" xmlns:atom="http://www.w3.org/2005/Atom">
    <relationship>
        <fact type="http://gedcomx.org/Marriage" id="C123-456">
            <attribution>
                <changeMessage>...change message...</changeMessage>
            </attribution>
        </fact>
    </relationship>
</gedcomx>

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/couple-relationships/crid
Date: Sun, 03 Apr 1836 10:00:00 GMT-5
Cache-control: no-transform, must-revalidate, max-age=0