---
title: "Changes to Add a record to the dataset"
method: POST
path: "/v1/observability/datasets/{dataset_id}/records"
---

# Changes to Add a record to the dataset

`POST /v1/observability/datasets/{dataset_id}/records`

> Every recorded change to this endpoint, newest first.

## Timeline

Changed in 3 of 5 revisions.

- **2026-09-23** `fa73befe1c61` — 31 warning, 36 info
- **2026-08-14** `61436a496404` — 5 warning
- **2026-07-26** `933c4ebdcd72` — 1 breaking, 1 warning, 1 info

## Changes

- **2026-09-23** `fa73befe1c61` — 31 warning, 36 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`
  - added the new `TELEMETRY_SPAN` enum value to the `source` response property for the response status `201`
  - added the new optional request property `source`
  - 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`
  - …27 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`
- **2026-07-26** `933c4ebdcd72` — 1 breaking, 1 warning, 1 info
  - removed the required property `payload/messages` from the response with the `201` status
  - removed the request property `payload/messages`
  - the request property `properties` became optional

---

[Operation](https://skmtc.dev/mistral/apis/mistral-ai-api/docs/v1/observability/datasets/:dataset_id/records/post.md) · [API](https://skmtc.dev/mistral/apis/mistral-ai-api.md) · [Page](https://skmtc.dev/mistral/apis/mistral-ai-api/changes/v1/observability/datasets/:dataset_id/records/post)