@zernio/node 0.2.1036 → 0.2.1038

package/dist/index.d.mts

@@ -4825,6 +4825,14 @@ type CommentAutomationAudience = {
      *
      */
     whenUnknown?: 'send' | 'skip' | 'verify';
+    /**
+     * Send `followGate.message` with its button to EVERY commenter and deliver the real
+     * DM when they tap it, with no follow check at any point. Cannot be combined with a
+     * `followerStatus` other than `any` or with `minFollowerCount` (400); `whenUnknown`
+     * is ignored. Instagram only. A PATCH that sends `audience` without this field clears it.
+     *
+     */
+    tapToUnlock?: boolean;
 };
 type followerStatus = 'any' | 'follower' | 'non_follower';
 /**
@@ -4842,11 +4850,11 @@ type whenUnknown = 'send' | 'skip' | 'verify';
  */
 type CommentAutomationFollowGate = {
     /**
-     * Confirmation DM sent when whenUnknown=verify.
+     * Confirmation DM sent when whenUnknown=verify or tapToUnlock=true. The default copy asks for a follow under whenUnknown=verify and only for the tap under tapToUnlock.
      */
     message?: string;
     /**
-     * Confirm button label. Defaults to "I'm following".
+     * Confirm button label. Defaults to "I'm following" (whenUnknown=verify) or "Unlock" (tapToUnlock).
      */
     buttonLabel?: string;
     /**
@@ -19212,7 +19220,7 @@ type GetAllAccountsHealthResponse = ({
         needsReconnect?: boolean;
         issues?: Array<(string)>;
         /**
-         * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction.
+         * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction. After subcode 1893063 (Meta refusing the Page's messages), comment automation DMs are held and one is retried at `pausedUntil`: 30 minutes, doubling per refused retry up to 4 hours; held DMs stay pending and are sent once Meta accepts again, within the 7-day private-reply window.
          */
         messagingRestriction?: {
             /**
@@ -19226,6 +19234,10 @@ type GetAllAccountsHealthResponse = ({
             message?: (string) | null;
             firstSeenAt?: string;
             lastSeenAt?: string;
+            /**
+             * When held automation DMs are next retried. Null when nothing is held.
+             */
+            pausedUntil?: (string) | null;
         } | null;
     }>;
 });
@@ -19364,7 +19376,7 @@ type GetAccountHealthResponse = ({
      */
     recommendations?: Array<(string)>;
     /**
-     * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction.
+     * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction. After subcode 1893063 (Meta refusing the Page's messages), comment automation DMs are held and one is retried at `pausedUntil`: 30 minutes, doubling per refused retry up to 4 hours; held DMs stay pending and are sent once Meta accepts again, within the 7-day private-reply window.
      */
     messagingRestriction?: {
         /**
@@ -19378,6 +19390,10 @@ type GetAccountHealthResponse = ({
         message?: (string) | null;
         firstSeenAt?: string;
         lastSeenAt?: string;
+        /**
+         * When held automation DMs are next retried. Null when nothing is held.
+         */
+        pausedUntil?: (string) | null;
     } | null;
     /**
      * WhatsApp accounts only. Live probe of the Meta link behind the channel, performed at request time (the same read as GET /v1/whatsapp/number-info).

package/dist/index.d.ts

@@ -4825,6 +4825,14 @@ type CommentAutomationAudience = {
      *
      */
     whenUnknown?: 'send' | 'skip' | 'verify';
+    /**
+     * Send `followGate.message` with its button to EVERY commenter and deliver the real
+     * DM when they tap it, with no follow check at any point. Cannot be combined with a
+     * `followerStatus` other than `any` or with `minFollowerCount` (400); `whenUnknown`
+     * is ignored. Instagram only. A PATCH that sends `audience` without this field clears it.
+     *
+     */
+    tapToUnlock?: boolean;
 };
 type followerStatus = 'any' | 'follower' | 'non_follower';
 /**
@@ -4842,11 +4850,11 @@ type whenUnknown = 'send' | 'skip' | 'verify';
  */
 type CommentAutomationFollowGate = {
     /**
-     * Confirmation DM sent when whenUnknown=verify.
+     * Confirmation DM sent when whenUnknown=verify or tapToUnlock=true. The default copy asks for a follow under whenUnknown=verify and only for the tap under tapToUnlock.
      */
     message?: string;
     /**
-     * Confirm button label. Defaults to "I'm following".
+     * Confirm button label. Defaults to "I'm following" (whenUnknown=verify) or "Unlock" (tapToUnlock).
      */
     buttonLabel?: string;
     /**
@@ -19212,7 +19220,7 @@ type GetAllAccountsHealthResponse = ({
         needsReconnect?: boolean;
         issues?: Array<(string)>;
         /**
-         * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction.
+         * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction. After subcode 1893063 (Meta refusing the Page's messages), comment automation DMs are held and one is retried at `pausedUntil`: 30 minutes, doubling per refused retry up to 4 hours; held DMs stay pending and are sent once Meta accepts again, within the 7-day private-reply window.
          */
         messagingRestriction?: {
             /**
@@ -19226,6 +19234,10 @@ type GetAllAccountsHealthResponse = ({
             message?: (string) | null;
             firstSeenAt?: string;
             lastSeenAt?: string;
+            /**
+             * When held automation DMs are next retried. Null when nothing is held.
+             */
+            pausedUntil?: (string) | null;
         } | null;
     }>;
 });
@@ -19364,7 +19376,7 @@ type GetAccountHealthResponse = ({
      */
     recommendations?: Array<(string)>;
     /**
-     * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction.
+     * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction. After subcode 1893063 (Meta refusing the Page's messages), comment automation DMs are held and one is retried at `pausedUntil`: 30 minutes, doubling per refused retry up to 4 hours; held DMs stay pending and are sent once Meta accepts again, within the 7-day private-reply window.
      */
     messagingRestriction?: {
         /**
@@ -19378,6 +19390,10 @@ type GetAccountHealthResponse = ({
         message?: (string) | null;
         firstSeenAt?: string;
         lastSeenAt?: string;
+        /**
+         * When held automation DMs are next retried. Null when nothing is held.
+         */
+        pausedUntil?: (string) | null;
     } | null;
     /**
      * WhatsApp accounts only. Live probe of the Meta link behind the channel, performed at request time (the same read as GET /v1/whatsapp/number-info).

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.1036",
+  version: "0.2.1038",
   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.1036",
+  version: "0.2.1038",
   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.1036",
+  "version": "0.2.1038",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/sdk.gen.ts

@@ -9041,7 +9041,9 @@ export const listCommentAutomations = <ThrowOnError extends boolean = false>(opt
  * follow relationship for people who have messaged the account, so `audience.whenUnknown`
  * decides what happens for everyone else - including `verify`, which sends a one-tap
  * confirmation DM (`followGate`) and then delivers the real DM automatically. People we
- * already know follow you skip the tap entirely.
+ * already know follow you skip the tap entirely. Set `audience.tapToUnlock: true` instead
+ * to send that button DM to every commenter and deliver the real DM on the tap with no
+ * follow check.
  *
  * Set `alsoMatchInDms: true` on a `comment` automation to also answer people who send
  * a keyword as a direct message instead of commenting it. One automation then covers

package/src/generated/types.gen.ts

@@ -2986,6 +2986,14 @@ export type CommentAutomationAudience = {
      *
      */
     whenUnknown?: 'send' | 'skip' | 'verify';
+    /**
+     * Send `followGate.message` with its button to EVERY commenter and deliver the real
+     * DM when they tap it, with no follow check at any point. Cannot be combined with a
+     * `followerStatus` other than `any` or with `minFollowerCount` (400); `whenUnknown`
+     * is ignored. Instagram only. A PATCH that sends `audience` without this field clears it.
+     *
+     */
+    tapToUnlock?: boolean;
 };
 
 export type followerStatus = 'any' | 'follower' | 'non_follower';
@@ -3006,11 +3014,11 @@ export type whenUnknown = 'send' | 'skip' | 'verify';
  */
 export type CommentAutomationFollowGate = {
     /**
-     * Confirmation DM sent when whenUnknown=verify.
+     * Confirmation DM sent when whenUnknown=verify or tapToUnlock=true. The default copy asks for a follow under whenUnknown=verify and only for the tap under tapToUnlock.
      */
     message?: string;
     /**
-     * Confirm button label. Defaults to "I'm following".
+     * Confirm button label. Defaults to "I'm following" (whenUnknown=verify) or "Unlock" (tapToUnlock).
      */
     buttonLabel?: string;
     /**
@@ -18090,7 +18098,7 @@ export type GetAllAccountsHealthResponse = ({
         needsReconnect?: boolean;
         issues?: Array<(string)>;
         /**
-         * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction.
+         * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction. After subcode 1893063 (Meta refusing the Page's messages), comment automation DMs are held and one is retried at `pausedUntil`: 30 minutes, doubling per refused retry up to 4 hours; held DMs stay pending and are sent once Meta accepts again, within the 7-day private-reply window.
          */
         messagingRestriction?: {
             /**
@@ -18104,6 +18112,10 @@ export type GetAllAccountsHealthResponse = ({
             message?: (string) | null;
             firstSeenAt?: string;
             lastSeenAt?: string;
+            /**
+             * When held automation DMs are next retried. Null when nothing is held.
+             */
+            pausedUntil?: (string) | null;
         } | null;
     }>;
 });
@@ -18254,7 +18266,7 @@ export type GetAccountHealthResponse = ({
      */
     recommendations?: Array<(string)>;
     /**
-     * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction.
+     * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction. After subcode 1893063 (Meta refusing the Page's messages), comment automation DMs are held and one is retried at `pausedUntil`: 30 minutes, doubling per refused retry up to 4 hours; held DMs stay pending and are sent once Meta accepts again, within the 7-day private-reply window.
      */
     messagingRestriction?: {
         /**
@@ -18268,6 +18280,10 @@ export type GetAccountHealthResponse = ({
         message?: (string) | null;
         firstSeenAt?: string;
         lastSeenAt?: string;
+        /**
+         * When held automation DMs are next retried. Null when nothing is held.
+         */
+        pausedUntil?: (string) | null;
     } | null;
     /**
      * WhatsApp accounts only. Live probe of the Meta link behind the channel, performed at request time (the same read as GET /v1/whatsapp/number-info).