zernio-sdk 0.0.837 → 0.0.838

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c553f997ab7a6b667fcb7737c9620d964ea06df02add35b5fb94d9d7bc07a650
-  data.tar.gz: a4fff8427cf2e94b98b12100c826ce5b9b02225b2cd35e011e45fe0ac7a9eea2
+  metadata.gz: d50dd1df50313310c2016cde8524562a2e539382d665f209202c3d307b458c01
+  data.tar.gz: e39d404749d5fe969461329a957e92d8ea6be1b38732e3df3cbe843a19a5b442
 SHA512:
-  metadata.gz: e16cef404587ce1608153c0bf776683deaec89f19b5ebed8897e9bccbc151e61ce40fee95fc8bce520d76954c825d083cd40abc14af624b2bd88a99a3aab3c21
-  data.tar.gz: ac352f6062fd7b64f2f2fbb9d06fa492f02e6edd7000c4af29ad5c1710b57917afac1cf4ca763ea3b2e6f8a755678c6c489f0bfbea6544de734f315ca6a50107
+  metadata.gz: 99852413d2aac736273b560094d27401704bec0d1f07e21f8cbe163b67cb8def9a142aad71ca317a59c02ea6382fac0e22cd40063881c504000148de227b3272
+  data.tar.gz: bf939528f8572adda8185d592a1df1d556a92bd3d76c1c617842bfc066d577bad35a7fdf2087a16d2c08bb72f8e0da5bb8f590e9b59b484a6554d61e31939b41

data/docs/WebhookEventsApi.md

@@ -2852,7 +2852,7 @@ nil (empty response body)
 
 WhatsApp automatic event detected
 
-Fired when Meta's automatic event identification (opt-in during Embedded Signup; not available for EU/UK/JP businesses) detects a lead or purchase in a Click-to-WhatsApp conversation. Branch on `eventName` (`LeadSubmitted` | `Purchase`). Carries the `ctwa_clid` even on coexistence numbers where the inbound referral omits it (this webhook is the only surface that delivers it there); the clid is also written back onto the conversation, so POST /v1/whatsapp/conversions becomes usable for the thread. 
+Fired when Meta's automatic event identification (opt-in during Embedded Signup; not available for EU/UK/JP businesses) detects a lead or purchase in a Click-to-WhatsApp conversation. Branch on `eventName` (`LeadSubmitted` | `Purchase`). Carries the `ctwa_clid`. Meta omits that clid on a minority of referrals on any number (coexistence or not, most often WhatsApp Status placements); when it does, this event can supply it and Zernio writes it back onto the conversation, so POST /v1/whatsapp/conversions becomes usable for the thread. 
 
 ### Examples
 

data/lib/zernio-sdk/api/webhook_events_api.rb

@@ -2726,7 +2726,7 @@ module Zernio
     end
 
     # WhatsApp automatic event detected
-    # Fired when Meta's automatic event identification (opt-in during Embedded Signup; not available for EU/UK/JP businesses) detects a lead or purchase in a Click-to-WhatsApp conversation. Branch on `eventName` (`LeadSubmitted` | `Purchase`). Carries the `ctwa_clid` even on coexistence numbers where the inbound referral omits it (this webhook is the only surface that delivers it there); the clid is also written back onto the conversation, so POST /v1/whatsapp/conversions becomes usable for the thread. 
+    # Fired when Meta's automatic event identification (opt-in during Embedded Signup; not available for EU/UK/JP businesses) detects a lead or purchase in a Click-to-WhatsApp conversation. Branch on `eventName` (`LeadSubmitted` | `Purchase`). Carries the `ctwa_clid`. Meta omits that clid on a minority of referrals on any number (coexistence or not, most often WhatsApp Status placements); when it does, this event can supply it and Zernio writes it back onto the conversation, so POST /v1/whatsapp/conversions becomes usable for the thread. 
     # @param on_whats_app_automatic_event_request [OnWhatsAppAutomaticEventRequest] 
     # @param [Hash] opts the optional parameters
     # @return [nil]
@@ -2736,7 +2736,7 @@ module Zernio
     end
 
     # WhatsApp automatic event detected
-    # Fired when Meta's automatic event identification (opt-in during Embedded Signup; not available for EU/UK/JP businesses) detects a lead or purchase in a Click-to-WhatsApp conversation. Branch on `eventName` (`LeadSubmitted` | `Purchase`). Carries the `ctwa_clid` even on coexistence numbers where the inbound referral omits it (this webhook is the only surface that delivers it there); the clid is also written back onto the conversation, so POST /v1/whatsapp/conversions becomes usable for the thread. 
+    # Fired when Meta's automatic event identification (opt-in during Embedded Signup; not available for EU/UK/JP businesses) detects a lead or purchase in a Click-to-WhatsApp conversation. Branch on `eventName` (`LeadSubmitted` | `Purchase`). Carries the `ctwa_clid`. Meta omits that clid on a minority of referrals on any number (coexistence or not, most often WhatsApp Status placements); when it does, this event can supply it and Zernio writes it back onto the conversation, so POST /v1/whatsapp/conversions becomes usable for the thread. 
     # @param on_whats_app_automatic_event_request [OnWhatsAppAutomaticEventRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers

data/lib/zernio-sdk/version.rb

@@ -11,5 +11,5 @@ Generator version: 7.19.0
 =end
 
 module Zernio
-  VERSION = '0.0.837'
+  VERSION = '0.0.838'
 end

data/openapi.yaml

@@ -10253,11 +10253,12 @@ webhooks:
         Fired when Meta's automatic event identification (opt-in during
         Embedded Signup; not available for EU/UK/JP businesses) detects a
         lead or purchase in a Click-to-WhatsApp conversation. Branch on
-        `eventName` (`LeadSubmitted` | `Purchase`). Carries the `ctwa_clid`
-        even on coexistence numbers where the inbound referral omits it (this
-        webhook is the only surface that delivers it there); the clid is also
-        written back onto the conversation, so POST /v1/whatsapp/conversions
-        becomes usable for the thread.
+        `eventName` (`LeadSubmitted` | `Purchase`). Carries the `ctwa_clid`.
+        Meta omits that clid on a minority of referrals on any number
+        (coexistence or not, most often WhatsApp Status placements); when it
+        does, this event can supply it and Zernio writes it back onto the
+        conversation, so POST /v1/whatsapp/conversions becomes usable for the
+        thread.
       tags: [Webhook Events]
       requestBody:
         required: true