@zernio/node 0.2.1037 → 0.2.1039

package/dist/index.d.mts

@@ -11618,7 +11618,7 @@ type TargetingSpec = {
         name?: string;
     }>;
     /**
-     * Behaviour entities from /v1/ads/targeting/search?dimension=behavior (Meta and TikTok). On TikTok they target people who interacted with videos (watched to the end, liked, commented or shared, last 15 days) or creators (followed or viewed the profile) in the picked categories, and the ad group uses the TikTok placement only.
+     * Behaviour entities from /v1/ads/targeting/search?dimension=behavior (Meta, TikTok and LinkedIn). On TikTok they target people who interacted with videos (watched to the end, liked, commented or shared, last 15 days) or creators (followed or viewed the profile) in the picked categories, and the ad group uses the TikTok placement only.
      */
     behaviors?: Array<{
         id: string;
@@ -19220,7 +19220,7 @@ type GetAllAccountsHealthResponse = ({
         needsReconnect?: boolean;
         issues?: Array<(string)>;
         /**
-         * 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.
+         * 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.
          */
         messagingRestriction?: {
             /**
@@ -19234,6 +19234,10 @@ type GetAllAccountsHealthResponse = ({
             message?: (string) | null;
             firstSeenAt?: string;
             lastSeenAt?: string;
+            /**
+             * When held automation DMs are next retried. Null when nothing is held.
+             */
+            pausedUntil?: (string) | null;
         } | null;
     }>;
 });
@@ -19372,7 +19376,7 @@ type GetAccountHealthResponse = ({
      */
     recommendations?: Array<(string)>;
     /**
-     * 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.
+     * 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.
      */
     messagingRestriction?: {
         /**
@@ -19386,6 +19390,10 @@ type GetAccountHealthResponse = ({
         message?: (string) | null;
         firstSeenAt?: string;
         lastSeenAt?: string;
+        /**
+         * When held automation DMs are next retried. Null when nothing is held.
+         */
+        pausedUntil?: (string) | null;
     } | null;
     /**
      * 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).
@@ -45484,7 +45492,7 @@ type CreateStandaloneAdData = {
             address?: string;
         }>;
         /**
-         * Behaviour entities from /v1/ads/targeting/search?dimension=behavior (Meta and TikTok). On TikTok they target people who interacted with videos (watched to the end, liked, commented or shared, last 15 days) or creators (followed or viewed the profile) in the picked categories, and the ad group uses the TikTok placement only. Each must include id.
+         * Behaviour entities from /v1/ads/targeting/search?dimension=behavior (Meta, TikTok and LinkedIn). On TikTok they target people who interacted with videos (watched to the end, liked, commented or shared, last 15 days) or creators (followed or viewed the profile) in the picked categories, and the ad group uses the TikTok placement only. Each must include id.
          */
         behaviors?: Array<{
             id: string;

package/dist/index.d.ts

@@ -11618,7 +11618,7 @@ type TargetingSpec = {
         name?: string;
     }>;
     /**
-     * Behaviour entities from /v1/ads/targeting/search?dimension=behavior (Meta and TikTok). On TikTok they target people who interacted with videos (watched to the end, liked, commented or shared, last 15 days) or creators (followed or viewed the profile) in the picked categories, and the ad group uses the TikTok placement only.
+     * Behaviour entities from /v1/ads/targeting/search?dimension=behavior (Meta, TikTok and LinkedIn). On TikTok they target people who interacted with videos (watched to the end, liked, commented or shared, last 15 days) or creators (followed or viewed the profile) in the picked categories, and the ad group uses the TikTok placement only.
      */
     behaviors?: Array<{
         id: string;
@@ -19220,7 +19220,7 @@ type GetAllAccountsHealthResponse = ({
         needsReconnect?: boolean;
         issues?: Array<(string)>;
         /**
-         * 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.
+         * 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.
          */
         messagingRestriction?: {
             /**
@@ -19234,6 +19234,10 @@ type GetAllAccountsHealthResponse = ({
             message?: (string) | null;
             firstSeenAt?: string;
             lastSeenAt?: string;
+            /**
+             * When held automation DMs are next retried. Null when nothing is held.
+             */
+            pausedUntil?: (string) | null;
         } | null;
     }>;
 });
@@ -19372,7 +19376,7 @@ type GetAccountHealthResponse = ({
      */
     recommendations?: Array<(string)>;
     /**
-     * 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.
+     * 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.
      */
     messagingRestriction?: {
         /**
@@ -19386,6 +19390,10 @@ type GetAccountHealthResponse = ({
         message?: (string) | null;
         firstSeenAt?: string;
         lastSeenAt?: string;
+        /**
+         * When held automation DMs are next retried. Null when nothing is held.
+         */
+        pausedUntil?: (string) | null;
     } | null;
     /**
      * 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).
@@ -45484,7 +45492,7 @@ type CreateStandaloneAdData = {
             address?: string;
         }>;
         /**
-         * Behaviour entities from /v1/ads/targeting/search?dimension=behavior (Meta and TikTok). On TikTok they target people who interacted with videos (watched to the end, liked, commented or shared, last 15 days) or creators (followed or viewed the profile) in the picked categories, and the ad group uses the TikTok placement only. Each must include id.
+         * Behaviour entities from /v1/ads/targeting/search?dimension=behavior (Meta, TikTok and LinkedIn). On TikTok they target people who interacted with videos (watched to the end, liked, commented or shared, last 15 days) or creators (followed or viewed the profile) in the picked categories, and the ad group uses the TikTok placement only. Each must include id.
          */
         behaviors?: Array<{
             id: string;

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -12001,11 +12001,14 @@ export const searchAdInterests = <ThrowOnError extends boolean = false>(options:
  *
  * - `geo`: locations, further scoped by `geoType`
  * - `interest`
- * - `behavior`: Meta and TikTok, matched by name; ids feed `TargetingSpec.behaviors`.
+ * - `behavior`: Meta, TikTok and LinkedIn, matched by name; ids feed `TargetingSpec.behaviors`.
  * Meta: its fixed behaviors catalog (e.g. `Small business owners`, `Frequent Travelers`).
  * TikTok: video and creator interaction categories (e.g. `Software & Apps`), with ids like
  * `video:1913101` or `creator:24001` and `path` starting with `Video interactions` or
- * `Creator interactions`
+ * `Creator interactions`. LinkedIn: member behaviors (e.g. `Frequent Travelers`,
+ * `Job Seekers`, `Recently Promoted`), ids like `urn:li:memberBehavior:9`. Google has no
+ * separate behavior catalog: its in-market and affinity segments come back from `interest`,
+ * and X removed behavior targeting from its Ads API
  * - `income`: the household-income tiers the platform can target (Meta, TikTok, Google).
  * The id is the normalized tier (`top_5`, `top_10`, `top_10_25`, `top_25_50`) to pass as
  * `TargetingSpec.incomeTier`, never a platform segment id. Meta's tiers are US-only

package/src/generated/types.gen.ts

@@ -10096,7 +10096,7 @@ export type TargetingSpec = {
         name?: string;
     }>;
     /**
-     * Behaviour entities from /v1/ads/targeting/search?dimension=behavior (Meta and TikTok). On TikTok they target people who interacted with videos (watched to the end, liked, commented or shared, last 15 days) or creators (followed or viewed the profile) in the picked categories, and the ad group uses the TikTok placement only.
+     * Behaviour entities from /v1/ads/targeting/search?dimension=behavior (Meta, TikTok and LinkedIn). On TikTok they target people who interacted with videos (watched to the end, liked, commented or shared, last 15 days) or creators (followed or viewed the profile) in the picked categories, and the ad group uses the TikTok placement only.
      */
     behaviors?: Array<{
         id: string;
@@ -18098,7 +18098,7 @@ export type GetAllAccountsHealthResponse = ({
         needsReconnect?: boolean;
         issues?: Array<(string)>;
         /**
-         * 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.
+         * 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.
          */
         messagingRestriction?: {
             /**
@@ -18112,6 +18112,10 @@ export type GetAllAccountsHealthResponse = ({
             message?: (string) | null;
             firstSeenAt?: string;
             lastSeenAt?: string;
+            /**
+             * When held automation DMs are next retried. Null when nothing is held.
+             */
+            pausedUntil?: (string) | null;
         } | null;
     }>;
 });
@@ -18262,7 +18266,7 @@ export type GetAccountHealthResponse = ({
      */
     recommendations?: Array<(string)>;
     /**
-     * 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.
+     * 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.
      */
     messagingRestriction?: {
         /**
@@ -18276,6 +18280,10 @@ export type GetAccountHealthResponse = ({
         message?: (string) | null;
         firstSeenAt?: string;
         lastSeenAt?: string;
+        /**
+         * When held automation DMs are next retried. Null when nothing is held.
+         */
+        pausedUntil?: (string) | null;
     } | null;
     /**
      * 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).
@@ -46213,7 +46221,7 @@ export type CreateStandaloneAdData = {
             address?: string;
         }>;
         /**
-         * Behaviour entities from /v1/ads/targeting/search?dimension=behavior (Meta and TikTok). On TikTok they target people who interacted with videos (watched to the end, liked, commented or shared, last 15 days) or creators (followed or viewed the profile) in the picked categories, and the ad group uses the TikTok placement only. Each must include id.
+         * Behaviour entities from /v1/ads/targeting/search?dimension=behavior (Meta, TikTok and LinkedIn). On TikTok they target people who interacted with videos (watched to the end, liked, commented or shared, last 15 days) or creators (followed or viewed the profile) in the picked categories, and the ad group uses the TikTok placement only. Each must include id.
          */
         behaviors?: Array<{
             id: string;