FAfamilysearch
Person

Update Genealogies Person

Update a genealogies person including names, gender, or facts of the person.

post/genealogies/persons/{pid}

Request

  • Base URL
    https://apibeta.familysearch.org/platform
  • URL
    https://apibeta.familysearch.org/platform/genealogies/persons/{pid}
  • Auth
    HTTP bearer

Path parameters

pidstring required

The ID of the genealogies person to update. To find genealogies person IDs, see <a href="/reference/readgenealogiespersons" target="_blank">Read Genealogies Persons</a>.

Headers

Accept'application/x-fs-v1+json' | 'application/x-gedcomx-v1+json' | 'application/json' | 'application/x-fs-v1+xml' | 'application/x-gedcomx-v1+xml' | 'application/xml' required

Specifies the media type(s) that the client is willing to accept in the response.

Content-Type'application/x-fs-v1+json' | 'application/x-gedcomx-v1+json' | 'application/x-fs-v1+xml' | 'application/x-gedcomx-v1+xml' required

Specifies the media type of the entity-body sent to the server in the request.

X-Reasonstring

Header giving the reason for updating a genealogies person.

Request body

Example request

{
  "persons": [
    {
      "gender": {
        "type": "http://gedcomx.org/Male"
      },
      "names": [
        {
          "type": "http://gedcomx.org/BirthName",
          "preferred": true,
          "nameForms": [
            {
              "fullText": "John Smith",
              "parts": [
                {
                  "type": "http://gedcomx.org/Given",
                  "value": "John"
                }
              ]
            }
          ],
          "attribution": {
            "changeMessage": "message"
          }
        }
      ],
      "facts": [
        {
          "type": "http://gedcomx.org/Birth",
          "date": {
            "original": "3 Apr 1836",
            "formal": "+1836"
          },
          "place": {
            "original": "Moscow, Russia",
            "normalized": "Moscow, Moskva, Russia"
          },
          "attribution": {
            "changeMessage": "message"
          }
        }
      ]
    }
  ]
}

Response

The successful update contained a single conclusion. Expect the id of the conclusion in the 'Location' header.

Changes

No recorded changes to this operation across all 1 revision of this API.