CONTENT_ENABLED

A reserved Boolean setting. Ovok accepts and stores it, but no Ovok route reads it today: turning it on or off changes nothing.

Type	Boolean setting
Change with	PUT /v1/project/settings/CONTENT_ENABLED
Who can change it	Project admin
When unset	Reads as false; the value has no effect either way
Set on new projects	Not set by any project-creation route
Effect today	None

Why it is listed

CONTENT_ENABLED is one of the keys that GET /v1/project/settings returns and PUT /v1/project/settings/:key accepts, so it appears in the settings record of every project.

curl --request PUT \
  --url 'https://api.sandbox.ovok.com/v1/project/settings/CONTENT_ENABLED' \
  --header "Authorization: Bearer ${OVOK_TOKEN}" \
  --header 'Content-Type: application/json' \
  --data '{"enabled":true}'

The response is the full settings record, so you can confirm the value was stored. Storing it changes no behaviour.

Gotchas

• Do not use it as a feature gate. No Ovok route checks it, so it cannot restrict or enable anything.
• Do not build your own logic on it. Its meaning is not defined, so treat the current value as meaningless.
• It is not a project feature. Features are the names you manage with PATCH /v1/projects/me/features; this key lives with the settings, and enabling it does not add anything to the feature list.
• Writes still follow the normal rules. Admin only, and a concurrent change answers 409; read the settings again and retry.

Related

• MAILING_ENABLED
• Settings and features