@zernio/node 0.2.645 → 0.2.647

package/dist/index.d.mts

@@ -8449,8 +8449,8 @@ type WebhookPayloadMessage = {
         /**
          * platformMessageId of the message this one is a quote-reply to.
          * WhatsApp (`context.id`), Instagram and Facebook Messenger
-         * (`reply_to.mid`). On `message.sent` echoes (operator replied
-         * from the native app) this is the only metadata field populated.
+         * (`reply_to.mid`). Outgoing quote-replies carry the same field on
+         * `message.sent`; see WebhookPayloadMessageSent.metadata.
          *
          */
         quotedMessageId?: string;
@@ -8880,7 +8880,10 @@ type WebhookPayloadMessageSent = {
          * Internal conversation ID
          */
         conversationId: string;
-        platform: 'instagram' | 'facebook' | 'telegram' | 'whatsapp';
+        /**
+         * Every platform whose outgoing messages Zernio observes. sms is absent on purpose: its carrier receipts update delivery status and never raise message.sent.
+         */
+        platform: 'instagram' | 'facebook' | 'telegram' | 'whatsapp' | 'twitter' | 'reddit' | 'bluesky' | 'slack';
         /**
          * Platform's message ID
          */
@@ -8934,13 +8937,38 @@ type WebhookPayloadMessageSent = {
     };
     conversation: InboxWebhookConversation;
     account: InboxWebhookAccount;
+    /**
+     * 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.
+     */
+    metadata?: {
+        /**
+         * 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.
+         *
+         */
+        quotedMessageId?: 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.
+         *
+         */
+        threadTs?: string;
+    };
     /**
      * UTC time at which Zernio generated this event (set once when the event payload is built, before delivery is queued). Retries and redeliveries keep the original value, so it reflects the event, not the delivery attempt.
      */
     timestamp: string;
 };
 type event17 = 'message.sent';
-type platform11 = 'instagram' | 'facebook' | 'telegram' | 'whatsapp';
+/**
+ * Every platform whose outgoing messages Zernio observes. sms is absent on purpose: its carrier receipts update delivery status and never raise message.sent.
+ */
+type platform11 = 'instagram' | 'facebook' | 'telegram' | 'whatsapp' | 'twitter' | 'reddit' | 'bluesky' | 'slack';
 /**
  * WhatsApp send origin. whatsapp_business_app when sent from the WhatsApp Business phone app on a Coexistence number; cloud_api when sent through Zernio (dashboard, API, or broadcasts). Absent on non-WhatsApp platforms. This is not the inbox metadata.source lineage field.
  */
@@ -12387,6 +12415,10 @@ type ListUsersResponse = ({
         isRoot?: boolean;
         profileAccess?: Array<(string)>;
         createdAt?: string;
+        /**
+         * Last sign-in, stamped at most once an hour, so it is accurate to within an hour rather than to the exact session. Omitted for members with no recorded sign-in since the field shipped, which does not mean they never signed in.
+         */
+        lastLoginAt?: string;
     }>;
 });
 type ListUsersError = ({
@@ -19718,13 +19750,21 @@ type AddMessageReactionData = {
          */
         conversationId: string;
         /**
-         * The platform message ID to react to
+         * The platform message ID (as returned by GET /messages) or the Zernio message ID (as returned by the reaction webhook)
          */
         messageId: string;
     };
 };
 type AddMessageReactionResponse = ({
     success?: boolean;
+    /**
+     * The Zernio message ID the reaction was resolved against
+     */
+    messageId?: string;
+    /**
+     * The platform message ID the reaction was sent for
+     */
+    platformMessageId?: string;
 });
 type AddMessageReactionError = (unknown | {
     error?: string;
@@ -19736,7 +19776,7 @@ type RemoveMessageReactionData = {
          */
         conversationId: string;
         /**
-         * The platform message ID
+         * The platform message ID (as returned by GET /messages) or the Zernio message ID (as returned by the reaction webhook)
          */
         messageId: string;
     };
@@ -19749,6 +19789,14 @@ type RemoveMessageReactionData = {
 };
 type RemoveMessageReactionResponse = ({
     success?: boolean;
+    /**
+     * The Zernio message ID the removal was resolved against
+     */
+    messageId?: string;
+    /**
+     * The platform message ID the removal was sent for
+     */
+    platformMessageId?: string;
 });
 type RemoveMessageReactionError = (unknown | {
     error?: string;
@@ -32548,10 +32596,18 @@ type CreateLeadFormData = {
             thankYouButtonText?: string;
             thankYouButtonType?: string;
             thankYouWebsiteUrl?: string;
+            /**
+             * Adds a 'Continue in Messenger' option to the thank-you page (Meta thank_you_page.enable_messenger), so the lead can carry on chatting with the Page. Set thankYouButtonType to MESSAGE_BUSINESS or P2B_MESSENGER to make the chat the primary button.
+             */
+            thankYouEnableMessenger?: boolean;
             /**
              * Set true for a higher-intent form (adds a review step before submit).
              */
             isOptimizedForQuality?: boolean;
+            /**
+             * Requires the lead to verify their phone number over SMS before the form submits (Meta is_phone_sms_verify_enabled). Only meaningful on a form with a PHONE question. Meta can restrict this parameter to apps holding a capability: when it does, the create fails with a 422 naming platformSpecificData.isPhoneSmsVerifyEnabled, and the toggle then has to be set in Meta's form builder.
+             */
+            isPhoneSmsVerifyEnabled?: boolean;
             blockDisplayForNonTargetedViewer?: boolean;
             questionPageCustomHeadline?: string;
             contextCard?: {

package/dist/index.d.ts

@@ -8449,8 +8449,8 @@ type WebhookPayloadMessage = {
         /**
          * platformMessageId of the message this one is a quote-reply to.
          * WhatsApp (`context.id`), Instagram and Facebook Messenger
-         * (`reply_to.mid`). On `message.sent` echoes (operator replied
-         * from the native app) this is the only metadata field populated.
+         * (`reply_to.mid`). Outgoing quote-replies carry the same field on
+         * `message.sent`; see WebhookPayloadMessageSent.metadata.
          *
          */
         quotedMessageId?: string;
@@ -8880,7 +8880,10 @@ type WebhookPayloadMessageSent = {
          * Internal conversation ID
          */
         conversationId: string;
-        platform: 'instagram' | 'facebook' | 'telegram' | 'whatsapp';
+        /**
+         * Every platform whose outgoing messages Zernio observes. sms is absent on purpose: its carrier receipts update delivery status and never raise message.sent.
+         */
+        platform: 'instagram' | 'facebook' | 'telegram' | 'whatsapp' | 'twitter' | 'reddit' | 'bluesky' | 'slack';
         /**
          * Platform's message ID
          */
@@ -8934,13 +8937,38 @@ type WebhookPayloadMessageSent = {
     };
     conversation: InboxWebhookConversation;
     account: InboxWebhookAccount;
+    /**
+     * 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.
+     */
+    metadata?: {
+        /**
+         * 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.
+         *
+         */
+        quotedMessageId?: 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.
+         *
+         */
+        threadTs?: string;
+    };
     /**
      * UTC time at which Zernio generated this event (set once when the event payload is built, before delivery is queued). Retries and redeliveries keep the original value, so it reflects the event, not the delivery attempt.
      */
     timestamp: string;
 };
 type event17 = 'message.sent';
-type platform11 = 'instagram' | 'facebook' | 'telegram' | 'whatsapp';
+/**
+ * Every platform whose outgoing messages Zernio observes. sms is absent on purpose: its carrier receipts update delivery status and never raise message.sent.
+ */
+type platform11 = 'instagram' | 'facebook' | 'telegram' | 'whatsapp' | 'twitter' | 'reddit' | 'bluesky' | 'slack';
 /**
  * WhatsApp send origin. whatsapp_business_app when sent from the WhatsApp Business phone app on a Coexistence number; cloud_api when sent through Zernio (dashboard, API, or broadcasts). Absent on non-WhatsApp platforms. This is not the inbox metadata.source lineage field.
  */
@@ -12387,6 +12415,10 @@ type ListUsersResponse = ({
         isRoot?: boolean;
         profileAccess?: Array<(string)>;
         createdAt?: string;
+        /**
+         * Last sign-in, stamped at most once an hour, so it is accurate to within an hour rather than to the exact session. Omitted for members with no recorded sign-in since the field shipped, which does not mean they never signed in.
+         */
+        lastLoginAt?: string;
     }>;
 });
 type ListUsersError = ({
@@ -19718,13 +19750,21 @@ type AddMessageReactionData = {
          */
         conversationId: string;
         /**
-         * The platform message ID to react to
+         * The platform message ID (as returned by GET /messages) or the Zernio message ID (as returned by the reaction webhook)
          */
         messageId: string;
     };
 };
 type AddMessageReactionResponse = ({
     success?: boolean;
+    /**
+     * The Zernio message ID the reaction was resolved against
+     */
+    messageId?: string;
+    /**
+     * The platform message ID the reaction was sent for
+     */
+    platformMessageId?: string;
 });
 type AddMessageReactionError = (unknown | {
     error?: string;
@@ -19736,7 +19776,7 @@ type RemoveMessageReactionData = {
          */
         conversationId: string;
         /**
-         * The platform message ID
+         * The platform message ID (as returned by GET /messages) or the Zernio message ID (as returned by the reaction webhook)
          */
         messageId: string;
     };
@@ -19749,6 +19789,14 @@ type RemoveMessageReactionData = {
 };
 type RemoveMessageReactionResponse = ({
     success?: boolean;
+    /**
+     * The Zernio message ID the removal was resolved against
+     */
+    messageId?: string;
+    /**
+     * The platform message ID the removal was sent for
+     */
+    platformMessageId?: string;
 });
 type RemoveMessageReactionError = (unknown | {
     error?: string;
@@ -32548,10 +32596,18 @@ type CreateLeadFormData = {
             thankYouButtonText?: string;
             thankYouButtonType?: string;
             thankYouWebsiteUrl?: string;
+            /**
+             * Adds a 'Continue in Messenger' option to the thank-you page (Meta thank_you_page.enable_messenger), so the lead can carry on chatting with the Page. Set thankYouButtonType to MESSAGE_BUSINESS or P2B_MESSENGER to make the chat the primary button.
+             */
+            thankYouEnableMessenger?: boolean;
             /**
              * Set true for a higher-intent form (adds a review step before submit).
              */
             isOptimizedForQuality?: boolean;
+            /**
+             * Requires the lead to verify their phone number over SMS before the form submits (Meta is_phone_sms_verify_enabled). Only meaningful on a form with a PHONE question. Meta can restrict this parameter to apps holding a capability: when it does, the create fails with a 422 naming platformSpecificData.isPhoneSmsVerifyEnabled, and the toggle then has to be set in Meta's form builder.
+             */
+            isPhoneSmsVerifyEnabled?: boolean;
             blockDisplayForNonTargetedViewer?: boolean;
             questionPageCustomHeadline?: string;
             contextCard?: {

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.645",
+  version: "0.2.647",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/dist/index.mjs

@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.645",
+  version: "0.2.647",
   description: "The official Node.js library for the Zernio API",
   main: "dist/index.js",
   module: "dist/index.mjs",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@zernio/node",
-  "version": "0.2.645",
+  "version": "0.2.647",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/types.gen.ts

@@ -7398,8 +7398,8 @@ export type WebhookPayloadMessage = {
         /**
          * platformMessageId of the message this one is a quote-reply to.
          * WhatsApp (`context.id`), Instagram and Facebook Messenger
-         * (`reply_to.mid`). On `message.sent` echoes (operator replied
-         * from the native app) this is the only metadata field populated.
+         * (`reply_to.mid`). Outgoing quote-replies carry the same field on
+         * `message.sent`; see WebhookPayloadMessageSent.metadata.
          *
          */
         quotedMessageId?: string;
@@ -7839,7 +7839,10 @@ export type WebhookPayloadMessageSent = {
          * Internal conversation ID
          */
         conversationId: string;
-        platform: 'instagram' | 'facebook' | 'telegram' | 'whatsapp';
+        /**
+         * Every platform whose outgoing messages Zernio observes. sms is absent on purpose: its carrier receipts update delivery status and never raise message.sent.
+         */
+        platform: 'instagram' | 'facebook' | 'telegram' | 'whatsapp' | 'twitter' | 'reddit' | 'bluesky' | 'slack';
         /**
          * Platform's message ID
          */
@@ -7893,6 +7896,28 @@ export type WebhookPayloadMessageSent = {
     };
     conversation: InboxWebhookConversation;
     account: InboxWebhookAccount;
+    /**
+     * 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.
+     */
+    metadata?: {
+        /**
+         * 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.
+         *
+         */
+        quotedMessageId?: 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.
+         *
+         */
+        threadTs?: string;
+    };
     /**
      * UTC time at which Zernio generated this event (set once when the event payload is built, before delivery is queued). Retries and redeliveries keep the original value, so it reflects the event, not the delivery attempt.
      */
@@ -7901,7 +7926,10 @@ export type WebhookPayloadMessageSent = {
 
 export type event17 = 'message.sent';
 
-export type platform11 = 'instagram' | 'facebook' | 'telegram' | 'whatsapp';
+/**
+ * Every platform whose outgoing messages Zernio observes. sms is absent on purpose: its carrier receipts update delivery status and never raise message.sent.
+ */
+export type platform11 = 'instagram' | 'facebook' | 'telegram' | 'whatsapp' | 'twitter' | 'reddit' | 'bluesky' | 'slack';
 
 /**
  * WhatsApp send origin. whatsapp_business_app when sent from the WhatsApp Business phone app on a Coexistence number; cloud_api when sent through Zernio (dashboard, API, or broadcasts). Absent on non-WhatsApp platforms. This is not the inbox metadata.source lineage field.
@@ -11578,6 +11606,10 @@ export type ListUsersResponse = ({
         isRoot?: boolean;
         profileAccess?: Array<(string)>;
         createdAt?: string;
+        /**
+         * Last sign-in, stamped at most once an hour, so it is accurate to within an hour rather than to the exact session. Omitted for members with no recorded sign-in since the field shipped, which does not mean they never signed in.
+         */
+        lastLoginAt?: string;
     }>;
 });
 
@@ -19387,7 +19419,7 @@ export type AddMessageReactionData = {
          */
         conversationId: string;
         /**
-         * The platform message ID to react to
+         * The platform message ID (as returned by GET /messages) or the Zernio message ID (as returned by the reaction webhook)
          */
         messageId: string;
     };
@@ -19395,6 +19427,14 @@ export type AddMessageReactionData = {
 
 export type AddMessageReactionResponse = ({
     success?: boolean;
+    /**
+     * The Zernio message ID the reaction was resolved against
+     */
+    messageId?: string;
+    /**
+     * The platform message ID the reaction was sent for
+     */
+    platformMessageId?: string;
 });
 
 export type AddMessageReactionError = (unknown | {
@@ -19408,7 +19448,7 @@ export type RemoveMessageReactionData = {
          */
         conversationId: string;
         /**
-         * The platform message ID
+         * The platform message ID (as returned by GET /messages) or the Zernio message ID (as returned by the reaction webhook)
          */
         messageId: string;
     };
@@ -19422,6 +19462,14 @@ export type RemoveMessageReactionData = {
 
 export type RemoveMessageReactionResponse = ({
     success?: boolean;
+    /**
+     * The Zernio message ID the removal was resolved against
+     */
+    messageId?: string;
+    /**
+     * The platform message ID the removal was sent for
+     */
+    platformMessageId?: string;
 });
 
 export type RemoveMessageReactionError = (unknown | {
@@ -33131,10 +33179,18 @@ export type CreateLeadFormData = {
     thankYouButtonText?: string;
     thankYouButtonType?: string;
     thankYouWebsiteUrl?: string;
+    /**
+     * Adds a 'Continue in Messenger' option to the thank-you page (Meta thank_you_page.enable_messenger), so the lead can carry on chatting with the Page. Set thankYouButtonType to MESSAGE_BUSINESS or P2B_MESSENGER to make the chat the primary button.
+     */
+    thankYouEnableMessenger?: boolean;
     /**
      * Set true for a higher-intent form (adds a review step before submit).
      */
     isOptimizedForQuality?: boolean;
+    /**
+     * Requires the lead to verify their phone number over SMS before the form submits (Meta is_phone_sms_verify_enabled). Only meaningful on a form with a PHONE question. Meta can restrict this parameter to apps holding a capability: when it does, the create fails with a 422 naming platformSpecificData.isPhoneSmsVerifyEnabled, and the toggle then has to be set in Meta's form builder.
+     */
+    isPhoneSmsVerifyEnabled?: boolean;
     blockDisplayForNonTargetedViewer?: boolean;
     questionPageCustomHeadline?: string;
     contextCard?: {