Change one setting for your organization.
Send either {"value": ...} or the bare value — both are accepted. The
value is validated against the setting’s schema before it is stored, and the
updated row is returned. The change applies only to your organization.
Two keys carry an extra check and reject with 422:
default_user_permissions must name a permission set that exists in this
org, and allowed_sign_ins may not be saved as a list that excludes the
operator making the change — that list filters who may sign in, and the
settings page is behind that sign-in, so there would be no way back in.
Authorizations
A scoped AgentEye API key. Mint one in the dashboard under Settings → API keys, or with POST /v1/keys. Each endpoint names the permission it requires; a key without it gets 403 and a required_permission field naming what was missing.
Path Parameters
The setting key, as listed by GET /settings/schema.
Body
The body is of type any.
Response
The updated setting.

