@getlatedev/node 0.2.1150 → 0.2.1152

package/dist/index.d.mts

@@ -15152,7 +15152,7 @@ type WebhookPayloadMessage = {
      */
     metadata?: {
         /**
-         * true when this inbound arrived on Meta's standby path because another app owned the conversation: Meta Business Agent on WhatsApp, another handover receiver (such as Page Inbox) on Facebook and Instagram. That app answers it, Zernio only observes, and no automation runs. On WhatsApp sending a reply takes control back; on Facebook and Instagram take control first with POST /v1/inbox/conversations/{conversationId}/thread-control. See conversation.control_changed.
+         * true when this inbound arrived on Meta's standby path because another app owned the conversation: Meta Business Agent on WhatsApp, another handover receiver (such as Page Inbox) on Facebook and Instagram. That app answers it, Zernio only observes, and no automation runs. On WhatsApp sending a reply takes control back; on Facebook, and on Instagram accounts connected through a Facebook Page, take control first with POST /v1/inbox/conversations/{conversationId}/thread-control; an Instagram Login connection cannot take or request and waits for the owner to pass it. See conversation.control_changed.
          */
         standby?: boolean;
         /**
@@ -20728,6 +20728,16 @@ type GetAllAccountsHealthResponse = ({
          */
         needsReconnect?: boolean;
         issues?: Array<(string)>;
+        /**
+         * Absent on platforms without analytics sync. failing: several consecutive sync attempts failed. stalled: a sync was requested over 6 hours ago and never completed. never_synced: no sync has completed yet. Failing and stalled raise the account status to at least warning.
+         */
+        analyticsSync?: {
+            status?: 'ok' | 'failing' | 'stalled' | 'never_synced';
+            /**
+             * Last successful sync. Null when never synced or the latest attempt failed.
+             */
+            lastSyncedAt?: (string) | null;
+        };
         /**
          * 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.
          */
@@ -20882,6 +20892,16 @@ type GetAccountHealthResponse = ({
      * Actionable recommendations to fix issues
      */
     recommendations?: Array<(string)>;
+    /**
+     * Absent on platforms without analytics sync. failing: several consecutive sync attempts failed. stalled: a sync was requested over 6 hours ago and never completed. never_synced: no sync has completed yet. Failing and stalled raise the account status to at least warning.
+     */
+    analyticsSync?: {
+        status?: 'ok' | 'failing' | 'stalled' | 'never_synced';
+        /**
+         * Last successful sync. Null when never synced or the latest attempt failed.
+         */
+        lastSyncedAt?: (string) | null;
+    };
     /**
      * 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.
      */
@@ -29389,7 +29409,7 @@ type SetConversationThreadControlData = {
          */
         accountId: string;
         /**
-         * `request` is Facebook and Instagram only.
+         * `request` is Facebook and Instagram only. `take` and `request` are refused with `platform_not_supported` on Instagram accounts connected with Instagram Login.
          */
         action: 'release' | 'take' | 'pass' | 'request';
         /**

package/dist/index.d.ts

@@ -15152,7 +15152,7 @@ type WebhookPayloadMessage = {
      */
     metadata?: {
         /**
-         * true when this inbound arrived on Meta's standby path because another app owned the conversation: Meta Business Agent on WhatsApp, another handover receiver (such as Page Inbox) on Facebook and Instagram. That app answers it, Zernio only observes, and no automation runs. On WhatsApp sending a reply takes control back; on Facebook and Instagram take control first with POST /v1/inbox/conversations/{conversationId}/thread-control. See conversation.control_changed.
+         * true when this inbound arrived on Meta's standby path because another app owned the conversation: Meta Business Agent on WhatsApp, another handover receiver (such as Page Inbox) on Facebook and Instagram. That app answers it, Zernio only observes, and no automation runs. On WhatsApp sending a reply takes control back; on Facebook, and on Instagram accounts connected through a Facebook Page, take control first with POST /v1/inbox/conversations/{conversationId}/thread-control; an Instagram Login connection cannot take or request and waits for the owner to pass it. See conversation.control_changed.
          */
         standby?: boolean;
         /**
@@ -20728,6 +20728,16 @@ type GetAllAccountsHealthResponse = ({
          */
         needsReconnect?: boolean;
         issues?: Array<(string)>;
+        /**
+         * Absent on platforms without analytics sync. failing: several consecutive sync attempts failed. stalled: a sync was requested over 6 hours ago and never completed. never_synced: no sync has completed yet. Failing and stalled raise the account status to at least warning.
+         */
+        analyticsSync?: {
+            status?: 'ok' | 'failing' | 'stalled' | 'never_synced';
+            /**
+             * Last successful sync. Null when never synced or the latest attempt failed.
+             */
+            lastSyncedAt?: (string) | null;
+        };
         /**
          * 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.
          */
@@ -20882,6 +20892,16 @@ type GetAccountHealthResponse = ({
      * Actionable recommendations to fix issues
      */
     recommendations?: Array<(string)>;
+    /**
+     * Absent on platforms without analytics sync. failing: several consecutive sync attempts failed. stalled: a sync was requested over 6 hours ago and never completed. never_synced: no sync has completed yet. Failing and stalled raise the account status to at least warning.
+     */
+    analyticsSync?: {
+        status?: 'ok' | 'failing' | 'stalled' | 'never_synced';
+        /**
+         * Last successful sync. Null when never synced or the latest attempt failed.
+         */
+        lastSyncedAt?: (string) | null;
+    };
     /**
      * 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.
      */
@@ -29389,7 +29409,7 @@ type SetConversationThreadControlData = {
          */
         accountId: string;
         /**
-         * `request` is Facebook and Instagram only.
+         * `request` is Facebook and Instagram only. `take` and `request` are refused with `platform_not_supported` on Instagram accounts connected with Instagram Login.
          */
         action: 'release' | 'take' | 'pass' | 'request';
         /**

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -1396,7 +1396,7 @@ export const deleteAccount = <ThrowOnError extends boolean = false>(options: Opt
 
 /**
  * Check accounts health
- * Returns health status of all connected accounts including token validity, permissions, and issues needing attention.
+ * Returns health status of all connected accounts including token validity, permissions, and issues needing attention. A failing or stalled analytics sync (see `analyticsSync`) raises a healthy account to at least warning.
  */
 export const getAllAccountsHealth = <ThrowOnError extends boolean = false>(options?: OptionsLegacyParser<GetAllAccountsHealthData, ThrowOnError>) => {
     return (options?.client ?? client).get<GetAllAccountsHealthResponse, GetAllAccountsHealthError, ThrowOnError>({
@@ -1456,6 +1456,8 @@ export const verifyWhatsAppNumber = <ThrowOnError extends boolean = false>(optio
  * Check account health
  * Returns detailed health info for a specific account including token status, permissions, and recommendations.
  *
+ * A failing or stalled analytics sync (see `analyticsSync`) raises a healthy account to at least `warning`.
+ *
  * 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
@@ -4242,8 +4244,8 @@ export const sendTypingIndicator = <ThrowOnError extends boolean = false>(option
  *
  * **Facebook and Instagram** (Messenger Platform handover between the apps on the Page, such as Page Inbox):
  * - `pass` with `targetAppId`: give the thread to another app (`pass_thread_control`). Page Inbox is 263902037430900.
- * - `take`: take the thread back (`take_thread_control`); Meta allows it only to the Page's primary receiver.
- * - `request`: ask the current owner to pass the thread (`request_thread_control`); nothing changes until it does.
+ * - `take`: take the thread back (`take_thread_control`); Meta allows it only to the Page's primary receiver, and only on accounts connected through a Facebook Page. On an Instagram Login connection it answers 400 `platform_not_supported`.
+ * - `request`: ask the current owner to pass the thread (`request_thread_control`); nothing changes until it does. Not available on Instagram Login connections (400 `platform_not_supported`).
  * - `release`: give the thread back to the primary receiver (`release_thread_control`).
  *
  * While another app owns a Facebook or Instagram thread, inbound arrive with `metadata.standby: true` and a send answers 409 `not_thread_owner`. The conversation's `threadControl` follows the result; a `conversation.control_changed` webhook fires when Meta later reports the change.

package/src/generated/types.gen.ts

@@ -13727,7 +13727,7 @@ export type WebhookPayloadMessage = {
      */
     metadata?: {
         /**
-         * true when this inbound arrived on Meta's standby path because another app owned the conversation: Meta Business Agent on WhatsApp, another handover receiver (such as Page Inbox) on Facebook and Instagram. That app answers it, Zernio only observes, and no automation runs. On WhatsApp sending a reply takes control back; on Facebook and Instagram take control first with POST /v1/inbox/conversations/{conversationId}/thread-control. See conversation.control_changed.
+         * true when this inbound arrived on Meta's standby path because another app owned the conversation: Meta Business Agent on WhatsApp, another handover receiver (such as Page Inbox) on Facebook and Instagram. That app answers it, Zernio only observes, and no automation runs. On WhatsApp sending a reply takes control back; on Facebook, and on Instagram accounts connected through a Facebook Page, take control first with POST /v1/inbox/conversations/{conversationId}/thread-control; an Instagram Login connection cannot take or request and waits for the owner to pass it. See conversation.control_changed.
          */
         standby?: boolean;
         /**
@@ -19626,6 +19626,16 @@ export type GetAllAccountsHealthResponse = ({
          */
         needsReconnect?: boolean;
         issues?: Array<(string)>;
+        /**
+         * Absent on platforms without analytics sync. failing: several consecutive sync attempts failed. stalled: a sync was requested over 6 hours ago and never completed. never_synced: no sync has completed yet. Failing and stalled raise the account status to at least warning.
+         */
+        analyticsSync?: {
+            status?: 'ok' | 'failing' | 'stalled' | 'never_synced';
+            /**
+             * Last successful sync. Null when never synced or the latest attempt failed.
+             */
+            lastSyncedAt?: (string) | null;
+        };
         /**
          * 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.
          */
@@ -19792,6 +19802,16 @@ export type GetAccountHealthResponse = ({
      * Actionable recommendations to fix issues
      */
     recommendations?: Array<(string)>;
+    /**
+     * Absent on platforms without analytics sync. failing: several consecutive sync attempts failed. stalled: a sync was requested over 6 hours ago and never completed. never_synced: no sync has completed yet. Failing and stalled raise the account status to at least warning.
+     */
+    analyticsSync?: {
+        status?: 'ok' | 'failing' | 'stalled' | 'never_synced';
+        /**
+         * Last successful sync. Null when never synced or the latest attempt failed.
+         */
+        lastSyncedAt?: (string) | null;
+    };
     /**
      * 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.
      */
@@ -28787,7 +28807,7 @@ export type SetConversationThreadControlData = {
          */
         accountId: string;
         /**
-         * `request` is Facebook and Instagram only.
+         * `request` is Facebook and Instagram only. `take` and `request` are refused with `platform_not_supported` on Instagram accounts connected with Instagram Login.
          */
         action: 'release' | 'take' | 'pass' | 'request';
         /**