On a profile marked deceased, sets, changes or clears the Deceased Date. A cleared date leaves the profile "Deceased" with no age.
On any other profile only clearing is allowed, which removes a Deceased Date that was never a death. Setting one there answers 400 deceased_date_requires_mark_desc; use POST /api/people/{id}/deceased instead.
Several stored dates collapse to the one sent. The date in the archive note is not changed. The same rules as Mark Deceased apply: the caller needs the permission at any of the person's campuses or organizations and cannot change their own profile (400 own_profile_status_refused_desc); only a super user can change a super user's (400 super_user_status_refused_desc). A business can never be given a Deceased Date (400 deceased_business_refused_desc), but a date it still holds can be cleared.
Required permission: Profile Deactivate
| Time | Status | User Agent | |
|---|---|---|---|
Retrieving recent requests… | |||
200OK
401Authentication is required, or the Ocs-Api-Key header is missing or invalid.
