late-sdk 0.0.814 → 0.0.816

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: c95b79b6876df7fb7f4385e253843605d074b4b19457661bd7f9c9af818caa80
-  data.tar.gz: 43aff17db2343a74defc77ae4f4037917e723de09c976707c3638bfcfbc31be9
+  metadata.gz: 3525f01a2062dc2131d0647fdcc7562a2774796b17c10d53066211d8b552a953
+  data.tar.gz: 3e9107679f37470121ddbd7b81ae7daf90a200f608ac0f33d0e662908db87a54
 SHA512:
-  metadata.gz: d98f486356d57acb61514522ae9f7c6aa0d415f84a10b5781b77efeadf0ea6870e508de934a0a9b41ed5dcdeb82fffc1e598b453ed8c96a6b4670f5e2885d095
-  data.tar.gz: 66e8a8121c2106e9106f1dc4f8e01a343ef149d5a029731ed3c8c365bf85ae4b1a3ad3362d352519b1ac30d08cf46c35f678a67649efd5ce6554ac4974b1bf94
+  metadata.gz: e99fdffbd77b99c0a73bbb49050510b21195597e76137daad38700e7b1fb29056ee1849c21dab534a845cff16af5c7826dce3c1ea04a19bbefe7043c6c2f64c9
+  data.tar.gz: 6f38e29b952c553f6f6272bcc53424591a32599d8ff7566cafd10e6c18d4f106183143b4dc7a30dfbdd0a15b064d169521b628afca0d4141bf4b702f69b69dc2

data/docs/GetInboxConversationMessages200ResponseMessagesInner.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **id** | **String** |  | [optional] |
+| **id** | **String** | The platform's own message id: the `wamid` on WhatsApp, the `mid` on Instagram and Facebook Messenger. This is what `metadata.quotedMessageId` points at, the value to pass as `replyTo` on the platforms that support quote-replies, and the `{messageId}` segment of the attachment-resolve URL. Webhooks deliver the same value as `message.platformMessageId`; this response has no field by that name.  | [optional] |
 | **conversation_id** | **String** |  | [optional] |
 | **account_id** | **String** |  | [optional] |
 | **platform** | **String** |  | [optional] |
@@ -30,7 +30,7 @@
 | **sent_at** | **Time** | Original send time for outgoing messages (used for Messenger watermark queries). | [optional] |
 | **delivery_error** | [**GetInboxConversationMessages200ResponseMessagesInnerDeliveryError**](GetInboxConversationMessages200ResponseMessagesInnerDeliveryError.md) |  | [optional] |
 | **reactions** | [**Array<GetInboxConversationMessages200ResponseMessagesInnerReactionsInner>**](GetInboxConversationMessages200ResponseMessagesInnerReactionsInner.md) | Emoji reactions on this message (WhatsApp / Telegram). At most one per party in a 1:1 thread. | [optional] |
-| **metadata** | **Hash<String, Object>** | Platform-specific extras. Free-form, but commonly includes: `quotedMessageId` (platformMessageId this message replies to), `waInteractive` (a compact descriptor of WhatsApp interactive content sent: buttons / list / cta_url / flow / location_request), and for inbound interactive taps `interactiveType` / `interactiveId`. It can also carry `source` (`whatsapp_business_app` / `coexistence_history` on a WhatsApp Coexistence number, `bulk-api` on a POST /v1/whatsapp/bulk send), which is where the message reached us from rather than who produced it: read `sentVia` for that.  | [optional] |
+| **metadata** | **Hash<String, Object>** | Platform-specific extras. Free-form, but commonly includes: `quotedMessageId` (the `id` of the message this one replies to, delivered as `message.platformMessageId` on webhooks), `waInteractive` (a compact descriptor of WhatsApp interactive content sent: buttons / list / cta_url / flow / location_request), and for inbound interactive taps `interactiveType` / `interactiveId`. It can also carry `source` (`whatsapp_business_app` / `coexistence_history` on a WhatsApp Coexistence number, `bulk-api` on a POST /v1/whatsapp/bulk send), which is where the message reached us from rather than who produced it: read `sentVia` for that.  | [optional] |
 | **sent_via** | **String** | Which Zernio surface produced this outgoing message: `human` (an operator in the Zernio inbox), `api` (a call to this API), `broadcast`, `sequence`, `workflow`, `comment_automation`, or `bulk-api` (POST /v1/whatsapp/bulk). Same vocabulary as the `source` filter on the inbox analytics endpoints.  Always present, and `null` whenever the lineage is unknown: every incoming message, any outgoing message sent from the platform's own app, and every message stored before this field shipped (2026-08). Existing messages are NOT backfilled, so treat `null` as \"unknown\", never as \"sent by a human\".  | [optional] |
 
 ## Example

data/docs/SendInboxMessageRequest.md

@@ -19,7 +19,7 @@
 | **reply_markup** | [**SendInboxMessageRequestReplyMarkup**](SendInboxMessageRequestReplyMarkup.md) |  | [optional] |
 | **messaging_type** | **String** | Facebook messaging type. Required when using messageTag. | [optional] |
 | **message_tag** | **String** | Facebook message tag for messaging outside 24h window. Requires messagingType MESSAGE_TAG. Instagram only supports HUMAN_AGENT. | [optional] |
-| **reply_to** | **String** | Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID (both available in message.platformMessageId from webhooks or the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without send-side reply support, including Instagram and Facebook Messenger (Meta's Send API rejects reply_to on Instagram and does not expose it on Messenger). | [optional] |
+| **reply_to** | **String** | Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID (delivered as message.platformMessageId on webhooks, and as `id` on each entry of the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without send-side reply support, including Instagram and Facebook Messenger (Meta's Send API rejects reply_to on Instagram and does not expose it on Messenger). | [optional] |
 | **location** | [**SendInboxMessageRequestLocation**](SendInboxMessageRequestLocation.md) |  | [optional] |
 | **contacts** | [**Array<SendInboxMessageRequestContactsInner>**](SendInboxMessageRequestContactsInner.md) | WhatsApp-only. Send one or more contact cards. | [optional] |
 

data/docs/WebhookEventsApi.md

@@ -1219,7 +1219,7 @@ nil (empty response body)
 
 Message sent event
 
-Fired when a message is sent via the API, or from the WhatsApp Business app on Coexistence numbers. Sends that carry platform-specific context deliver it under `metadata`, so a quote-reply arrives with `metadata.quotedMessageId` and mirroring CRMs can thread it without a lookup. 
+Fired when a message is sent via the API, or from the WhatsApp Business app on Coexistence numbers. Sends that carry platform-specific context deliver it under `metadata`, so a quote-reply sent through the API arrives with `metadata.quotedMessageId` and mirroring CRMs can thread it without a lookup. Which surfaces actually carry that reference is documented on `WebhookPayloadMessageSent.metadata.quotedMessageId`; a quote-reply sent from the WhatsApp Business or Instagram app is not one of them. 
 
 ### Examples
 

data/docs/WebhookPayloadMessageMetadata.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **quoted_message_id** | **String** | platformMessageId of the message this one is a quote-reply to. WhatsApp (`context.id`), Instagram and Facebook Messenger (`reply_to.mid`). Outgoing quote-replies carry the same field on `message.sent`; see WebhookPayloadMessageSent.metadata.  | [optional] |
+| **quoted_message_id** | **String** | platformMessageId of the message this one is a quote-reply to. WhatsApp (`context.id`), Instagram and Facebook Messenger (`reply_to.mid`). On outgoing messages the same field appears on `message.sent`, but only on some surfaces: see WebhookPayloadMessageSent.metadata.quotedMessageId.  | [optional] |
 | **quick_reply_payload** | **String** | Payload from a quick reply tap (Facebook/Instagram Messenger). | [optional] |
 | **postback_payload** | **String** | Payload from a postback button tap (Facebook/Instagram Messenger). | [optional] |
 | **postback_title** | **String** | Title of the tapped postback button (Facebook/Instagram Messenger). | [optional] |

data/docs/WebhookPayloadMessageSentMetadata.md

@@ -4,7 +4,7 @@
 
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
-| **quoted_message_id** | **String** | platformMessageId of the message this send is a quote-reply to. Set when the reply was sent through Zernio with `replyTo` on the inbox send API (WhatsApp and Telegram), and when the operator replied from the native WhatsApp Business, Instagram or Messenger app. WhatsApp API sends carry it on the event fired from the delivery status, so it arrives on the same `message.sent` as any other WhatsApp send.  | [optional] |
+| **quoted_message_id** | **String** | `platformMessageId` of the message this send is a quote-reply to.  Present when the reply was sent through Zernio with `replyTo` on the inbox send API (WhatsApp and Telegram). A WhatsApp API send fires its `message.sent` off the delivery status, and the quote reference is forwarded from the stored send there, so it arrives on the same `message.sent` as any other WhatsApp send.  Not delivered on Instagram echoes. Zernio forwards `reply_to.mid` whenever Meta puts it on an echo, but on Instagram Meta does not send it, so a reply the operator quoted in the Instagram app arrives with no `quotedMessageId`. Facebook Messenger rides a separate subscription (`message_echoes`) and has not been measured, so treat it as unverified rather than supported.  Absent on WhatsApp Coexistence echoes. Meta omits the quote context from `smb_message_echoes`, so a reply the operator sent from the WhatsApp Business app arrives with no `quotedMessageId` even though WhatsApp shows it as a quote-reply. Do not read the absence of this field as \"not a reply\".  | [optional] |
 | **thread_ts** | **String** | Slack only. Parent thread ts of the sent message. Pass it back as `replyTo` on the inbox send API to keep replying inside the thread.  | [optional] |
 
 ## Example

data/docs/WebhooksApi.md

@@ -304,7 +304,7 @@ This endpoint does not need any parameter.
 
 Redeliver a webhook event
 
-Replay a past delivery: the original payload is re-sent, byte for byte, to the subscription's current URL. The original event ID is preserved so your endpoint can dedupe, and the replay is recorded as a fresh attempt, so it shows up in `GET /v1/webhooks/logs` next to the delivery it replays.  Both `webhookId` and `eventId` come from a row of `GET /v1/webhooks/logs`. Because the stored payload is replayed as-is, a redelivery reflects the event as it was emitted, not the current state of the resource.  Only deliveries inside the 30-day log retention window can be replayed; past that the payload is gone and the request fails with a 500. Replays run the same resource-group checks as live delivery, against both the key's groups and the subscription's `disabledResourceGroups`. 
+Replay a past delivery: the original payload is re-sent, byte for byte, to the subscription's current URL. The original event ID is preserved so your endpoint can dedupe, and the replay is recorded as a fresh attempt, so it shows up in `GET /v1/webhooks/logs` next to the delivery it replays.  Both `webhookId` and `eventId` come from a row of `GET /v1/webhooks/logs`. Because the stored payload is replayed as-is, a redelivery reflects the event as it was emitted, not the current state of the resource.  Only deliveries inside the 30-day log retention window can be replayed; past that the payload is gone and the request fails with a 422. Replays run the same resource-group checks as live delivery, against both the key's groups and the subscription's `disabledResourceGroups`. 
 
 ### Examples
 

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

@@ -1142,7 +1142,7 @@ module Zernio
     end
 
     # Message sent event
-    # Fired when a message is sent via the API, or from the WhatsApp Business app on Coexistence numbers. Sends that carry platform-specific context deliver it under `metadata`, so a quote-reply arrives with `metadata.quotedMessageId` and mirroring CRMs can thread it without a lookup. 
+    # Fired when a message is sent via the API, or from the WhatsApp Business app on Coexistence numbers. Sends that carry platform-specific context deliver it under `metadata`, so a quote-reply sent through the API arrives with `metadata.quotedMessageId` and mirroring CRMs can thread it without a lookup. Which surfaces actually carry that reference is documented on `WebhookPayloadMessageSent.metadata.quotedMessageId`; a quote-reply sent from the WhatsApp Business or Instagram app is not one of them. 
     # @param webhook_payload_message_sent [WebhookPayloadMessageSent] 
     # @param [Hash] opts the optional parameters
     # @return [nil]
@@ -1152,7 +1152,7 @@ module Zernio
     end
 
     # Message sent event
-    # Fired when a message is sent via the API, or from the WhatsApp Business app on Coexistence numbers. Sends that carry platform-specific context deliver it under `metadata`, so a quote-reply arrives with `metadata.quotedMessageId` and mirroring CRMs can thread it without a lookup. 
+    # Fired when a message is sent via the API, or from the WhatsApp Business app on Coexistence numbers. Sends that carry platform-specific context deliver it under `metadata`, so a quote-reply sent through the API arrives with `metadata.quotedMessageId` and mirroring CRMs can thread it without a lookup. Which surfaces actually carry that reference is documented on `WebhookPayloadMessageSent.metadata.quotedMessageId`; a quote-reply sent from the WhatsApp Business or Instagram app is not one of them. 
     # @param webhook_payload_message_sent [WebhookPayloadMessageSent] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers

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

@@ -333,7 +333,7 @@ module Zernio
     end
 
     # Redeliver a webhook event
-    # Replay a past delivery: the original payload is re-sent, byte for byte, to the subscription's current URL. The original event ID is preserved so your endpoint can dedupe, and the replay is recorded as a fresh attempt, so it shows up in `GET /v1/webhooks/logs` next to the delivery it replays.  Both `webhookId` and `eventId` come from a row of `GET /v1/webhooks/logs`. Because the stored payload is replayed as-is, a redelivery reflects the event as it was emitted, not the current state of the resource.  Only deliveries inside the 30-day log retention window can be replayed; past that the payload is gone and the request fails with a 500. Replays run the same resource-group checks as live delivery, against both the key's groups and the subscription's `disabledResourceGroups`. 
+    # Replay a past delivery: the original payload is re-sent, byte for byte, to the subscription's current URL. The original event ID is preserved so your endpoint can dedupe, and the replay is recorded as a fresh attempt, so it shows up in `GET /v1/webhooks/logs` next to the delivery it replays.  Both `webhookId` and `eventId` come from a row of `GET /v1/webhooks/logs`. Because the stored payload is replayed as-is, a redelivery reflects the event as it was emitted, not the current state of the resource.  Only deliveries inside the 30-day log retention window can be replayed; past that the payload is gone and the request fails with a 422. Replays run the same resource-group checks as live delivery, against both the key's groups and the subscription's `disabledResourceGroups`. 
     # @param redeliver_webhook_event_request [RedeliverWebhookEventRequest] 
     # @param [Hash] opts the optional parameters
     # @return [UnpublishPost200Response]
@@ -343,7 +343,7 @@ module Zernio
     end
 
     # Redeliver a webhook event
-    # Replay a past delivery: the original payload is re-sent, byte for byte, to the subscription's current URL. The original event ID is preserved so your endpoint can dedupe, and the replay is recorded as a fresh attempt, so it shows up in `GET /v1/webhooks/logs` next to the delivery it replays.  Both `webhookId` and `eventId` come from a row of `GET /v1/webhooks/logs`. Because the stored payload is replayed as-is, a redelivery reflects the event as it was emitted, not the current state of the resource.  Only deliveries inside the 30-day log retention window can be replayed; past that the payload is gone and the request fails with a 500. Replays run the same resource-group checks as live delivery, against both the key's groups and the subscription's `disabledResourceGroups`. 
+    # Replay a past delivery: the original payload is re-sent, byte for byte, to the subscription's current URL. The original event ID is preserved so your endpoint can dedupe, and the replay is recorded as a fresh attempt, so it shows up in `GET /v1/webhooks/logs` next to the delivery it replays.  Both `webhookId` and `eventId` come from a row of `GET /v1/webhooks/logs`. Because the stored payload is replayed as-is, a redelivery reflects the event as it was emitted, not the current state of the resource.  Only deliveries inside the 30-day log retention window can be replayed; past that the payload is gone and the request fails with a 422. Replays run the same resource-group checks as live delivery, against both the key's groups and the subscription's `disabledResourceGroups`. 
     # @param redeliver_webhook_event_request [RedeliverWebhookEventRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(UnpublishPost200Response, Integer, Hash)>] UnpublishPost200Response data, response status code and response headers

data/lib/zernio-sdk/models/get_inbox_conversation_messages200_response_messages_inner.rb

@@ -15,6 +15,7 @@ require 'time'
 
 module Zernio
   class GetInboxConversationMessages200ResponseMessagesInner < ApiModelBase
+    # The platform's own message id: the `wamid` on WhatsApp, the `mid` on Instagram and Facebook Messenger. This is what `metadata.quotedMessageId` points at, the value to pass as `replyTo` on the platforms that support quote-replies, and the `{messageId}` segment of the attachment-resolve URL. Webhooks deliver the same value as `message.platformMessageId`; this response has no field by that name. 
     attr_accessor :id
 
     attr_accessor :conversation_id
@@ -79,7 +80,7 @@ module Zernio
     # Emoji reactions on this message (WhatsApp / Telegram). At most one per party in a 1:1 thread.
     attr_accessor :reactions
 
-    # Platform-specific extras. Free-form, but commonly includes: `quotedMessageId` (platformMessageId this message replies to), `waInteractive` (a compact descriptor of WhatsApp interactive content sent: buttons / list / cta_url / flow / location_request), and for inbound interactive taps `interactiveType` / `interactiveId`. It can also carry `source` (`whatsapp_business_app` / `coexistence_history` on a WhatsApp Coexistence number, `bulk-api` on a POST /v1/whatsapp/bulk send), which is where the message reached us from rather than who produced it: read `sentVia` for that. 
+    # Platform-specific extras. Free-form, but commonly includes: `quotedMessageId` (the `id` of the message this one replies to, delivered as `message.platformMessageId` on webhooks), `waInteractive` (a compact descriptor of WhatsApp interactive content sent: buttons / list / cta_url / flow / location_request), and for inbound interactive taps `interactiveType` / `interactiveId`. It can also carry `source` (`whatsapp_business_app` / `coexistence_history` on a WhatsApp Coexistence number, `bulk-api` on a POST /v1/whatsapp/bulk send), which is where the message reached us from rather than who produced it: read `sentVia` for that. 
     attr_accessor :metadata
 
     # Which Zernio surface produced this outgoing message: `human` (an operator in the Zernio inbox), `api` (a call to this API), `broadcast`, `sequence`, `workflow`, `comment_automation`, or `bulk-api` (POST /v1/whatsapp/bulk). Same vocabulary as the `source` filter on the inbox analytics endpoints.  Always present, and `null` whenever the lineage is unknown: every incoming message, any outgoing message sent from the platform's own app, and every message stored before this field shipped (2026-08). Existing messages are NOT backfilled, so treat `null` as \"unknown\", never as \"sent by a human\". 

data/lib/zernio-sdk/models/send_inbox_message_request.rb

@@ -57,7 +57,7 @@ module Zernio
     # Facebook message tag for messaging outside 24h window. Requires messagingType MESSAGE_TAG. Instagram only supports HUMAN_AGENT.
     attr_accessor :message_tag
 
-    # Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID (both available in message.platformMessageId from webhooks or the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without send-side reply support, including Instagram and Facebook Messenger (Meta's Send API rejects reply_to on Instagram and does not expose it on Messenger).
+    # Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID (delivered as message.platformMessageId on webhooks, and as `id` on each entry of the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without send-side reply support, including Instagram and Facebook Messenger (Meta's Send API rejects reply_to on Instagram and does not expose it on Messenger).
     attr_accessor :reply_to
 
     attr_accessor :location

data/lib/zernio-sdk/models/update_ad_request_creative.rb

@@ -14,7 +14,7 @@ require 'date'
 require 'time'
 
 module Zernio
-  # Replace or patch the ad's creative. Meta, TikTok, and LinkedIn.  - **Meta**: patch-style. Pass any subset — fields you omit are preserved from the   live creative, including media (`image_hash`/`video_id` are reused, no re-upload)   and `url_tags`. Sending the full set (`headline`, `body`, `callToAction`,   `linkUrl`, `imageUrl`) rebuilds the creative from scratch instead. Partial   patching reads the live `object_story_spec`, which Meta strips on SHARE /   page-post / dark / asset_feed creatives — those return 422 asking for the full   set. A `videoUrl`/`videoId` on an image creative is a type change and also   needs the full set. `existingCreativeId` repoints the ad at a creative from   GET /v1/ads/creatives and ignores every other field. Meta creatives are   immutable, so any change creates a new creative and repoints the ad; the old   creative is retained on the ad account for historical reporting. - **TikTok**: patch-style. Pass any subset; `headline` is ignored (TikTok creatives   have no headline slot). `body` becomes the in-feed `ad_text`; `linkUrl` becomes   `landing_page_url`; `videoUrl` triggers a fresh upload. `description`, `videoId`   and `existingCreativeId` are Meta-only and return 400. - **LinkedIn**: uploads new media (image via `imageUrl` or video via `videoUrl`),   creates a new inline media creative on the same campaign, and pauses the old   creative (best-effort). The old creative is retained for historical reporting.   `videoId` and `existingCreativeId` are Meta-only and return 400. 
+  # Replace or patch the ad's creative. Meta, TikTok, and LinkedIn.  - **Meta**: patch-style. Pass any subset — fields you omit are preserved from the   live creative, including media (`image_hash`/`video_id` are reused, no re-upload)   and `url_tags`. Sending the full set (`headline`, `body`, `callToAction`,   `linkUrl`, `imageUrl`) rebuilds the creative from scratch instead. Partial   patching reads the live `object_story_spec`, which Meta strips on SHARE /   page-post / dark / asset_feed creatives — those return 422 asking for the full   set. A `videoUrl`/`videoId` on an image creative is a type change and also   needs the full set. `existingCreativeId` repoints the ad at a creative from   GET /v1/ads/creatives and ignores every other field. Meta creatives are   immutable, so any change creates a new creative and repoints the ad; the old   creative is retained on the ad account for historical reporting. - **TikTok**: patch-style. Pass any subset; `headline` is ignored (TikTok creatives   have no headline slot). `body` becomes the in-feed `ad_text`; `linkUrl` becomes   `landing_page_url`; `videoUrl` triggers a fresh upload. `description`, `videoId`   and `existingCreativeId` are Meta-only and return 400. - **LinkedIn**: requires new media (image via `imageUrl` or video via `videoUrl`);   a text-only creative update returns 400. Uploads the media, creates a new inline   media creative on the same campaign, and pauses the old creative (best-effort).   The old creative is retained for historical reporting. `videoId` and   `existingCreativeId` are Meta-only and return 400. 
   class UpdateAdRequestCreative < ApiModelBase
     # Meta and LinkedIn (TikTok has no headline slot)
     attr_accessor :headline

data/lib/zernio-sdk/models/webhook_payload_message_metadata.rb

@@ -16,7 +16,7 @@ require 'time'
 module Zernio
   # Platform-specific message context (present when the message is a quick reply tap, postback button tap, inline keyboard callback, or a quote-reply to an earlier message)
   class WebhookPayloadMessageMetadata < ApiModelBase
-    # platformMessageId of the message this one is a quote-reply to. WhatsApp (`context.id`), Instagram and Facebook Messenger (`reply_to.mid`). Outgoing quote-replies carry the same field on `message.sent`; see WebhookPayloadMessageSent.metadata. 
+    # platformMessageId of the message this one is a quote-reply to. WhatsApp (`context.id`), Instagram and Facebook Messenger (`reply_to.mid`). On outgoing messages the same field appears on `message.sent`, but only on some surfaces: see WebhookPayloadMessageSent.metadata.quotedMessageId. 
     attr_accessor :quoted_message_id
 
     # Payload from a quick reply tap (Facebook/Instagram Messenger).

data/lib/zernio-sdk/models/webhook_payload_message_sent_metadata.rb

@@ -16,7 +16,7 @@ require 'time'
 module Zernio
   # Platform-specific context for the sent message. The key is present only when the send carried some context, and absent otherwise: it is never null and never an empty object.
   class WebhookPayloadMessageSentMetadata < ApiModelBase
-    # platformMessageId of the message this send is a quote-reply to. Set when the reply was sent through Zernio with `replyTo` on the inbox send API (WhatsApp and Telegram), and when the operator replied from the native WhatsApp Business, Instagram or Messenger app. WhatsApp API sends carry it on the event fired from the delivery status, so it arrives on the same `message.sent` as any other WhatsApp send. 
+    # `platformMessageId` of the message this send is a quote-reply to.  Present when the reply was sent through Zernio with `replyTo` on the inbox send API (WhatsApp and Telegram). A WhatsApp API send fires its `message.sent` off the delivery status, and the quote reference is forwarded from the stored send there, so it arrives on the same `message.sent` as any other WhatsApp send.  Not delivered on Instagram echoes. Zernio forwards `reply_to.mid` whenever Meta puts it on an echo, but on Instagram Meta does not send it, so a reply the operator quoted in the Instagram app arrives with no `quotedMessageId`. Facebook Messenger rides a separate subscription (`message_echoes`) and has not been measured, so treat it as unverified rather than supported.  Absent on WhatsApp Coexistence echoes. Meta omits the quote context from `smb_message_echoes`, so a reply the operator sent from the WhatsApp Business app arrives with no `quotedMessageId` even though WhatsApp shows it as a quote-reply. Do not read the absence of this field as \"not a reply\". 
     attr_accessor :quoted_message_id
 
     # Slack only. Parent thread ts of the sent message. Pass it back as `replyTo` on the inbox send API to keep replying inside the thread. 

data/lib/zernio-sdk/version.rb

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

data/openapi.yaml

@@ -3749,8 +3749,9 @@ components:
               description: |
                 platformMessageId of the message this one is a quote-reply to.
                 WhatsApp (`context.id`), Instagram and Facebook Messenger
-                (`reply_to.mid`). Outgoing quote-replies carry the same field on
-                `message.sent`; see WebhookPayloadMessageSent.metadata.
+                (`reply_to.mid`). On outgoing messages the same field appears on
+                `message.sent`, but only on some surfaces: see
+                WebhookPayloadMessageSent.metadata.quotedMessageId.
             quickReplyPayload:
               type: string
               description: Payload from a quick reply tap (Facebook/Instagram Messenger).
@@ -4142,13 +4143,27 @@ components:
             quotedMessageId:
               type: string
               description: |
-                platformMessageId of the message this send is a quote-reply to.
-                Set when the reply was sent through Zernio with `replyTo` on the
-                inbox send API (WhatsApp and Telegram), and when the operator
-                replied from the native WhatsApp Business, Instagram or Messenger
-                app. WhatsApp API sends carry it on the event fired from the
-                delivery status, so it arrives on the same `message.sent` as any
-                other WhatsApp send.
+                `platformMessageId` of the message this send is a quote-reply to.
+
+                Present when the reply was sent through Zernio with `replyTo` on
+                the inbox send API (WhatsApp and Telegram). A WhatsApp API send
+                fires its `message.sent` off the delivery status, and the quote
+                reference is forwarded from the stored send there, so it arrives
+                on the same `message.sent` as any other WhatsApp send.
+
+                Not delivered on Instagram echoes. Zernio forwards
+                `reply_to.mid` whenever Meta puts it on an echo, but on
+                Instagram Meta does not send it, so a reply the operator quoted
+                in the Instagram app arrives with no `quotedMessageId`.
+                Facebook Messenger rides a separate subscription
+                (`message_echoes`) and has not been measured, so treat it as
+                unverified rather than supported.
+
+                Absent on WhatsApp Coexistence echoes. Meta omits the quote
+                context from `smb_message_echoes`, so a reply the operator sent
+                from the WhatsApp Business app arrives with no `quotedMessageId`
+                even though WhatsApp shows it as a quote-reply. Do not read the
+                absence of this field as "not a reply".
             threadTs:
               type: string
               description: |
@@ -9523,8 +9538,11 @@ webhooks:
       description: |
         Fired when a message is sent via the API, or from the WhatsApp Business app on
         Coexistence numbers. Sends that carry platform-specific context deliver it under
-        `metadata`, so a quote-reply arrives with `metadata.quotedMessageId` and mirroring
-        CRMs can thread it without a lookup.
+        `metadata`, so a quote-reply sent through the API arrives with
+        `metadata.quotedMessageId` and mirroring CRMs can thread it without a lookup.
+        Which surfaces actually carry that reference is documented on
+        `WebhookPayloadMessageSent.metadata.quotedMessageId`; a quote-reply sent from
+        the WhatsApp Business or Instagram app is not one of them.
       tags: [Webhook Events]
       requestBody:
         required: true
@@ -25679,7 +25697,7 @@ paths:
         emitted, not the current state of the resource.
 
         Only deliveries inside the 30-day log retention window can be replayed; past that
-        the payload is gone and the request fails with a 500. Replays run the same
+        the payload is gone and the request fails with a 422. Replays run the same
         resource-group checks as live delivery, against both the key's groups and the
         subscription's `disabledResourceGroups`.
       security:
@@ -25718,10 +25736,11 @@ paths:
               example:
                 success: true
                 message: "Webhook re-delivered"
-        '400': { description: 'webhookId or eventId missing or empty' }
+        '400': { description: 'webhookId or eventId missing or empty, or the subscription has no URL configured' }
         '401': { $ref: '#/components/responses/Unauthorized' }
         '403': { $ref: '#/components/responses/ResourceGroupForbidden' }
-        '500': { description: 'Webhook no longer exists, has no URL configured, or the original payload is outside the 30-day retention window' }
+        '404': { description: 'Webhook subscription not found' }
+        '422': { description: 'Original payload not replayable: no delivery matches this event inside the 30-day retention window, or the stored payload is truncated or not valid JSON' }
         '502':
           description: |
             Re-delivery was attempted but your endpoint errored again. The attempt is still
@@ -26873,7 +26892,16 @@ paths:
                     items:
                       type: object
                       properties:
-                        id: { type: string }
+                        id:
+                          type: string
+                          description: |
+                            The platform's own message id: the `wamid` on WhatsApp, the
+                            `mid` on Instagram and Facebook Messenger. This is what
+                            `metadata.quotedMessageId` points at, the value to pass as
+                            `replyTo` on the platforms that support quote-replies, and the
+                            `{messageId}` segment of the attachment-resolve URL. Webhooks
+                            deliver the same value as `message.platformMessageId`; this
+                            response has no field by that name.
                         conversationId: { type: string }
                         accountId: { type: string }
                         platform: { type: string }
@@ -26968,7 +26996,8 @@ paths:
                           type: object
                           description: |
                             Platform-specific extras. Free-form, but commonly includes:
-                            `quotedMessageId` (platformMessageId this message replies to),
+                            `quotedMessageId` (the `id` of the message this one replies to,
+                            delivered as `message.platformMessageId` on webhooks),
                             `waInteractive` (a compact descriptor of WhatsApp interactive
                             content sent: buttons / list / cta_url / flow / location_request),
                             and for inbound interactive taps `interactiveType` / `interactiveId`.
@@ -27505,7 +27534,7 @@ paths:
                   description: Facebook message tag for messaging outside 24h window. Requires messagingType MESSAGE_TAG. Instagram only supports HUMAN_AGENT.
                 replyTo:
                   type: string
-                  description: 'Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID (both available in message.platformMessageId from webhooks or the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without send-side reply support, including Instagram and Facebook Messenger (Meta''s Send API rejects reply_to on Instagram and does not expose it on Messenger).'
+                  description: 'Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID (delivered as message.platformMessageId on webhooks, and as `id` on each entry of the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without send-side reply support, including Instagram and Facebook Messenger (Meta''s Send API rejects reply_to on Instagram and does not expose it on Messenger).'
                 location:
                   type: object
                   description: WhatsApp-only. Send a location pin.
@@ -27595,7 +27624,7 @@ paths:
                   description: Message tag (requires messagingType MESSAGE_TAG)
                 replyTo:
                   type: string
-                  description: 'Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID (both available in message.platformMessageId from webhooks or the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without send-side reply support, including Instagram and Facebook Messenger (Meta''s Send API rejects reply_to on Instagram and does not expose it on Messenger).'
+                  description: 'Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID (delivered as message.platformMessageId on webhooks, and as `id` on each entry of the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without send-side reply support, including Instagram and Facebook Messenger (Meta''s Send API rejects reply_to on Instagram and does not expose it on Messenger).'
                 voiceNote:
                   type: string
                   enum: ['true']
@@ -41634,10 +41663,11 @@ paths:
                       have no headline slot). `body` becomes the in-feed `ad_text`; `linkUrl` becomes
                       `landing_page_url`; `videoUrl` triggers a fresh upload. `description`, `videoId`
                       and `existingCreativeId` are Meta-only and return 400.
-                    - **LinkedIn**: uploads new media (image via `imageUrl` or video via `videoUrl`),
-                      creates a new inline media creative on the same campaign, and pauses the old
-                      creative (best-effort). The old creative is retained for historical reporting.
-                      `videoId` and `existingCreativeId` are Meta-only and return 400.
+                    - **LinkedIn**: requires new media (image via `imageUrl` or video via `videoUrl`);
+                      a text-only creative update returns 400. Uploads the media, creates a new inline
+                      media creative on the same campaign, and pauses the old creative (best-effort).
+                      The old creative is retained for historical reporting. `videoId` and
+                      `existingCreativeId` are Meta-only and return 400.
                   properties:
                     headline: { type: string, description: "Meta and LinkedIn (TikTok has no headline slot)" }
                     body: { type: string }
@@ -41660,7 +41690,7 @@ paths:
                   ad: { $ref: '#/components/schemas/Ad' }
                   message: { type: string }
         '400':
-          description: Invalid status transition or budget below minimum
+          description: 'Invalid status transition, budget below minimum, or a LinkedIn creative update without imageUrl or videoUrl'
         '401': { $ref: '#/components/responses/Unauthorized' }
         '404': { $ref: '#/components/responses/NotFound' }
         '501': { description: "targeting or creative not supported on the platform (supported on Meta, TikTok, and LinkedIn)" }

data/spec/api/webhooks_api_spec.rb

@@ -86,7 +86,7 @@ describe 'WebhooksApi' do
 
   # unit tests for redeliver_webhook_event
   # Redeliver a webhook event
-  # Replay a past delivery: the original payload is re-sent, byte for byte, to the subscription's current URL. The original event ID is preserved so your endpoint can dedupe, and the replay is recorded as a fresh attempt, so it shows up in `GET /v1/webhooks/logs` next to the delivery it replays.  Both `webhookId` and `eventId` come from a row of `GET /v1/webhooks/logs`. Because the stored payload is replayed as-is, a redelivery reflects the event as it was emitted, not the current state of the resource.  Only deliveries inside the 30-day log retention window can be replayed; past that the payload is gone and the request fails with a 500. Replays run the same resource-group checks as live delivery, against both the key's groups and the subscription's `disabledResourceGroups`. 
+  # Replay a past delivery: the original payload is re-sent, byte for byte, to the subscription's current URL. The original event ID is preserved so your endpoint can dedupe, and the replay is recorded as a fresh attempt, so it shows up in `GET /v1/webhooks/logs` next to the delivery it replays.  Both `webhookId` and `eventId` come from a row of `GET /v1/webhooks/logs`. Because the stored payload is replayed as-is, a redelivery reflects the event as it was emitted, not the current state of the resource.  Only deliveries inside the 30-day log retention window can be replayed; past that the payload is gone and the request fails with a 422. Replays run the same resource-group checks as live delivery, against both the key's groups and the subscription's `disabledResourceGroups`. 
   # @param redeliver_webhook_event_request 
   # @param [Hash] opts the optional parameters
   # @return [UnpublishPost200Response]

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: late-sdk
 version: !ruby/object:Gem::Version
-  version: 0.0.814
+  version: 0.0.816
 platform: ruby
 authors:
 - OpenAPI-Generator
@@ -5557,7 +5557,7 @@ files:
 - spec/models/you_tube_video_retention_response_retention_curve_inner_spec.rb
 - spec/models/you_tube_video_retention_response_spec.rb
 - spec/spec_helper.rb
-- zernio-sdk-0.0.814.gem
+- zernio-sdk-0.0.816.gem
 - zernio-sdk.gemspec
 homepage: https://openapi-generator.tech
 licenses: