[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"insight-klaviyo-openapi-2026-07-16-remove-required-constraint-on-city-and-mark-it-nullable":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},"01KXNKP0N0Q498CFHSH093QA78","2026-07-16-remove-required-constraint-on-city-and-mark-it-nullable","Breaking","Remove required constraint on 'city' and mark it nullable","The **`city`** field in the `ContactInformation`-adjacent schema (likely a location\u002Faddress object) has had its `required` constraint removed and is now marked `nullable: true`. This is a **breaking change for clients that rely on `city` always being present** in responses — code that accesses `city` without a null check may now encounter `null` or a missing field. Clients sending requests that previously relied on server-side validation rejecting missing `city` values will also see different behaviour.","2026-07-16T14:00:57.248Z"]