Update Etherforce Settings
PUT /api/data/settings/etherforce
Apply a partial update to Etherforce settings and persist to disk.
Only fields explicitly set on the request body (i.e. non-None after
model_dump(exclude_none=True)) are touched. The live in-memory
config is mutated first so subsequent reads see the new values, then
the partial dict is merged into user_settings.json, and finally
the conduit is asked to reload its cached config snapshot.
Request Body required
Section titled “Request Body required ”Partial update payload — only non-None fields are applied.
Mirrors :class:EtherforceSettingsResponse minus a few of the more
specialised tunables that the UI does not yet expose. Validation
bounds protect against pathological values (e.g. zero timeouts that
would deadlock long-running handlers, or values large enough to mask
real bugs as “still running”).
object
Responses
Section titled “ Responses ”Successful Response
Shared response envelope for every settings update endpoint.
status is "success" when at least one field changed, "noop"
when the request carried no updatable fields. updated_fields lists the
snake_case keys that were actually persisted so the caller can display
exactly what changed.
object
Validation Error