[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-datadog-v2-openapi-2026-05-26-remove-scope-field-from-recommendationsfilterrequest":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},"01KSJQ582EKF8W4RGCRN404JVY","2026-05-26-remove-scope-field-from-recommendationsfilterrequest","Breaking","Remove `scope` field from RecommendationsFilterRequest","The `scope` property has been removed from the `RecommendationsFilterRequest` schema. Clients that currently pass `scope` (e.g. `\"experiment\"` or `\"*\"`) in their recommendations filter request body will no longer have this field recognized by the API, which may silently change behavior or cause validation errors depending on server-side handling.","2026-05-26T18:01:11.502Z"]