[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-datadog-v2-openapi-2026-05-19-new-required-fields-created-at-and-modified-at-added-to":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"datadog-v2-openapi","Datadog API v2","datadog","openapi-yaml","rest","https:\u002F\u002Fraw.githubusercontent.com\u002FDataDog\u002Fdatadog-api-client-typescript\u002Fmaster\u002F.generator\u002Fschemas\u002Fv2\u002Fopenapi.yaml",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KS0560BHNMH772K8JX92RPBD","2026-05-19-new-required-fields-created-at-and-modified-at-added-to","Breaking","New required fields created_at and modified_at added to LLMObs interaction schemas","Two new fields, **`created_at`** and **`modified_at`** (both `date-time` strings), have been added as **required** properties to the `LLMObsTraceInteraction` and `LLMObsTraceInteractionItem` schemas. Because these fields are marked `required`, any client code that constructs or validates these objects must now supply both timestamps, otherwise requests or deserialization will fail. Clients that only read these objects (e.g. parsing API responses) may be unaffected if the server always returns them, but strict schema validators or typed SDK models will break on existing payloads that lack the fields.","2026-05-19T13:00:42.225Z"]