Update configuration value
Update a configuration’s value. Only the value can be changed after creation.
The configuration is identified by its own id (find it with the list endpoint), not by the ID of the model,
project, or organization it applies to.
For retention settings, the update is applied asynchronously. The response returns the configuration
with its previous value. The stored value changes only after the new retention period has been applied
to the underlying data. Poll the get endpoint until value shows the new value.
What a shorter retention period deletes depends on the setting:
PROD_EVENTS_TTL_DAYSon aMODEL: existing events older than the new period are permanently deleted by background processes over the following hours.GENAI_METRICS_TTL_DAYS: existing metrics older than the new period are permanently deleted as ClickHouse merges data in the background; timing is not guaranteed.GENAI_TRACES_TTL_DAYS: only data ingested after the change gets the new period. Existing traces keep the expiry date they were given when ingested.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Path Parameters
The configuration's own id, as returned by the list or create endpoints. This is not the ID of the model, project, or organization the configuration applies to.
Body
Configuration value. The format depends on the configuration type (determined by the name field).
The value must be one of:
- Boolean:
trueorfalse(for BoolConfigValue) - Integer:
123(for IntConfigValue) - Float:
123.45(for FloatConfigValue) - String:
"string"(for StringConfigValue)
The actual type is determined by the configuration name and validated against the config registry.