@getlatedev/node 0.2.1346 → 0.2.1347

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.mts CHANGED
@@ -51041,6 +51041,20 @@ type BoostPostData = {
51041
51041
  *
51042
51042
  */
51043
51043
  metaObjective?: 'OUTCOME_ENGAGEMENT';
51044
+ /**
51045
+ * Meta only (facebook, instagram and Meta ads connections). Dry-runs the boost with Meta's
51046
+ * execution_options validate_only: the campaign, ad set, creative (the post reference) and ad
51047
+ * are checked as sent, everything PAUSED, and nothing is created or stored on Meta or in Zernio.
51048
+ * Returns 200 with the same body as a validateOnly POST /v1/ads/create (`validateOnly`, `results`
51049
+ * per node, `message`). Idempotency-Key storage and the duplicate-boost guard are bypassed. Counts
51050
+ * toward the 30 Meta writes per ad account per 5 minutes. With `adSetId` only the ad is dry-run.
51051
+ * An Instagram video that Meta refuses as a direct reference (subcode 1815279) comes back as
51052
+ * `unverified` nodes, because the copy a real boost makes cannot be dry-run.
51053
+ * `true` on any other platform returns 400 naming `validateOnly` and creates nothing; `false` is
51054
+ * ignored. `dryRun` is not a field: sending it returns 400 instead of creating the ad.
51055
+ *
51056
+ */
51057
+ validateOnly?: boolean;
51044
51058
  };
51045
51059
  headers?: {
51046
51060
  /**
@@ -51050,6 +51064,20 @@ type BoostPostData = {
51050
51064
  };
51051
51065
  };
51052
51066
  type BoostPostResponse = ({
51067
+ /**
51068
+ * Always true in a validate-only response.
51069
+ */
51070
+ validateOnly?: boolean;
51071
+ results?: Array<{
51072
+ node?: 'campaign' | 'adSet' | 'creative' | 'ad';
51073
+ status?: 'validated' | 'skipped' | 'unverified';
51074
+ /**
51075
+ * 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).
51076
+ */
51077
+ reason?: string;
51078
+ }>;
51079
+ message?: string;
51080
+ } | {
51053
51081
  ad?: Ad;
51054
51082
  message?: string;
51055
51083
  instagramVideoFallback?: InstagramVideoFallback;
package/dist/index.d.ts CHANGED
@@ -51041,6 +51041,20 @@ type BoostPostData = {
51041
51041
  *
51042
51042
  */
51043
51043
  metaObjective?: 'OUTCOME_ENGAGEMENT';
51044
+ /**
51045
+ * Meta only (facebook, instagram and Meta ads connections). Dry-runs the boost with Meta's
51046
+ * execution_options validate_only: the campaign, ad set, creative (the post reference) and ad
51047
+ * are checked as sent, everything PAUSED, and nothing is created or stored on Meta or in Zernio.
51048
+ * Returns 200 with the same body as a validateOnly POST /v1/ads/create (`validateOnly`, `results`
51049
+ * per node, `message`). Idempotency-Key storage and the duplicate-boost guard are bypassed. Counts
51050
+ * toward the 30 Meta writes per ad account per 5 minutes. With `adSetId` only the ad is dry-run.
51051
+ * An Instagram video that Meta refuses as a direct reference (subcode 1815279) comes back as
51052
+ * `unverified` nodes, because the copy a real boost makes cannot be dry-run.
51053
+ * `true` on any other platform returns 400 naming `validateOnly` and creates nothing; `false` is
51054
+ * ignored. `dryRun` is not a field: sending it returns 400 instead of creating the ad.
51055
+ *
51056
+ */
51057
+ validateOnly?: boolean;
51044
51058
  };
51045
51059
  headers?: {
51046
51060
  /**
@@ -51050,6 +51064,20 @@ type BoostPostData = {
51050
51064
  };
51051
51065
  };
51052
51066
  type BoostPostResponse = ({
51067
+ /**
51068
+ * Always true in a validate-only response.
51069
+ */
51070
+ validateOnly?: boolean;
51071
+ results?: Array<{
51072
+ node?: 'campaign' | 'adSet' | 'creative' | 'ad';
51073
+ status?: 'validated' | 'skipped' | 'unverified';
51074
+ /**
51075
+ * 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).
51076
+ */
51077
+ reason?: string;
51078
+ }>;
51079
+ message?: string;
51080
+ } | {
51053
51081
  ad?: Ad;
51054
51082
  message?: string;
51055
51083
  instagramVideoFallback?: InstagramVideoFallback;
package/dist/index.js CHANGED
@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
36
36
  // package.json
37
37
  var package_default = {
38
38
  name: "@getlatedev/node",
39
- version: "0.2.1346",
39
+ version: "0.2.1347",
40
40
  description: "The official Node.js library for the Zernio API",
41
41
  main: "dist/index.js",
42
42
  module: "dist/index.mjs",
package/dist/index.mjs CHANGED
@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
5
5
  // package.json
6
6
  var package_default = {
7
7
  name: "@getlatedev/node",
8
- version: "0.2.1346",
8
+ version: "0.2.1347",
9
9
  description: "The official Node.js library for the Zernio API",
10
10
  main: "dist/index.js",
11
11
  module: "dist/index.mjs",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@getlatedev/node",
3
- "version": "0.2.1346",
3
+ "version": "0.2.1347",
4
4
  "description": "The official Node.js library for the Zernio API",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
@@ -51985,6 +51985,20 @@ export type BoostPostData = {
51985
51985
  *
51986
51986
  */
51987
51987
  metaObjective?: 'OUTCOME_ENGAGEMENT';
51988
+ /**
51989
+ * Meta only (facebook, instagram and Meta ads connections). Dry-runs the boost with Meta's
51990
+ * execution_options validate_only: the campaign, ad set, creative (the post reference) and ad
51991
+ * are checked as sent, everything PAUSED, and nothing is created or stored on Meta or in Zernio.
51992
+ * Returns 200 with the same body as a validateOnly POST /v1/ads/create (`validateOnly`, `results`
51993
+ * per node, `message`). Idempotency-Key storage and the duplicate-boost guard are bypassed. Counts
51994
+ * toward the 30 Meta writes per ad account per 5 minutes. With `adSetId` only the ad is dry-run.
51995
+ * An Instagram video that Meta refuses as a direct reference (subcode 1815279) comes back as
51996
+ * `unverified` nodes, because the copy a real boost makes cannot be dry-run.
51997
+ * `true` on any other platform returns 400 naming `validateOnly` and creates nothing; `false` is
51998
+ * ignored. `dryRun` is not a field: sending it returns 400 instead of creating the ad.
51999
+ *
52000
+ */
52001
+ validateOnly?: boolean;
51988
52002
  };
51989
52003
  headers?: {
51990
52004
  /**
@@ -51995,6 +52009,20 @@ export type BoostPostData = {
51995
52009
  };
51996
52010
 
51997
52011
  export type BoostPostResponse = ({
52012
+ /**
52013
+ * Always true in a validate-only response.
52014
+ */
52015
+ validateOnly?: boolean;
52016
+ results?: Array<{
52017
+ node?: 'campaign' | 'adSet' | 'creative' | 'ad';
52018
+ status?: 'validated' | 'skipped' | 'unverified';
52019
+ /**
52020
+ * 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).
52021
+ */
52022
+ reason?: string;
52023
+ }>;
52024
+ message?: string;
52025
+ } | {
51998
52026
  ad?: Ad;
51999
52027
  message?: string;
52000
52028
  instagramVideoFallback?: InstagramVideoFallback;