Update Persons of a Couple Relationship

This example request illustrates how to change the persons of a couple relationship. A user may determine that they have added the wrong person to the relationship and need to change it.

JSON

Request

POST /platform/tree/couple-relationships/crid
Content-Type: application/x-gedcomx-v1+json
Authorization: Bearer YOUR_ACCESS_TOKEN_HERE{
  "relationships" : [ {
    "id" : "crid",
    "attribution" : {
      "changeMessage" : "...change message..."
    },
    "person1" : {
      "resource" : "https://api.familysearch.org/platform/tree/persons/FJP-M4RK",
      "resourceId" : "FJP-M4RK"
    },
    "person2" : {
      "resource" : "https://api.familysearch.org/platform/tree/persons/JRW-NMSD",
      "resourceId" : "JRW-NMSD"
    }
  } ]
}

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 id="crid">
        <attribution>
            <changeMessage>...change message...</changeMessage>
        </attribution>
        <person1 resource="https://api.familysearch.org/platform/tree/persons/FJP-M4RK" resourceId="FJP-M4RK"/>
        <person2 resource="https://api.familysearch.org/platform/tree/persons/JRW-NMSD" resourceId="JRW-NMSD"/>
    </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