@getlatedev/node 0.2.1376 → 0.2.1377

package/dist/index.d.mts

@@ -57935,9 +57935,31 @@ type EstimateAdReachData = {
          */
         adAccountId: string;
         /**
-         * The targeting spec to estimate. Same shape used by POST /v1/ads/create.
+         * The targeting spec to estimate. Same shape used by POST /v1/ads/create. Required unless `rawTargeting` is sent; with `rawTargeting` it can be omitted or minimal.
          */
-        spec: (TargetingSpec);
+        spec?: (TargetingSpec);
+        /**
+         * Meta only. A Meta-native targeting spec (snake_case: `geo_locations`, `age_min`,
+         * `flexible_spec`, `excluded_custom_audiences`, `user_os`, ...), the same field
+         * `POST /v1/ads/create` accepts, so the estimate covers the exact audience the ad
+         * set will use. For layered targeting, send `flexible_spec` here: entries AND
+         * together, ids inside one entry OR.
+         *
+         * It uses the same merge rules as `POST /v1/ads/create`: rawTargeting is the BASE
+         * layer and `spec`, converted to Meta's wire shape, is merged on top key by key,
+         * with `spec` winning on collision. The merge goes one level deep inside
+         * `geo_locations` and `excluded_geo_locations` (spec sub-keys win, raw-only
+         * sub-keys such as `location_types` survive). Array values (`flexible_spec`, ...)
+         * are replaced as a whole key when `spec` builds them, never element-merged, so
+         * `spec.interests` or `spec.behaviors` replace a raw `flexible_spec`. The result is
+         * sent to Meta `delivery_estimate` as `targeting_spec`.
+         *
+         * Sending it for an account on another platform returns 400 naming `rawTargeting`.
+         *
+         */
+        rawTargeting?: {
+            [key: string]: unknown;
+        };
         /**
          * Optional. The optimization goal the estimate should assume (platform's
          * own vocabulary, e.g. Meta `REACH`, `LINK_CLICKS`, `OFFSITE_CONVERSIONS`).

package/dist/index.d.ts

@@ -57935,9 +57935,31 @@ type EstimateAdReachData = {
          */
         adAccountId: string;
         /**
-         * The targeting spec to estimate. Same shape used by POST /v1/ads/create.
+         * The targeting spec to estimate. Same shape used by POST /v1/ads/create. Required unless `rawTargeting` is sent; with `rawTargeting` it can be omitted or minimal.
          */
-        spec: (TargetingSpec);
+        spec?: (TargetingSpec);
+        /**
+         * Meta only. A Meta-native targeting spec (snake_case: `geo_locations`, `age_min`,
+         * `flexible_spec`, `excluded_custom_audiences`, `user_os`, ...), the same field
+         * `POST /v1/ads/create` accepts, so the estimate covers the exact audience the ad
+         * set will use. For layered targeting, send `flexible_spec` here: entries AND
+         * together, ids inside one entry OR.
+         *
+         * It uses the same merge rules as `POST /v1/ads/create`: rawTargeting is the BASE
+         * layer and `spec`, converted to Meta's wire shape, is merged on top key by key,
+         * with `spec` winning on collision. The merge goes one level deep inside
+         * `geo_locations` and `excluded_geo_locations` (spec sub-keys win, raw-only
+         * sub-keys such as `location_types` survive). Array values (`flexible_spec`, ...)
+         * are replaced as a whole key when `spec` builds them, never element-merged, so
+         * `spec.interests` or `spec.behaviors` replace a raw `flexible_spec`. The result is
+         * sent to Meta `delivery_estimate` as `targeting_spec`.
+         *
+         * Sending it for an account on another platform returns 400 naming `rawTargeting`.
+         *
+         */
+        rawTargeting?: {
+            [key: string]: unknown;
+        };
         /**
          * Optional. The optimization goal the estimate should assume (platform's
          * own vocabulary, e.g. Meta `REACH`, `LINK_CLICKS`, `OFFSITE_CONVERSIONS`).

package/dist/index.js

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

package/src/generated/types.gen.ts

@@ -59162,9 +59162,31 @@ export type EstimateAdReachData = {
          */
         adAccountId: string;
         /**
-         * The targeting spec to estimate. Same shape used by POST /v1/ads/create.
+         * The targeting spec to estimate. Same shape used by POST /v1/ads/create. Required unless `rawTargeting` is sent; with `rawTargeting` it can be omitted or minimal.
          */
-        spec: (TargetingSpec);
+        spec?: (TargetingSpec);
+        /**
+         * Meta only. A Meta-native targeting spec (snake_case: `geo_locations`, `age_min`,
+         * `flexible_spec`, `excluded_custom_audiences`, `user_os`, ...), the same field
+         * `POST /v1/ads/create` accepts, so the estimate covers the exact audience the ad
+         * set will use. For layered targeting, send `flexible_spec` here: entries AND
+         * together, ids inside one entry OR.
+         *
+         * It uses the same merge rules as `POST /v1/ads/create`: rawTargeting is the BASE
+         * layer and `spec`, converted to Meta's wire shape, is merged on top key by key,
+         * with `spec` winning on collision. The merge goes one level deep inside
+         * `geo_locations` and `excluded_geo_locations` (spec sub-keys win, raw-only
+         * sub-keys such as `location_types` survive). Array values (`flexible_spec`, ...)
+         * are replaced as a whole key when `spec` builds them, never element-merged, so
+         * `spec.interests` or `spec.behaviors` replace a raw `flexible_spec`. The result is
+         * sent to Meta `delivery_estimate` as `targeting_spec`.
+         *
+         * Sending it for an account on another platform returns 400 naming `rawTargeting`.
+         *
+         */
+        rawTargeting?: {
+            [key: string]: unknown;
+        };
         /**
          * Optional. The optimization goal the estimate should assume (platform's
          * own vocabulary, e.g. Meta `REACH`, `LINK_CLICKS`, `OFFSITE_CONVERSIONS`).