[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fjVMfDSSNErhDLRM-CWf9ENTOrubDraFGiwPGyx0B61I":3,"$fhmL7ckVsYd0cJH-Hfkf1o2NTqOCXMO2KTMF770pxxgg":21},{"status":4,"source":5,"previous":12,"current":16,"newerSnapshotId":20,"olderSnapshotId":13},"has-previous",{"id":6,"displayName":7,"vendor":8,"kind":9,"apiType":10,"url":11},"klaviyo-openapi","Klaviyo API","klaviyo","openapi-json","rest","https:\u002F\u002Fraw.githubusercontent.com\u002Fklaviyo\u002Fopenapi\u002Fmain\u002Fopenapi\u002Fstable.json",{"id":13,"contentHash":14,"fetchedAt":15},"01KWPPWQX4QNB0AGC721B746A6","a75352fcd38cf5602694aeca42f931aa3e60bb45613857861536e071522640f2","2026-07-04T14:00:35.095Z",{"id":17,"contentHash":18,"fetchedAt":19},"01KX10FXA8AZH33YFX8V28JFD9","8c9eb80ed5673fb9134adc29622d7e76e95b570bb4c7a529f24f31990c333836","2026-07-08T14:00:44.813Z",null,{"alerts":22},[23,30,36,43,50,58,65,72,80,87,94,101,108,115,122,129,136,143,150,157],{"id":24,"severity":25,"title":26,"summary":27,"contentHash":18,"detectedAt":28,"slug":29},"01KX10G1PE42WTXX15YX1HVGS1","Additive","Add channel field to Conversation object and enum options","The Klaviyo API adds a new required `attributes` object to the **Conversation** resource with a required `channel` field that can be `instagram`, `sms`, or `whatsapp`. Additionally, `channel` is added as an optional enum value to several field filters. This change adds new response fields and makes the `attributes` object required in the Conversation response schema.","2026-07-08T14:00:50.126Z","2026-07-08-add-channel-field-to-conversation-object-and-enum-options",{"id":31,"severity":25,"title":32,"summary":33,"contentHash":14,"detectedAt":34,"slug":35},"01KWPPWW09KNRD7ZHMMW2TCRQZ","Add message_hierarchy field to push message definitions","A new optional `message_hierarchy` field has been added to multiple push message definition schemas across the Klaviyo API. This field is nullable and describes an RCS\u002FSMS message hierarchy (fallback chain) with format and content information. The change is purely additive and does not affect existing integrations.","2026-07-04T14:00:40.201Z","2026-07-04-add-message-hierarchy-field-to-push-message-definitions",{"id":37,"severity":25,"title":38,"summary":39,"contentHash":40,"detectedAt":41,"slug":42},"01KWHJ3K4B4KNWSDJ6W5RCSF30","Add font_style and text_decoration fields to text properties","Two new optional response fields—`font_style` and `text_decoration`—have been added to text styling properties in the Klaviyo API. Both fields are nullable strings and do not affect existing integrations.","344114efb58434199db4cb91ebc357c8f8e2f664dda9a46b492b3262d061da00","2026-07-02T14:00:45.451Z","2026-07-02-add-font-style-and-text-decoration-fields-to-text-properties",{"id":44,"severity":25,"title":45,"summary":46,"contentHash":47,"detectedAt":48,"slug":49},"01KWEZQ58P1ZZVRM2Q47C24XXK","Add email open tracking consent fields to subscription schemas","The Klaviyo API introduces new email open tracking consent support with a new `OpenTrackingConsent` schema and updates to `EmailChannel`, `EmailSubscriptionParameters`, and `EmailUnsubscriptionParameters` to include optional `open_tracking` fields. Existing integrations remain unaffected as all new fields are optional and the new schema parameters are nullable, enabling gradual adoption of open tracking consent management.","10287e1aa37c14a4a93d7d7c90bd86b4f1d1b610f19b309c21b13ff0d4628d6c","2026-07-01T14:00:54.806Z","2026-07-01-add-email-open-tracking-consent-fields-to-subscription",{"id":51,"severity":52,"title":53,"summary":54,"contentHash":55,"detectedAt":56,"slug":57},"01KWCDA19SMJZ8NKD3DBCZ98SM","Informational","Bulk catalog API rate limits updated in documentation","Rate limit values for six catalog bulk operation endpoints have been updated from `350\u002Fs` burst and `3500\u002Fm` steady to `75\u002Fs` burst and `750\u002Fm` steady. This is a **documentation change only**—the actual rate limits applied by the API have changed, but the endpoint signatures, request\u002Fresponse formats, and SDK interfaces remain unchanged.","5152720848ffffd324e1b2dca3df6070aedda86c3c471a08d9bb93b0a39ea733","2026-06-30T14:00:41.529Z","2026-06-30-bulk-catalog-api-rate-limits-updated-in-documentation",{"id":59,"severity":25,"title":60,"summary":61,"contentHash":62,"detectedAt":63,"slug":64},"01KVZHAQ2V7ZV073NJJEMFCW41","Form Version response and query parameters expanded","The GET `\u002Fapi\u002Fform-versions` endpoint adds optional query parameters `fields[form]` and `include` for sparse fieldsets and relationship inclusion, plus a new `included` array in the response. The response schema renamed from `GetFormVersionResponse` to `GetFormVersionResponseCompoundDocument` with a new `relationships.form` object on form versions. Additionally, the daily rate limit for image uploads increases from 100 to 500 requests\u002Fday, and \"Message Format\" is added as a filter\u002Fsort option for reports.","f1a78dabecdc57ba32fa50a1b26de3f877cd7f5198db2b7d03e66d2df5f4d5f4","2026-06-25T14:00:50.523Z","2026-06-25-form-version-response-and-query-parameters-expanded",{"id":66,"severity":25,"title":67,"summary":68,"contentHash":69,"detectedAt":70,"slug":71},"01KVWYXZ4ZPQ72SJGAX99ASQGD","WhatsApp phone_number field now nullable, removed from required","The `phone_number` field in three WhatsApp channel schemas (`WhatsappTransactionalChannel`, `WhatsappConversationalChannel`, and `WhatsappChannel`) is now marked `nullable: true` and removed from the `required` array. This makes the field optional and allows null values, enabling clients to omit phone numbers when the data is not available. Additionally, a documentation example for the `operator` field was expanded to show a complete filter usage pattern.","42024b58d8283f2c7c65a39c3b51ca3edfde8f0fd0e526ad54a10f0d5b9f6b51","2026-06-24T14:00:49.567Z","2026-06-24-whatsapp-phone-number-field-now-nullable-removed-from",{"id":73,"severity":74,"title":75,"summary":76,"contentHash":77,"detectedAt":78,"slug":79},"01KVQT4G8PYHXNWDG988NA7A2E","Breaking","ProfileEventTrackedProperties.metric no longer required; new enum value added","Two changes in this diff:\n- **`ProfileEventTrackedProperties.metric`** is removed from the `required` array and gains `nullable: true` with a default of `\"\"`. Clients that previously relied on `metric` always being present in responses may break; servers that previously required `metric` in requests no longer do, which is additive for request senders but potentially breaking for consumers expecting it.\n- A new enum value **`\"full\"`** is added to a size\u002Fimage-related field's enum (appears to be an image size selector), which is a purely additive change for that field.","e31ffea8a7229f0a83eff3a5b333abdbba58d92ef15b36e88dadbdb96698d994","2026-06-22T14:00:48.662Z","2026-06-22-profileeventtrackedproperties-metric-no-longer-required-new",{"id":81,"severity":25,"title":82,"summary":83,"contentHash":84,"detectedAt":85,"slug":86},"01KVG2Y0K89HSVJCVDJ10QE9Q0","Add DELETE \u002Fapi\u002Fflow-actions\u002F{id} endpoint","A new `DELETE \u002Fapi\u002Fflow-actions\u002F{id}` endpoint has been added to allow deletion of flow actions. This is a new optional operation that does not break existing code but provides additional functionality for managing flows.","51e3b35a2769bdbae3f77b6784dd19695a0c906e005a8df3cd787cb4be113104","2026-06-19T14:00:37.736Z","2026-06-19-add-delete-api-flow-actions-id-endpoint",{"id":88,"severity":25,"title":89,"summary":90,"contentHash":91,"detectedAt":92,"slug":93},"01KVDGJ0158PM2PPGQEFY9MWWW","Add metric field filtering support to metrics endpoint","The `filter` query parameter on the metrics endpoint now supports filtering by the `metric` field using the `has` operator. This is a purely additive change that expands filtering capabilities without removing or altering existing functionality.","fb79ced9cc6a0043dea192529cba98c051cd8a0f373b89a39fb95443ac6ae33b","2026-06-18T14:01:00.709Z","2026-06-18-add-metric-field-filtering-support-to-metrics-endpoint",{"id":95,"severity":25,"title":96,"summary":97,"contentHash":98,"detectedAt":99,"slug":100},"01KV8BRNZR5SN8GQW92S8HFDNY","Add vendor_id, FlowWhatsApp, and channel fields to Klaviyo API","Added new optional fields to the Klaviyo API: **vendor_id** in message definitions for flow campaigns, a new **FlowWhatsApp** schema type, and a **channel** field for form objects. Also inlined three reusable filter schemas (`ActionOutputConditionFilter`, `MetricPropertyConditionFilter`, `PriceDropConditionFilter`, `LowInventoryConditionFilter`) into their concrete usages, and added a new `IafDeeplinkToScreen` button type. All changes are backward-compatible expansions of the API surface.","de58cb8453a2fbb7cb3c346048c131117dd83e45d7daf019613076ef02fe72f8","2026-06-16T14:01:04.760Z","2026-06-16-add-vendor-id-flowwhatsapp-and-channel-fields-to-klaviyo-api",{"id":102,"severity":74,"title":103,"summary":104,"contentHash":105,"detectedAt":106,"slug":107},"01KTY25FXHRPAVFCM3Z4K2WC7B","EnrollFormAction schema and definition.data.form_id field removed","The **`EnrollFormAction`** and **`EnrollFormActionData`** schemas have been entirely removed from the spec, along with `definition.data.form_id` from the allowed fields list across multiple flow endpoints. `EnrollFormAction` is also removed from all `oneOf` action union types used in flow create\u002Fupdate\u002Fread operations. Any client that references `EnrollFormAction`, uses `type: \"enroll-form\"` actions, or requests\u002Fsends `definition.data.form_id` will break.","5197f5836d58cf01e8f9f1c0fb53e2349e75908e6e9bbecc61cd26e09cc6c35b","2026-06-12T14:00:54.449Z","2026-06-12-enrollformaction-schema-and-definition-data-form-id-field",{"id":109,"severity":25,"title":110,"summary":111,"contentHash":112,"detectedAt":113,"slug":114},"01KTRXBX4918MAZN5STQ43V11H","Add optional accessible_name field to modal properties","A new optional `accessible_name` field (string, nullable) has been added to a modal properties schema. This is a purely additive change that does not affect existing integrations.","4d753f78377a619d8c42a9197d14ecdca051cd2445aff4359267c66aa416e67f","2026-06-10T14:00:49.545Z","2026-06-10-add-optional-accessible-name-field-to-modal-properties",{"id":116,"severity":25,"title":117,"summary":118,"contentHash":119,"detectedAt":120,"slug":121},"01KT9EZCDTVEDPWPVNESRWSPZG","Add web_url field to push notification on_open action","The Klaviyo API now supports a new **`PushOnOpenWebUrl`** schema and adds **`web_url`** as an option in push notification's `definition.options.on_open` configuration. This enables opening external URLs when a push notification is triggered, extending the existing deep-link and app-open capabilities without breaking existing integrations.","3574ab5356f853f090a3bd42559b7b8b2bafd2e77d43f31d5f86edd52991b4bf","2026-06-04T14:00:42.682Z","2026-06-04-add-web-url-field-to-push-notification-on-open-action",{"id":123,"severity":25,"title":124,"summary":125,"contentHash":126,"detectedAt":127,"slug":128},"01KT4A60F042NHRBB498EN16T3","Add web_url field to message objects and open_url action type","The Klaviyo API now exposes a new `web_url` field on message objects and introduces a new `open_url` action type option. Both changes are backward compatible and purely additive — existing integrations continue to work unchanged, and client applications can optionally leverage the new fields to support additional web messaging capabilities.","7e780de9e9c73a3c3114e30f13efe265618ae73462a31af41c63a8d517708cac","2026-06-02T14:00:44.768Z","2026-06-02-add-web-url-field-to-message-objects-and-open-url-action",{"id":130,"severity":25,"title":131,"summary":132,"contentHash":133,"detectedAt":134,"slug":135},"01KST0KZDYP170MJRMSZ8337R1","Add channel affinity conditions and cart content segment type","Added two new predictive analytics condition types (`ProfilePredictiveAnalyticsChannelAffinityPriorityCondition` and `ProfilePredictiveAnalyticsChannelAffinityRankCondition`) across multiple segment endpoints, a new `CartContent` segment condition type that consolidates cart-based properties, and new `SMSDisclosureLinkTextStyle` schema for SMS disclosure styling. Also removed the `url` field requirement from one schema (now has default value) and adjusted `shadow_color` enum in review block styling. These are purely additive changes that expand segment condition options without breaking existing behavior.","c902360569b3ef133d8a1fb6beacf4d24d22c93a49f33170d7fd0782960a64c0","2026-05-29T14:01:12.382Z","2026-05-29-add-channel-affinity-conditions-and-cart-content-segment",{"id":137,"severity":25,"title":138,"summary":139,"contentHash":140,"detectedAt":141,"slug":142},"01KS5DDED916VMHJNSRBCNVJSQ","Make form_id and list_id optional in enrollment form action","The `form_id` and `list_id` fields in the enrollment form action request have been made optional: `form_id` is now nullable and both fields have been removed from the required list. This allows clients to omit these fields when creating or updating enrollment form actions, expanding the API's flexibility.","b7f55cb3116d5f6edf45dc1e41593a38c3d5ceed88a483c1b309ddf6866f3983","2026-05-21T14:00:46.761Z","2026-05-21-make-form-id-and-list-id-optional-in-enrollment-form-action",{"id":144,"severity":74,"title":145,"summary":146,"contentHash":147,"detectedAt":148,"slug":149},"01KS08M9BPXQFCSB7YJVQNSZZG","Flow action fields replaced and new trigger type added in Klaviyo API","In the flow action schema (appears to be `EnrollFormAction` or similar), **`expire_after_unit`** and **`expire_after_value`** have been removed and replaced by a new required field **`form_id`** (string). This is a breaking change for any client that reads or writes these fields, and `form_id` is now listed as `required`, so existing create\u002Fupdate calls omitting it will fail. Additionally, a new **`CustomObjectDateTrigger`** schema has been added and included as a valid option in the flow date trigger `oneOf`, which is purely additive.","dd0e58590a6c05684de2270870b2e5081ec0ad8563f0c37a4d289f172c00370b","2026-05-19T14:00:55.926Z","2026-05-19-flow-action-fields-replaced-and-new-trigger-type-added-in",{"id":151,"severity":74,"title":152,"summary":153,"contentHash":154,"detectedAt":155,"slug":156},"01KRREVA2K6T33WEHBB5DJB4SR","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.","7d6ba2a9f15abea65e0c1aea85b3e95aef6b0da989a6b29192ed5ca4ddceab3c","2026-05-16T13:15:42.035Z","2026-05-16-data-field-type-constraints-removed-now-accepts-any-type",{"id":158,"severity":74,"title":159,"summary":160,"contentHash":161,"detectedAt":162,"slug":163},"01KRK9HTNK56ZNV7N17F4G131F","Remove `data` from required fields in template universal content schema","The field **`data`** has been removed from the `required` array in what appears to be a template universal content request schema. This is potentially breaking for clients that relied on server-side validation rejecting requests missing `data` — however, it could also be a fix making `data` optional, which would be additive. If clients were required to send `data` and the server now accepts requests without it, existing integrations are unaffected, but the change could indicate a schema correction that previously caused valid requests to fail.","3334056ef6e0e78415813ed2b791655ce97a252a71f8f3ca0ccefd09cf3c1fb5","2026-05-14T13:06:56.307Z","2026-05-14-remove-data-from-required-fields-in-template-universal"]