[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-klaviyo-openapi-2026-05-16-data-field-type-constraints-removed-now-accepts-any-type":3},{"source":4,"alert":11},{"id":5,"displayName":6,"vendor":7,"kind":8,"apiType":9,"url":10},"klaviyo-openapi","Klaviyo API","klaviyo","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fklaviyo\u002Fopenapi\u002Fmain\u002Fopenapi\u002Fstable.json",{"id":12,"slug":13,"severity":14,"title":15,"summary":16,"detectedAt":17},"01KRREVA2K6T33WEHBB5DJB4SR","2026-05-16-data-field-type-constraints-removed-now-accepts-any-type","Breaking","data field type constraints removed, now accepts any type","The `data` field previously declared a `oneOf` constraint accepting `integer`, `number`, `string`, or `boolean` types; that constraint has been removed, leaving only `nullable: true`. This is a schema loosening on the spec side, but clients that relied on the documented type union for validation or code generation will now see an untyped\u002F`any` field, which could break generated SDK models or strict validators expecting a known type.","2026-05-16T13:15:42.035Z"]