@getlatedev/node 0.2.1392 → 0.2.1393

package/dist/index.d.mts

@@ -27811,9 +27811,9 @@ type GetAccountHealthResponse = ({
             message?: string;
         } | null;
         /**
-         * From the phone number's Meta health_status.
+         * From the phone number's Meta health_status, overridden to `false` when subscribing the number's WhatsApp Business Account to Zernio's webhooks failed at connect.
          *
-         * - `false`: Meta says Zernio is not subscribed to the message webhook for this number, so inbound messages are not delivered, though the number is CONNECTED and can still send.
+         * - `false`: Meta says Zernio is not subscribed to the message webhook for this number, or the subscribe failed when the number was connected, so inbound messages are not delivered, though the number is CONNECTED and can still send.
          * - `false`, fix: re-subscribe (reconnect the number). If it stays `false`, the number is routed to a different WhatsApp Business Account (typically after linking it to a Facebook Page).
          * - `true`: Meta reports no such problem.
          * - `null`: Meta did not report it (read failed or no health_status); not evidence either way.

package/dist/index.d.ts

@@ -27811,9 +27811,9 @@ type GetAccountHealthResponse = ({
             message?: string;
         } | null;
         /**
-         * From the phone number's Meta health_status.
+         * From the phone number's Meta health_status, overridden to `false` when subscribing the number's WhatsApp Business Account to Zernio's webhooks failed at connect.
          *
-         * - `false`: Meta says Zernio is not subscribed to the message webhook for this number, so inbound messages are not delivered, though the number is CONNECTED and can still send.
+         * - `false`: Meta says Zernio is not subscribed to the message webhook for this number, or the subscribe failed when the number was connected, so inbound messages are not delivered, though the number is CONNECTED and can still send.
          * - `false`, fix: re-subscribe (reconnect the number). If it stays `false`, the number is routed to a different WhatsApp Business Account (typically after linking it to a Facebook Page).
          * - `true`: Meta reports no such problem.
          * - `null`: Meta did not report it (read failed or no health_status); not evidence either way.

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -2288,7 +2288,7 @@ export const verifyWhatsAppNumber = <ThrowOnError extends boolean = false>(optio
  * The OAuth token can be perfectly valid while Meta refuses to serve the phone-number object (for example after a phone-side coexistence disconnect). So `tokenStatus` alone is not a liveness signal for WhatsApp.
  *
  * - When the Meta link is dead, `platformConnection.status` is `disconnected` and the overall `status` is `error`.
- * - When Meta reports that the number's inbound message webhook does not reach Zernio, `platformConnection.inboundWebhookSubscribed` is `false`, an entry is added to `issues`, and the overall `status` is at least `warning`.
+ * - When Meta reports that the number's inbound message webhook does not reach Zernio, or subscribing the number's WhatsApp Business Account to Zernio's webhooks failed at connect, `platformConnection.inboundWebhookSubscribed` is `false`, an entry is added to `issues`, and the overall `status` is at least `warning`.
  *
  * ### Standalone ads connections (`googleads`, `redditads`)
  *

package/src/generated/types.gen.ts

@@ -26819,9 +26819,9 @@ export type GetAccountHealthResponse = ({
             message?: string;
         } | null;
         /**
-         * From the phone number's Meta health_status.
+         * From the phone number's Meta health_status, overridden to `false` when subscribing the number's WhatsApp Business Account to Zernio's webhooks failed at connect.
          *
-         * - `false`: Meta says Zernio is not subscribed to the message webhook for this number, so inbound messages are not delivered, though the number is CONNECTED and can still send.
+         * - `false`: Meta says Zernio is not subscribed to the message webhook for this number, or the subscribe failed when the number was connected, so inbound messages are not delivered, though the number is CONNECTED and can still send.
          * - `false`, fix: re-subscribe (reconnect the number). If it stays `false`, the number is routed to a different WhatsApp Business Account (typically after linking it to a Facebook Page).
          * - `true`: Meta reports no such problem.
          * - `null`: Meta did not report it (read failed or no health_status); not evidence either way.