Get Preferences

What lifecycle email this family currently gets.

Read-only on purpose. These preferences live in users.personalization.notifications, beside the email_updates and push_enabled flags the app's notification screen already owns, and the Settings screen changes them the same way it changes those two:

PATCH /users/{id}/personalization
{"notifications": { ...the whole notifications object... }}

That endpoint merges at the top level, so the screen must send the object complete. Keeping the write there means one screen owns notifications, and nothing in the lifecycle system ever writes the users table.

patch_example is that body, prefilled with the current values, so a client can change one toggle and send it back.