@getlatedev/node 0.2.1149 → 0.2.1151

package/dist/index.d.mts

@@ -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.
      */

package/dist/index.d.ts

@@ -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.
      */

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@getlatedev/node",
-  version: "0.2.1149",
+  version: "0.2.1151",
   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.1149",
+  version: "0.2.1151",
   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.1149",
+  "version": "0.2.1151",
   "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
@@ -13749,6 +13751,8 @@ export const sendWhatsAppConversion = <ThrowOnError extends boolean = false>(opt
  * `accountId` is a Facebook, Instagram or Meta ads (business login) connection;
  * `pageId` picks the Page when that connection was granted several.
  *
+ * **WhatsApp number prerequisite.** For the WhatsApp destination, link the WhatsApp number to the Facebook Page used for the ad before creating it: Meta checks the pairing at creation. Link it from the WhatsApp Business app (Settings > Business tools > Facebook & Instagram) or from the Page settings (Linked accounts > WhatsApp). Linking does not affect the number's WhatsApp connection in Zernio (Cloud API or coexistence), so no reconnect or re-sync is needed. If Meta creates a new ad set without the requested `whatsappPhoneNumber`, the 201 response carries a `warnings` entry. This can happen even when the number is linked (Meta can drop a Page's second linked number).
+ *
  * **Idempotency:** this endpoint is not idempotent at the platform level (a blind retry creates a second campaign/ad set/ad). Send an `Idempotency-Key` header to make retries safe: the first request with a given key creates the ad and we store the response; a retry with the same key replays that exact response (with `Idempotent-Replayed: true`) instead of creating duplicates. Reusing a key with a different body returns 422; a key whose first request is still in flight returns 409 (retry after a short backoff). Keys are scoped to your credential and expire after 24h.
  */
 export const createMessagingAd = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<CreateMessagingAdData, ThrowOnError>) => {
@@ -13795,6 +13799,8 @@ export const createCallAd = <ThrowOnError extends boolean = false>(options: Opti
  * media and copy for that creative. Optional `whatsappPhoneNumber` selects
  * a number already paired with the Page (WhatsApp destination only).
  *
+ * **WhatsApp number prerequisite.** Link the WhatsApp number to the Facebook Page used for the ad before creating it: Meta checks the pairing at creation. Link it from the WhatsApp Business app (Settings > Business tools > Facebook & Instagram) or from the Page settings (Linked accounts > WhatsApp). Linking does not affect the number's WhatsApp connection in Zernio (Cloud API or coexistence), so no reconnect or re-sync is needed. If Meta creates a new ad set without the requested `whatsappPhoneNumber`, the 201 response carries a `warnings` entry. This can happen even when the number is linked (Meta can drop a Page's second linked number).
+ *
  * **Idempotency:** this endpoint is not idempotent at the platform level (a blind retry creates a second campaign/ad set/ad). Send an `Idempotency-Key` header to make retries safe: the first request with a given key creates the ad and we store the response; a retry with the same key replays that exact response (with `Idempotent-Replayed: true`) instead of creating duplicates. Reusing a key with a different body returns 422; a key whose first request is still in flight returns 409 (retry after a short backoff). Keys are scoped to your credential and expire after 24h.
  */
 export const createCtwaAd = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<CreateCtwaAdData, ThrowOnError>) => {

package/src/generated/types.gen.ts

@@ -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.
      */