@zernio/node 0.2.891 → 0.2.893

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.mts CHANGED
@@ -16286,6 +16286,10 @@ type GetAccountHealthResponse = ({
16286
16286
  subcode?: number;
16287
16287
  message?: string;
16288
16288
  } | null;
16289
+ /**
16290
+ * From the phone number's Meta health_status. `false` = Meta says Zernio is not subscribed to the message webhook for this number, so inbound messages are not delivered even though the number is CONNECTED and can still send. Fix by re-subscribing (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.
16291
+ */
16292
+ inboundWebhookSubscribed?: (boolean) | null;
16289
16293
  };
16290
16294
  });
16291
16295
  type GetAccountHealthError = (ErrorResponse | {
package/dist/index.d.ts CHANGED
@@ -16286,6 +16286,10 @@ type GetAccountHealthResponse = ({
16286
16286
  subcode?: number;
16287
16287
  message?: string;
16288
16288
  } | null;
16289
+ /**
16290
+ * From the phone number's Meta health_status. `false` = Meta says Zernio is not subscribed to the message webhook for this number, so inbound messages are not delivered even though the number is CONNECTED and can still send. Fix by re-subscribing (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.
16291
+ */
16292
+ inboundWebhookSubscribed?: (boolean) | null;
16289
16293
  };
16290
16294
  });
16291
16295
  type GetAccountHealthError = (ErrorResponse | {
package/dist/index.js CHANGED
@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
36
36
  // package.json
37
37
  var package_default = {
38
38
  name: "@zernio/node",
39
- version: "0.2.891",
39
+ version: "0.2.893",
40
40
  description: "The official Node.js library for the Zernio API",
41
41
  main: "dist/index.js",
42
42
  module: "dist/index.mjs",
package/dist/index.mjs CHANGED
@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
5
5
  // package.json
6
6
  var package_default = {
7
7
  name: "@zernio/node",
8
- version: "0.2.891",
8
+ version: "0.2.893",
9
9
  description: "The official Node.js library for the Zernio API",
10
10
  main: "dist/index.js",
11
11
  module: "dist/index.mjs",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@zernio/node",
3
- "version": "0.2.891",
3
+ "version": "0.2.893",
4
4
  "description": "The official Node.js library for the Zernio API",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
@@ -1386,7 +1386,9 @@ export const verifyWhatsAppNumber = <ThrowOnError extends boolean = false>(optio
1386
1386
  * token can be perfectly valid while Meta refuses to serve the phone-number object (for
1387
1387
  * example after a phone-side coexistence disconnect), so `tokenStatus` alone is not a
1388
1388
  * liveness signal for WhatsApp. When the Meta link is dead, `platformConnection.status` is
1389
- * `disconnected` and the overall `status` is `error`.
1389
+ * `disconnected` and the overall `status` is `error`. When Meta reports that the number's
1390
+ * inbound message webhook does not reach Zernio, `platformConnection.inboundWebhookSubscribed`
1391
+ * is `false`, an entry is added to `issues`, and the overall `status` is at least `warning`.
1390
1392
  *
1391
1393
  */
1392
1394
  export const getAccountHealth = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetAccountHealthData, ThrowOnError>) => {
@@ -9621,7 +9623,6 @@ export const getAdAnalytics = <ThrowOnError extends boolean = false>(options: Op
9621
9623
  * Unified read of the platform's native click-URL tracking params.
9622
9624
  * - Meta (facebook/instagram): the creative's `url_tags` (and template_url_spec).
9623
9625
  * - Google (googleads): the campaign's `trackingUrlTemplate` + `finalUrlSuffix`.
9624
- * Subject to the Google Ads API access-tier daily quota; bulk audits need Standard access.
9625
9626
  * - LinkedIn (linkedinads): the campaign's Dynamic UTM `dynamicValueParameters` + `customValueParameters`.
9626
9627
  * Returns 405 for platforms without a click-URL tracking surface (TikTok, X, Pinterest).
9627
9628
  *
@@ -15291,6 +15291,10 @@ export type GetAccountHealthResponse = ({
15291
15291
  subcode?: number;
15292
15292
  message?: string;
15293
15293
  } | null;
15294
+ /**
15295
+ * From the phone number's Meta health_status. `false` = Meta says Zernio is not subscribed to the message webhook for this number, so inbound messages are not delivered even though the number is CONNECTED and can still send. Fix by re-subscribing (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.
15296
+ */
15297
+ inboundWebhookSubscribed?: (boolean) | null;
15294
15298
  };
15295
15299
  });
15296
15300