---
title: "Changes to Get options for a span evaluation field"
method: GET
path: "/v1/observability/spans/evaluations/fields/{field_name}/options"
---

# Changes to Get options for a span evaluation field

`GET /v1/observability/spans/evaluations/fields/{field_name}/options`

> Every recorded change to this endpoint, newest first.

## Timeline

Changed in 2 of 5 revisions.

- **2026-09-23** `fa73befe1c61` — 30 warning, 35 info
- **2026-08-14** `61436a496404` — 5 warning

## Changes

- **2026-09-23** `fa73befe1c61` — 30 warning, 35 info
  - added the new `EVALUATION_RUN_OUTPUT_RECORD_CONFLICT` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `400`
  - added the new `EVALUATION_RUN_OUTPUT_RECORD_CONFLICT` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `404`
  - added the new `EVALUATION_RUN_OUTPUT_RECORD_CONFLICT` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `408`
  - added the new `EVALUATION_RUN_OUTPUT_RECORD_CONFLICT` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `409`
  - added the new `EVALUATION_RUN_OUTPUT_RECORD_CONFLICT` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `422`
  - added the new `PIPELINE_CONFIG_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `400`
  - added the new `PIPELINE_CONFIG_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `404`
  - added the new `PIPELINE_CONFIG_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `408`
  - added the new `PIPELINE_CONFIG_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `409`
  - added the new `PIPELINE_CONFIG_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `422`
  - added the new `PIPELINE_CONFIG_NOT_FOUND` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `400`
  - added the new `PIPELINE_CONFIG_NOT_FOUND` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `404`
  - added the new `PIPELINE_CONFIG_NOT_FOUND` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `408`
  - added the new `PIPELINE_CONFIG_NOT_FOUND` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `409`
  - added the new `PIPELINE_CONFIG_NOT_FOUND` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `422`
  - added the new `SCORER_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `400`
  - added the new `SCORER_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `404`
  - added the new `SCORER_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `408`
  - added the new `SCORER_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `409`
  - added the new `SCORER_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `422`
  - added the new `SCORER_CONFIG_KIND_MISMATCH` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `400`
  - added the new `SCORER_CONFIG_KIND_MISMATCH` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `404`
  - added the new `SCORER_CONFIG_KIND_MISMATCH` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `408`
  - added the new `SCORER_CONFIG_KIND_MISMATCH` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `409`
  - added the new `SCORER_CONFIG_KIND_MISMATCH` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `422`
  - added the new `SCORER_NOT_FOUND` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `400`
  - added the new `SCORER_NOT_FOUND` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `404`
  - added the new `SCORER_NOT_FOUND` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `408`
  - added the new `SCORER_NOT_FOUND` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `409`
  - added the new `SCORER_NOT_FOUND` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `422`
  - removed the `CAMPAIGN_NOT_FOUND` enum value from the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `400`
  - removed the `CAMPAIGN_NOT_FOUND` enum value from the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `404`
  - removed the `CAMPAIGN_NOT_FOUND` enum value from the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `408`
  - removed the `CAMPAIGN_NOT_FOUND` enum value from the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `409`
  - removed the `CAMPAIGN_NOT_FOUND` enum value from the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `422`
  - removed the `CAMPAIGN_NO_MATCHING_EVENTS` enum value from the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `400`
  - removed the `CAMPAIGN_NO_MATCHING_EVENTS` enum value from the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `404`
  - removed the `CAMPAIGN_NO_MATCHING_EVENTS` enum value from the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `408`
  - removed the `CAMPAIGN_NO_MATCHING_EVENTS` enum value from the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `409`
  - removed the `CAMPAIGN_NO_MATCHING_EVENTS` enum value from the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `422`
  - …25 more
- **2026-08-14** `61436a496404` — 5 warning
  - added the new `OPTIMIZATION_TRIAL_KEY_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `400`
  - added the new `OPTIMIZATION_TRIAL_KEY_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `404`
  - added the new `OPTIMIZATION_TRIAL_KEY_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `408`
  - added the new `OPTIMIZATION_TRIAL_KEY_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `409`
  - added the new `OPTIMIZATION_TRIAL_KEY_ALREADY_EXISTS` enum value to the `detail/error_code/anyOf[subschema #1: ObservabilityErrorCode]/` response property for the response status `422`

---

[Operation](https://skmtc.dev/mistral/apis/mistral-ai-api/docs/v1/observability/spans/evaluations/fields/:field_name/options/get.md) · [API](https://skmtc.dev/mistral/apis/mistral-ai-api.md) · [Page](https://skmtc.dev/mistral/apis/mistral-ai-api/changes/v1/observability/spans/evaluations/fields/:field_name/options/get)