@getlatedev/node 0.2.1218 → 0.2.1220

package/dist/index.d.mts

@@ -42272,6 +42272,44 @@ type UpdateAdSetData = {
              */
             interestsBehaviors?: boolean;
         };
+        /**
+         * Meta only (400 elsewhere). Manual placements, same object and enums as `placements` on
+         * POST /v1/ads/create. Sending an object REPLACES the ad set's current placement set
+         * (`publisher_platforms`, every `*_positions` list and `device_platforms`); a position
+         * list you leave out is removed. `null` removes every placement key so Meta returns to
+         * automatic (Advantage+) placements. Omit to leave placements untouched. Meta enforces
+         * co-selection rules (e.g. a position needs its publisher platform) and its error is
+         * returned as is. Meta may also reject `null` or a narrower set when an ad's creative
+         * uses per-placement asset customization (`placementAssets`). An object with no
+         * non-empty list is a 400 (send `null` instead). Cannot be combined with
+         * `targeting.placements` (400).
+         *
+         */
+        placements?: {
+            publisherPlatforms?: Array<('facebook' | 'instagram' | 'threads' | 'messenger' | 'audience_network' | 'whatsapp')>;
+            facebookPositions?: Array<('feed' | 'right_hand_column' | 'marketplace' | 'video_feeds' | 'story' | 'search' | 'instream_video' | 'facebook_reels' | 'facebook_reels_overlay' | 'profile_feed' | 'notification')>;
+            instagramPositions?: Array<('stream' | 'story' | 'explore' | 'explore_home' | 'reels' | 'profile_feed' | 'ig_search' | 'profile_reels')>;
+            messengerPositions?: Array<('messenger_home' | 'sponsored_messages' | 'story')>;
+            audienceNetworkPositions?: Array<('classic' | 'rewarded_video')>;
+            threadsPositions?: Array<('threads_stream')>;
+            whatsappPositions?: Array<('status')>;
+            devicePlatforms?: Array<('mobile' | 'desktop')>;
+        } | null;
+        /**
+         * Meta only (400 elsewhere). Targeting fields to change, same shape as the `targeting`
+         * object on POST /v1/ads/create. Only the keys you send change: Zernio reads the ad set's
+         * live targeting from Meta, merges these keys over it and writes the full spec back, so
+         * everything you do not send (custom audiences, geo, age, interest groups,
+         * `targeting_automation`) is kept. Setting any location replaces every location list.
+         * An empty list or `gender: all` clears that key. `incomeTier` is resolved to Meta's
+         * income segment first (422 when Meta has none). Fields Meta cannot target (LinkedIn
+         * B2B, Google `devices`, Reddit communities and keywords) return 400 with
+         * `param: targeting.<field>`. An empty object is a 400, and so is a
+         * `targeting.placements` object with no non-empty list (`param: targeting.placements`). When the live targeting cannot be
+         * read the request returns 502 and nothing is written.
+         *
+         */
+        targeting?: (TargetingSpec);
         /**
          * Bid cap in WHOLE currency units (USD: 5 = $5.00; JPY: 100 = ¥100). Required when
          * bidStrategy is LOWEST_COST_WITH_BID_CAP or COST_CAP. Internally converted to Meta's
@@ -42407,6 +42445,12 @@ type UpdateAdSetResponse = ({
     platformSpecificData?: {
         [key: string]: unknown;
     };
+    /**
+     * Present when `placements` or `targeting` was sent. The ad set's full Meta targeting as written (Meta snake_case). The same snake_case object is stored as the ad set's and its ads' `targeting`.
+     */
+    targeting?: {
+        [key: string]: unknown;
+    };
 });
 type UpdateAdSetError = (unknown | ErrorResponse);
 type DeleteAdSetData = {
@@ -48182,10 +48226,16 @@ type CreateStandaloneAdData = {
         pageId?: string;
         /**
          * Meta only. Override the Instagram account the ad is delivered as. Pass an Instagram
-         * Business Account ID (e.g. 17841...), mapped to the creative's `instagram_user_id`.
-         * When omitted we use the Instagram actor Meta already runs the Page's other ads as,
-         * falling back to the Page's page-backed Instagram account. Useful when a Page has more
-         * than one eligible IG account.
+         * Business Account ID (e.g. 17841...), mapped to the creative's `instagram_user_id`; it
+         * is sent as-is and never replaced. When omitted we use the Instagram account linked to
+         * the Page; formats that need an Instagram actor without one use the actor the Page's
+         * other ads already run as, then the Page's page-backed Instagram account. If Meta
+         * refuses that default because the ad account has no access to it (200/1815199), the
+         * creative is retried once with an Instagram account the ad account is authorized for;
+         * with none, the request fails with a 422 on `instagramAccountId` (list the usable
+         * accounts with GET /v1/ads/instagram-accounts). A creative replaced later through
+         * /v1/ads/{adId} follows the same rule. Useful when a Page has more than one eligible IG
+         * account.
          *
          */
         instagramAccountId?: string;

package/dist/index.d.ts

@@ -42272,6 +42272,44 @@ type UpdateAdSetData = {
              */
             interestsBehaviors?: boolean;
         };
+        /**
+         * Meta only (400 elsewhere). Manual placements, same object and enums as `placements` on
+         * POST /v1/ads/create. Sending an object REPLACES the ad set's current placement set
+         * (`publisher_platforms`, every `*_positions` list and `device_platforms`); a position
+         * list you leave out is removed. `null` removes every placement key so Meta returns to
+         * automatic (Advantage+) placements. Omit to leave placements untouched. Meta enforces
+         * co-selection rules (e.g. a position needs its publisher platform) and its error is
+         * returned as is. Meta may also reject `null` or a narrower set when an ad's creative
+         * uses per-placement asset customization (`placementAssets`). An object with no
+         * non-empty list is a 400 (send `null` instead). Cannot be combined with
+         * `targeting.placements` (400).
+         *
+         */
+        placements?: {
+            publisherPlatforms?: Array<('facebook' | 'instagram' | 'threads' | 'messenger' | 'audience_network' | 'whatsapp')>;
+            facebookPositions?: Array<('feed' | 'right_hand_column' | 'marketplace' | 'video_feeds' | 'story' | 'search' | 'instream_video' | 'facebook_reels' | 'facebook_reels_overlay' | 'profile_feed' | 'notification')>;
+            instagramPositions?: Array<('stream' | 'story' | 'explore' | 'explore_home' | 'reels' | 'profile_feed' | 'ig_search' | 'profile_reels')>;
+            messengerPositions?: Array<('messenger_home' | 'sponsored_messages' | 'story')>;
+            audienceNetworkPositions?: Array<('classic' | 'rewarded_video')>;
+            threadsPositions?: Array<('threads_stream')>;
+            whatsappPositions?: Array<('status')>;
+            devicePlatforms?: Array<('mobile' | 'desktop')>;
+        } | null;
+        /**
+         * Meta only (400 elsewhere). Targeting fields to change, same shape as the `targeting`
+         * object on POST /v1/ads/create. Only the keys you send change: Zernio reads the ad set's
+         * live targeting from Meta, merges these keys over it and writes the full spec back, so
+         * everything you do not send (custom audiences, geo, age, interest groups,
+         * `targeting_automation`) is kept. Setting any location replaces every location list.
+         * An empty list or `gender: all` clears that key. `incomeTier` is resolved to Meta's
+         * income segment first (422 when Meta has none). Fields Meta cannot target (LinkedIn
+         * B2B, Google `devices`, Reddit communities and keywords) return 400 with
+         * `param: targeting.<field>`. An empty object is a 400, and so is a
+         * `targeting.placements` object with no non-empty list (`param: targeting.placements`). When the live targeting cannot be
+         * read the request returns 502 and nothing is written.
+         *
+         */
+        targeting?: (TargetingSpec);
         /**
          * Bid cap in WHOLE currency units (USD: 5 = $5.00; JPY: 100 = ¥100). Required when
          * bidStrategy is LOWEST_COST_WITH_BID_CAP or COST_CAP. Internally converted to Meta's
@@ -42407,6 +42445,12 @@ type UpdateAdSetResponse = ({
     platformSpecificData?: {
         [key: string]: unknown;
     };
+    /**
+     * Present when `placements` or `targeting` was sent. The ad set's full Meta targeting as written (Meta snake_case). The same snake_case object is stored as the ad set's and its ads' `targeting`.
+     */
+    targeting?: {
+        [key: string]: unknown;
+    };
 });
 type UpdateAdSetError = (unknown | ErrorResponse);
 type DeleteAdSetData = {
@@ -48182,10 +48226,16 @@ type CreateStandaloneAdData = {
         pageId?: string;
         /**
          * Meta only. Override the Instagram account the ad is delivered as. Pass an Instagram
-         * Business Account ID (e.g. 17841...), mapped to the creative's `instagram_user_id`.
-         * When omitted we use the Instagram actor Meta already runs the Page's other ads as,
-         * falling back to the Page's page-backed Instagram account. Useful when a Page has more
-         * than one eligible IG account.
+         * Business Account ID (e.g. 17841...), mapped to the creative's `instagram_user_id`; it
+         * is sent as-is and never replaced. When omitted we use the Instagram account linked to
+         * the Page; formats that need an Instagram actor without one use the actor the Page's
+         * other ads already run as, then the Page's page-backed Instagram account. If Meta
+         * refuses that default because the ad account has no access to it (200/1815199), the
+         * creative is retried once with an Instagram account the ad account is authorized for;
+         * with none, the request fails with a 422 on `instagramAccountId` (list the usable
+         * accounts with GET /v1/ads/instagram-accounts). A creative replaced later through
+         * /v1/ads/{adId} follows the same rule. Useful when a Page has more than one eligible IG
+         * account.
          *
          */
         instagramAccountId?: string;

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -10540,6 +10540,17 @@ export const getAdSetDetails = <ThrowOnError extends boolean = false>(options: O
  * theirs, and `statusUpdated` / `statusSkipped` report whether that switch
  * was written or a live read showed it already in place.
  *
+ * Placements and targeting (Meta only): `placements` and `targeting` take the same shapes
+ * as POST /v1/ads/create. Meta replaces an ad set's targeting wholesale, so Zernio reads
+ * the live targeting first, changes only what the request names and writes the merged
+ * spec back: custom audiences, geo, age, interest groups and `targeting_automation` you do
+ * not send are kept. `placements` replaces the whole placement set, `placements: null`
+ * returns the ad set to automatic placements, and omitting it leaves placements as they
+ * are. Other platforms return 400 for either field before anything in the request is
+ * written (use PUT /v1/ads/{adId} with `targeting` where that platform supports it). The
+ * live read and the `incomeTier` lookup run before any other field is written, so a 502
+ * or 422 from them leaves the ad set unchanged.
+ *
  */
 export const updateAdSet = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<UpdateAdSetData, ThrowOnError>) => {
     return (options?.client ?? client).put<UpdateAdSetResponse, UpdateAdSetError, ThrowOnError>({

package/src/generated/types.gen.ts

@@ -42757,6 +42757,44 @@ export type UpdateAdSetData = {
              */
             interestsBehaviors?: boolean;
         };
+        /**
+         * Meta only (400 elsewhere). Manual placements, same object and enums as `placements` on
+         * POST /v1/ads/create. Sending an object REPLACES the ad set's current placement set
+         * (`publisher_platforms`, every `*_positions` list and `device_platforms`); a position
+         * list you leave out is removed. `null` removes every placement key so Meta returns to
+         * automatic (Advantage+) placements. Omit to leave placements untouched. Meta enforces
+         * co-selection rules (e.g. a position needs its publisher platform) and its error is
+         * returned as is. Meta may also reject `null` or a narrower set when an ad's creative
+         * uses per-placement asset customization (`placementAssets`). An object with no
+         * non-empty list is a 400 (send `null` instead). Cannot be combined with
+         * `targeting.placements` (400).
+         *
+         */
+        placements?: {
+            publisherPlatforms?: Array<('facebook' | 'instagram' | 'threads' | 'messenger' | 'audience_network' | 'whatsapp')>;
+            facebookPositions?: Array<('feed' | 'right_hand_column' | 'marketplace' | 'video_feeds' | 'story' | 'search' | 'instream_video' | 'facebook_reels' | 'facebook_reels_overlay' | 'profile_feed' | 'notification')>;
+            instagramPositions?: Array<('stream' | 'story' | 'explore' | 'explore_home' | 'reels' | 'profile_feed' | 'ig_search' | 'profile_reels')>;
+            messengerPositions?: Array<('messenger_home' | 'sponsored_messages' | 'story')>;
+            audienceNetworkPositions?: Array<('classic' | 'rewarded_video')>;
+            threadsPositions?: Array<('threads_stream')>;
+            whatsappPositions?: Array<('status')>;
+            devicePlatforms?: Array<('mobile' | 'desktop')>;
+        } | null;
+        /**
+         * Meta only (400 elsewhere). Targeting fields to change, same shape as the `targeting`
+         * object on POST /v1/ads/create. Only the keys you send change: Zernio reads the ad set's
+         * live targeting from Meta, merges these keys over it and writes the full spec back, so
+         * everything you do not send (custom audiences, geo, age, interest groups,
+         * `targeting_automation`) is kept. Setting any location replaces every location list.
+         * An empty list or `gender: all` clears that key. `incomeTier` is resolved to Meta's
+         * income segment first (422 when Meta has none). Fields Meta cannot target (LinkedIn
+         * B2B, Google `devices`, Reddit communities and keywords) return 400 with
+         * `param: targeting.<field>`. An empty object is a 400, and so is a
+         * `targeting.placements` object with no non-empty list (`param: targeting.placements`). When the live targeting cannot be
+         * read the request returns 502 and nothing is written.
+         *
+         */
+        targeting?: (TargetingSpec);
         /**
          * Bid cap in WHOLE currency units (USD: 5 = $5.00; JPY: 100 = ¥100). Required when
          * bidStrategy is LOWEST_COST_WITH_BID_CAP or COST_CAP. Internally converted to Meta's
@@ -42893,6 +42931,12 @@ export type UpdateAdSetResponse = ({
     platformSpecificData?: {
         [key: string]: unknown;
     };
+    /**
+     * Present when `placements` or `targeting` was sent. The ad set's full Meta targeting as written (Meta snake_case). The same snake_case object is stored as the ad set's and its ads' `targeting`.
+     */
+    targeting?: {
+        [key: string]: unknown;
+    };
 });
 
 export type UpdateAdSetError = (unknown | ErrorResponse);
@@ -49000,10 +49044,16 @@ export type CreateStandaloneAdData = {
         pageId?: string;
         /**
          * Meta only. Override the Instagram account the ad is delivered as. Pass an Instagram
-         * Business Account ID (e.g. 17841...), mapped to the creative's `instagram_user_id`.
-         * When omitted we use the Instagram actor Meta already runs the Page's other ads as,
-         * falling back to the Page's page-backed Instagram account. Useful when a Page has more
-         * than one eligible IG account.
+         * Business Account ID (e.g. 17841...), mapped to the creative's `instagram_user_id`; it
+         * is sent as-is and never replaced. When omitted we use the Instagram account linked to
+         * the Page; formats that need an Instagram actor without one use the actor the Page's
+         * other ads already run as, then the Page's page-backed Instagram account. If Meta
+         * refuses that default because the ad account has no access to it (200/1815199), the
+         * creative is retried once with an Instagram account the ad account is authorized for;
+         * with none, the request fails with a 422 on `instagramAccountId` (list the usable
+         * accounts with GET /v1/ads/instagram-accounts). A creative replaced later through
+         * /v1/ads/{adId} follows the same rule. Useful when a Page has more than one eligible IG
+         * account.
          *
          */
         instagramAccountId?: string;