Update an investor preference
/investor-preferences/{id}Changes state (enabled or disabled), enforcement_type or editable and returns the preference. The changes are applied together or not at all. A body that changes nothing returns the preference unchanged and emits nothing. name and form_id are read-only, and classifications change through /investor-preferences/{id}/classifications. dry_run shows the result without saving it. Emits investor_preference.updated; no email. Sending the previous values undoes it.
Path parameters
The record's id.
Query parameters
Validate and run the call without committing it, returning what the real call would return with
meta.dry_runset.
Request body
application/json, required · InvestorPreferenceUpdate
- One of:
enabledasks investors the preference;disabledstops asking.enabled,disabled - One of:
noneleaves the preference optional,popupshows investors a prompt,forcedrequires an answer.none,popup,forced Whether investors can change their answers after giving them.
{
"state": "enabled",
"enforcement_type": "popup"
}Responses
{
"data": {
"id": "4f7c1d2e-8a3b-4c5d-9e6f-0a1b2c3d4e5f",
"name": "Quarterly updates",
"form_id": "9b8a7c6d-5e4f-4a3b-8c2d-1e0f9a8b7c6d",
"state": "enabled",
"enforcement_type": "popup",
"editable": true,
"created_at": "2026-06-15T10:30:00Z",
"updated_at": "2026-06-15T10:30:00Z"
}
}Authorization failed. error.code is one of org_disabled,
ip_blocked, missing_scope, scope_disabled, user_disabled.
The request conflicts with existing state (error.code = conflict),
e.g. a compliance flow with the requested name already exists.
The request can't be processed (HTTP 422): validation_failed with one ErrorDetail per
problem, or a code documented on the operation.
Examples
curl -X PATCH https://your-org-domain/kong/core/api/v2/investor-preferences/{id}\
-H "Authorization: Bearer $HELM_API_KEY"\
-H "Content-Type: application/json"\
-d '{
"state": "enabled",
"enforcement_type": "popup"
}'