FlowSettingsResponse

The saved settings in the same shape PUT /v1/flow-settings accepts, so you can read them, change a field and save them back. Null means no settings have been saved. For a church, this is the appearance in effect for it (its overrides on top of your default); to change the church, edit church_settings instead.

Version of these settings: 0 before the first save, then one more on every save, from the API or the partner portal. Saved settings never read 0: settings saved before versions were counted read 1. Send it back as expected_version when you save. With church_id, the version of that church's own settings; a change to your default does not change it.

Only with church_id: what that church itself stores, in the shape PUT /v1/flow-settings accepts with church_id. Null means the church follows your default as is. A save with church_id replaces this whole object: apply your change to it and send it back with version as expected_version.

Only in the response to PUT /v1/flow-settings, where it is always present: the properties that were saved before the request and are not saved after it, named by their path in the request body, such as display_name or customization.css.padding. Without church_id, compared with your previous default; with church_id, with what the church stored before. A property whose value changed is not listed. Empty when the save removed nothing. If it lists a property you meant to keep, save again with it.