---
title: "Update Metric Roll Up Color Threshold"
method: PATCH
path: "/scorers/{scorer_id}/metric-roll-up-config"
tags: ["metric_roll_up"]
---

# Update Metric Roll Up Color Threshold

`PATCH /scorers/{scorer_id}/metric-roll-up-config`

Update only the color_threshold_config on an existing MetricRollUpConfig.

Does not alter roll_up_methods. Pass null to clear the color thresholds.
Omitting the field entirely is a no-op.

## Path parameters

- `scorer_id` string, uuid4, required

## Request body

- UpdateMetricRollUpColorThresholdRequest — Request to update only the color_threshold_config on an existing MetricRollUpConfig. Omitting `color_threshold_config` is a no-op — only an explicitly sent field (even if null) is written. Send null to clear the stored threshold.
  - `color_threshold_config` MetricColorPickerNumeric — Color picker configuration for numeric metrics. Each constraint maps a numeric condition to a color. The UI uses these constraints to color-code metric values (e.g. green for high scores, red for low scores). Example: { "type": "numeric", "constraints": [ {"color": "green", "operator": "gte", "value": 0.8}, {"color": "yellow", "operator": "between", "value": [0.3, 0.8]}, {"color": "red", "operator": "lt", "value": 0.3} ] }
    - `type` 'numeric'
    - `constraints` NumericColorConstraintOutput[], required
      - `color` 'red' | 'yellow' | 'green', required — Allowed colors for metric threshold visualization in the UI.
      - `operator` 'eq' | 'gt' | 'gte' | 'lt' | 'lte' | 'between', required
      - `value` union, required
        - number
        - number[]

## Response `200`

Successful Response

- MetricRollUpConfigResponse — Response for a metric roll up configuration.
  - `roll_up_methods` union, required — List of roll up methods to apply to the metric. For numeric scorers we support doing multiple roll up types per metric.
    - NumericRollUpMethod[]
    - CategoricalRollUpMethod[]
  - `color_threshold_config` MetricColorPickerNumeric — Color picker configuration for numeric metrics. Each constraint maps a numeric condition to a color. The UI uses these constraints to color-code metric values (e.g. green for high scores, red for low scores). Example: { "type": "numeric", "constraints": [ {"color": "green", "operator": "gte", "value": 0.8}, {"color": "yellow", "operator": "between", "value": [0.3, 0.8]}, {"color": "red", "operator": "lt", "value": 0.3} ] }
    - `type` 'numeric'
    - `constraints` NumericColorConstraintOutput[], required
      - `color` 'red' | 'yellow' | 'green', required — Allowed colors for metric threshold visualization in the UI.
      - `operator` 'eq' | 'gt' | 'gte' | 'lt' | 'lte' | 'between', required
      - `value` union, required
        - number
        - number[]
  - `id` string, uuid4, required
  - `organization_id` string, uuid4, required
  - `scorer_id` string, uuid4, required
  - `metric_name` string, required
  - `created_at` string, date-time, required
  - `updated_at` string, date-time, required

## Other responses

- `422` — Validation Error

---

[API](https://skmtc.net/galileo/apis/galileo-api-server.md) · [All operations](https://skmtc.net/galileo/apis/galileo-api-server/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/galileo/galileo-api-server/revisions/ec2affc66693/schema)