@getlatedev/node 0.2.577 → 0.2.579

package/dist/index.d.mts

@@ -12283,8 +12283,39 @@ type GetAccountHealthResponse = ({
      * Actionable recommendations to fix issues
      */
     recommendations?: Array<(string)>;
+    /**
+     * 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).
+     */
+    platformConnection?: {
+        /**
+         * `connected` = Meta served the channel object. `disconnected` = Meta refused to serve it (Graph error 100, subcode 33), which is how a phone-side coexistence disconnect surfaces. `unknown` = the live read failed for another reason (timeout, transient Meta error), not evidence either way.
+         */
+        status?: 'connected' | 'disconnected' | 'unknown';
+        /**
+         * When this live probe ran (always the current request; never cached)
+         */
+        checkedAt?: string;
+        /**
+         * Meta's own `status` field from the phone-number node (for example CONNECTED), when the object was readable
+         */
+        phoneStatus?: (string) | null;
+        /**
+         * Set only when status is `disconnected`
+         */
+        metaError?: {
+            /**
+             * Meta Graph error code (100)
+             */
+            code?: number;
+            /**
+             * Meta Graph error subcode (33)
+             */
+            subcode?: number;
+            message?: string;
+        } | null;
+    };
 });
-type GetAccountHealthError = ({
+type GetAccountHealthError = (ErrorResponse | {
     error?: string;
 });
 type GetInstagramFollowStatusData = {
@@ -17569,7 +17600,7 @@ type SearchInboxConversationsData = {
          */
         accountId?: string;
         /**
-         * Pagination cursor for next page
+         * Opaque pagination cursor. Pass back pagination.nextCursor verbatim; do not construct one.
          */
         cursor?: string;
         /**

package/dist/index.d.ts

@@ -12283,8 +12283,39 @@ type GetAccountHealthResponse = ({
      * Actionable recommendations to fix issues
      */
     recommendations?: Array<(string)>;
+    /**
+     * 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).
+     */
+    platformConnection?: {
+        /**
+         * `connected` = Meta served the channel object. `disconnected` = Meta refused to serve it (Graph error 100, subcode 33), which is how a phone-side coexistence disconnect surfaces. `unknown` = the live read failed for another reason (timeout, transient Meta error), not evidence either way.
+         */
+        status?: 'connected' | 'disconnected' | 'unknown';
+        /**
+         * When this live probe ran (always the current request; never cached)
+         */
+        checkedAt?: string;
+        /**
+         * Meta's own `status` field from the phone-number node (for example CONNECTED), when the object was readable
+         */
+        phoneStatus?: (string) | null;
+        /**
+         * Set only when status is `disconnected`
+         */
+        metaError?: {
+            /**
+             * Meta Graph error code (100)
+             */
+            code?: number;
+            /**
+             * Meta Graph error subcode (33)
+             */
+            subcode?: number;
+            message?: string;
+        } | null;
+    };
 });
-type GetAccountHealthError = ({
+type GetAccountHealthError = (ErrorResponse | {
     error?: string;
 });
 type GetInstagramFollowStatusData = {
@@ -17569,7 +17600,7 @@ type SearchInboxConversationsData = {
          */
         accountId?: string;
         /**
-         * Pagination cursor for next page
+         * Opaque pagination cursor. Pass back pagination.nextCursor verbatim; do not construct one.
          */
         cursor?: string;
         /**

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -1167,6 +1167,14 @@ export const registerWhatsAppNumber = <ThrowOnError extends boolean = false>(opt
 /**
  * Check account health
  * Returns detailed health info for a specific account including token status, permissions, and recommendations.
+ *
+ * For WhatsApp accounts the response also includes `platformConnection`, a live probe of the
+ * Meta link behind the channel (the same read as `GET /v1/whatsapp/number-info`). 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`.
+ *
  */
 export const getAccountHealth = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetAccountHealthData, ThrowOnError>) => {
     return (options?.client ?? client).get<GetAccountHealthResponse, GetAccountHealthError, ThrowOnError>({

package/src/generated/types.gen.ts

@@ -11526,9 +11526,40 @@ export type GetAccountHealthResponse = ({
      * Actionable recommendations to fix issues
      */
     recommendations?: Array<(string)>;
+    /**
+     * 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).
+     */
+    platformConnection?: {
+        /**
+         * `connected` = Meta served the channel object. `disconnected` = Meta refused to serve it (Graph error 100, subcode 33), which is how a phone-side coexistence disconnect surfaces. `unknown` = the live read failed for another reason (timeout, transient Meta error), not evidence either way.
+         */
+        status?: 'connected' | 'disconnected' | 'unknown';
+        /**
+         * When this live probe ran (always the current request; never cached)
+         */
+        checkedAt?: string;
+        /**
+         * Meta's own `status` field from the phone-number node (for example CONNECTED), when the object was readable
+         */
+        phoneStatus?: (string) | null;
+        /**
+         * Set only when status is `disconnected`
+         */
+        metaError?: {
+            /**
+             * Meta Graph error code (100)
+             */
+            code?: number;
+            /**
+             * Meta Graph error subcode (33)
+             */
+            subcode?: number;
+            message?: string;
+        } | null;
+    };
 });
 
-export type GetAccountHealthError = ({
+export type GetAccountHealthError = (ErrorResponse | {
     error?: string;
 });
 
@@ -17197,7 +17228,7 @@ export type SearchInboxConversationsData = {
          */
         accountId?: string;
         /**
-         * Pagination cursor for next page
+         * Opaque pagination cursor. Pass back pagination.nextCursor verbatim; do not construct one.
          */
         cursor?: string;
         /**