# Every PUT keeps what is left out and clears what is sent as null

17 November 2026 · Changed · Getting started · Breaking

Every update endpoint now follows one rule. A field left out of the body keeps its stored value, and a field sent as null is cleared. A field that cannot be empty, such as a name, a label or a cadence, refuses null with 422. A boolean left out keeps its value. A list sent whole (tags, options, columns, the ways a name is written, the groups and fields of a life event type) keeps the stored list when left out and replaces it when sent. Before, these endpoints either required every field or cleared the ones left out. A relationship type left without role_b now keeps its own role_b rather than copying role_a. A notification channel destination and a notification preference timezone sent as null still keep what is saved.

## Why this is a breaking change

An integration that cleared a field by leaving it out now keeps the old value. Send the field as null to clear it.

## Why it changed

Each endpoint had its own idea of what a missing field meant, so changing one thing meant reading the record first and sending all of it back. Now a request carries only the change.

## Changes

- `A field left out keeps its stored value` (Changed): `PUT /api/v1/me`, `PUT /api/v1/me/contact-list-view`, `PUT /api/v1/notification-channels/{channel}`, `PUT /api/v1/notification-preferences`, `PUT /api/v1/vaults/{vault}`, `PUT /api/v1/entity-types/{entityType}`, `PUT /api/v1/templates/{template}`, `PUT /api/v1/templates/{template}/versions/{version}/pages/{page}`, `PUT /api/v1/templates/{template}/versions/{version}/sections/{section}`, `PUT /api/v1/templates/{template}/versions/{version}/sections/{section}/fields/{field}`, `PUT /api/v1/life-event-categories/{lifeEventCategory}`, `PUT /api/v1/life-event-types/{lifeEventType}`, `PUT /api/v1/life-event-types/{lifeEventType}/fields`, `PUT /api/v1/relationship-categories/{relationshipCategory}`, `PUT /api/v1/relationship-types/{relationshipType}`, `PUT /api/v1/locations/{location}`, `PUT /api/v1/possession-types/{possessionType}`, `PUT /api/v1/possession-types/{possessionType}/groups/{group}`, `PUT /api/v1/possession-types/{possessionType}/fields/{field}`, `PUT /api/v1/possession-tags/{possessionTag}`, `PUT /api/v1/possession-conditions/{possessionCondition}`, `PUT /api/v1/vaults/{vault}/possessions/{possession}`, `PUT /api/v1/vaults/{vault}/contact-list-columns`, `PUT /api/v1/vaults/{vault}/contacts/{contact}/name`, `PUT /api/v1/vaults/{vault}/contacts/{contact}/name-representations`, `PUT /api/v1/vaults/{vault}/contacts/{contact}/sections/{section}`, `PUT /api/v1/vaults/{vault}/contacts/{contact}/reminders/{reminder}`, `PUT /api/v1/vaults/{vault}/life-events/{lifeEvent}`, `PUT /api/v1/vaults/{vault}/groups/{group}/notes/{note}`, `PUT /api/v1/vaults/{vault}/groups/{group}/reminders/{reminder}`
- `Send null to clear a field` (Changed): `PUT /api/v1/me`, `PUT /api/v1/me/contact-list-view`, `PUT /api/v1/notification-channels/{channel}`, `PUT /api/v1/notification-preferences`, `PUT /api/v1/vaults/{vault}`, `PUT /api/v1/entity-types/{entityType}`, `PUT /api/v1/templates/{template}`, `PUT /api/v1/templates/{template}/versions/{version}/pages/{page}`, `PUT /api/v1/templates/{template}/versions/{version}/sections/{section}`, `PUT /api/v1/templates/{template}/versions/{version}/sections/{section}/fields/{field}`, `PUT /api/v1/life-event-categories/{lifeEventCategory}`, `PUT /api/v1/life-event-types/{lifeEventType}`, `PUT /api/v1/life-event-types/{lifeEventType}/fields`, `PUT /api/v1/relationship-categories/{relationshipCategory}`, `PUT /api/v1/relationship-types/{relationshipType}`, `PUT /api/v1/locations/{location}`, `PUT /api/v1/possession-types/{possessionType}`, `PUT /api/v1/possession-types/{possessionType}/groups/{group}`, `PUT /api/v1/possession-types/{possessionType}/fields/{field}`, `PUT /api/v1/possession-tags/{possessionTag}`, `PUT /api/v1/possession-conditions/{possessionCondition}`, `PUT /api/v1/vaults/{vault}/possessions/{possession}`, `PUT /api/v1/vaults/{vault}/contact-list-columns`, `PUT /api/v1/vaults/{vault}/contacts/{contact}/name`, `PUT /api/v1/vaults/{vault}/contacts/{contact}/name-representations`, `PUT /api/v1/vaults/{vault}/contacts/{contact}/sections/{section}`, `PUT /api/v1/vaults/{vault}/contacts/{contact}/reminders/{reminder}`, `PUT /api/v1/vaults/{vault}/life-events/{lifeEvent}`, `PUT /api/v1/vaults/{vault}/groups/{group}/notes/{note}`, `PUT /api/v1/vaults/{vault}/groups/{group}/reminders/{reminder}`
- `role_b left out keeps its role rather than copying role_a` (Changed): `PUT /api/v1/relationship-types/{relationshipType}`

## In the same release

- Added: [List the value lists of the account](https://my.monicahq.com/docs/api/changelog/value-lists.md)
- Added: [List every reminder of a vault](https://my.monicahq.com/docs/api/changelog/vault-reminders.md)
- Added: [A reminder names the contact it is about](https://my.monicahq.com/docs/api/changelog/reminder-contact-attribute.md)
- Added: [Adds the changes of What’s new](https://my.monicahq.com/docs/api/changelog/changelog-entries.md)

## Example

Renaming a vault

Before:

```
{"name": "Scranton", "description": "The branch.", "colour": "#9a3f2b"}
```

After:

```
{"name": "Scranton"}
```
