late-sdk 0.0.837 → 0.0.838

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 43716434b61f41adcbff28c9bb8791d5b7f9ec32e99316ce8754ef59bc32ab84
-  data.tar.gz: 4e07bc1a460a6d183cde204b16cfaf2b719127a410c8a3a0ac597b42a8b5eb84
+  metadata.gz: 65464e7e3428719a99cda5a52821ebd91a3799fa71a9edfee5039239c8da12aa
+  data.tar.gz: e7203c87eaaeb72a1749fa4b4f5366dc169ccb8eeaf0c7c87c48635da5080fa0
 SHA512:
-  metadata.gz: 67ba627456e443b641206eb57b0560b19153166566830a7f95af8e97fe65974593d0fee28fb964c60578bd6c5e35699d31ed99426dd1842d45e9f64e3a2c764a
-  data.tar.gz: f905f7a6b184673d982f2e234b51cbdf2f634c7ddd98ac6b50d48e3d6732bed982a01526b2ca64db4dc4b98d5ffed26ff850e9611b23b59d40ecf34f3fa98e64
+  metadata.gz: 86f445355c3ea21698e62a008aeee0936ede4ec97433eee63a7e4545573efd3d964cad380965aff60ce8e95efb374e0521f4c0c8fa766b295f06dd28b70a81a4
+  data.tar.gz: de2d2d5764faf3faa323432953dac73ce4466713cdf161ccc6c7aa892960bf6e14c397fc2d051f9f54c890a27f60c73c1c5bf8ac7b29101aa1a50a8ed7138b73

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