@getlatedev/node 0.2.1346 → 0.2.1348

package/dist/index.d.mts

@@ -24338,7 +24338,7 @@ type GetConnectUrlData = {
         /**
          * Instagram only. Which of the two Instagram connection methods to use. Ignored for every other platform.
          *
-         * `instagram_login` (the default, and what you get if you omit this): the Instagram Login dialog. The user authorizes their Instagram professional account directly, no Facebook Page required.
+         * `instagram_login` (the default, and what you get if you omit this): the Instagram Login dialog. The user authorizes their Instagram professional account directly, no Facebook Page required. Exception: when you omit it and `reconnectAccountId` names an account connected with `facebook_login`, the reconnect keeps that method and opens the Facebook Login dialog.
          *
          * `facebook_login`: the Facebook Login dialog, i.e. "Instagram API with Facebook Login". The user authorizes a Facebook Page that has a linked Instagram professional account, and every API call for that account then runs through the Page. Use this when the customer manages Instagram through a Page and expects the Facebook consent screen. Because the user has to pick which Page to connect, the callback continues at the account-selection step, `/v1/connect/instagram/select-account`.
          *
@@ -51041,6 +51041,20 @@ type BoostPostData = {
          *
          */
         metaObjective?: 'OUTCOME_ENGAGEMENT';
+        /**
+         * Meta only (facebook, instagram and Meta ads connections). Dry-runs the boost with Meta's
+         * execution_options validate_only: the campaign, ad set, creative (the post reference) and ad
+         * are checked as sent, everything PAUSED, and nothing is created or stored on Meta or in Zernio.
+         * Returns 200 with the same body as a validateOnly POST /v1/ads/create (`validateOnly`, `results`
+         * per node, `message`). Idempotency-Key storage and the duplicate-boost guard are bypassed. Counts
+         * toward the 30 Meta writes per ad account per 5 minutes. With `adSetId` only the ad is dry-run.
+         * An Instagram video that Meta refuses as a direct reference (subcode 1815279) comes back as
+         * `unverified` nodes, because the copy a real boost makes cannot be dry-run.
+         * `true` on any other platform returns 400 naming `validateOnly` and creates nothing; `false` is
+         * ignored. `dryRun` is not a field: sending it returns 400 instead of creating the ad.
+         *
+         */
+        validateOnly?: boolean;
     };
     headers?: {
         /**
@@ -51050,6 +51064,20 @@ type BoostPostData = {
     };
 };
 type BoostPostResponse = ({
+    /**
+     * Always true in a validate-only response.
+     */
+    validateOnly?: boolean;
+    results?: Array<{
+        node?: 'campaign' | 'adSet' | 'creative' | 'ad';
+        status?: 'validated' | 'skipped' | 'unverified';
+        /**
+         * Why the node was skipped (it already exists with adSetId), why Meta could not dry-run it (on unverified), or what the dry run could not check (on validated).
+         */
+        reason?: string;
+    }>;
+    message?: string;
+} | {
     ad?: Ad;
     message?: string;
     instagramVideoFallback?: InstagramVideoFallback;

package/dist/index.d.ts

@@ -24338,7 +24338,7 @@ type GetConnectUrlData = {
         /**
          * Instagram only. Which of the two Instagram connection methods to use. Ignored for every other platform.
          *
-         * `instagram_login` (the default, and what you get if you omit this): the Instagram Login dialog. The user authorizes their Instagram professional account directly, no Facebook Page required.
+         * `instagram_login` (the default, and what you get if you omit this): the Instagram Login dialog. The user authorizes their Instagram professional account directly, no Facebook Page required. Exception: when you omit it and `reconnectAccountId` names an account connected with `facebook_login`, the reconnect keeps that method and opens the Facebook Login dialog.
          *
          * `facebook_login`: the Facebook Login dialog, i.e. "Instagram API with Facebook Login". The user authorizes a Facebook Page that has a linked Instagram professional account, and every API call for that account then runs through the Page. Use this when the customer manages Instagram through a Page and expects the Facebook consent screen. Because the user has to pick which Page to connect, the callback continues at the account-selection step, `/v1/connect/instagram/select-account`.
          *
@@ -51041,6 +51041,20 @@ type BoostPostData = {
          *
          */
         metaObjective?: 'OUTCOME_ENGAGEMENT';
+        /**
+         * Meta only (facebook, instagram and Meta ads connections). Dry-runs the boost with Meta's
+         * execution_options validate_only: the campaign, ad set, creative (the post reference) and ad
+         * are checked as sent, everything PAUSED, and nothing is created or stored on Meta or in Zernio.
+         * Returns 200 with the same body as a validateOnly POST /v1/ads/create (`validateOnly`, `results`
+         * per node, `message`). Idempotency-Key storage and the duplicate-boost guard are bypassed. Counts
+         * toward the 30 Meta writes per ad account per 5 minutes. With `adSetId` only the ad is dry-run.
+         * An Instagram video that Meta refuses as a direct reference (subcode 1815279) comes back as
+         * `unverified` nodes, because the copy a real boost makes cannot be dry-run.
+         * `true` on any other platform returns 400 naming `validateOnly` and creates nothing; `false` is
+         * ignored. `dryRun` is not a field: sending it returns 400 instead of creating the ad.
+         *
+         */
+        validateOnly?: boolean;
     };
     headers?: {
         /**
@@ -51050,6 +51064,20 @@ type BoostPostData = {
     };
 };
 type BoostPostResponse = ({
+    /**
+     * Always true in a validate-only response.
+     */
+    validateOnly?: boolean;
+    results?: Array<{
+        node?: 'campaign' | 'adSet' | 'creative' | 'ad';
+        status?: 'validated' | 'skipped' | 'unverified';
+        /**
+         * Why the node was skipped (it already exists with adSetId), why Meta could not dry-run it (on unverified), or what the dry run could not check (on validated).
+         */
+        reason?: string;
+    }>;
+    message?: string;
+} | {
     ad?: Ad;
     message?: string;
     instagramVideoFallback?: InstagramVideoFallback;

package/dist/index.js

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

package/src/generated/types.gen.ts

@@ -23311,7 +23311,7 @@ export type GetConnectUrlData = {
         /**
          * Instagram only. Which of the two Instagram connection methods to use. Ignored for every other platform.
          *
-         * `instagram_login` (the default, and what you get if you omit this): the Instagram Login dialog. The user authorizes their Instagram professional account directly, no Facebook Page required.
+         * `instagram_login` (the default, and what you get if you omit this): the Instagram Login dialog. The user authorizes their Instagram professional account directly, no Facebook Page required. Exception: when you omit it and `reconnectAccountId` names an account connected with `facebook_login`, the reconnect keeps that method and opens the Facebook Login dialog.
          *
          * `facebook_login`: the Facebook Login dialog, i.e. "Instagram API with Facebook Login". The user authorizes a Facebook Page that has a linked Instagram professional account, and every API call for that account then runs through the Page. Use this when the customer manages Instagram through a Page and expects the Facebook consent screen. Because the user has to pick which Page to connect, the callback continues at the account-selection step, `/v1/connect/instagram/select-account`.
          *
@@ -51985,6 +51985,20 @@ export type BoostPostData = {
          *
          */
         metaObjective?: 'OUTCOME_ENGAGEMENT';
+        /**
+         * Meta only (facebook, instagram and Meta ads connections). Dry-runs the boost with Meta's
+         * execution_options validate_only: the campaign, ad set, creative (the post reference) and ad
+         * are checked as sent, everything PAUSED, and nothing is created or stored on Meta or in Zernio.
+         * Returns 200 with the same body as a validateOnly POST /v1/ads/create (`validateOnly`, `results`
+         * per node, `message`). Idempotency-Key storage and the duplicate-boost guard are bypassed. Counts
+         * toward the 30 Meta writes per ad account per 5 minutes. With `adSetId` only the ad is dry-run.
+         * An Instagram video that Meta refuses as a direct reference (subcode 1815279) comes back as
+         * `unverified` nodes, because the copy a real boost makes cannot be dry-run.
+         * `true` on any other platform returns 400 naming `validateOnly` and creates nothing; `false` is
+         * ignored. `dryRun` is not a field: sending it returns 400 instead of creating the ad.
+         *
+         */
+        validateOnly?: boolean;
     };
     headers?: {
         /**
@@ -51995,6 +52009,20 @@ export type BoostPostData = {
 };
 
 export type BoostPostResponse = ({
+    /**
+     * Always true in a validate-only response.
+     */
+    validateOnly?: boolean;
+    results?: Array<{
+        node?: 'campaign' | 'adSet' | 'creative' | 'ad';
+        status?: 'validated' | 'skipped' | 'unverified';
+        /**
+         * Why the node was skipped (it already exists with adSetId), why Meta could not dry-run it (on unverified), or what the dry run could not check (on validated).
+         */
+        reason?: string;
+    }>;
+    message?: string;
+} | {
     ad?: Ad;
     message?: string;
     instagramVideoFallback?: InstagramVideoFallback;