@getlatedev/node 0.2.1342 → 0.2.1344

package/dist/index.d.mts

@@ -8491,6 +8491,16 @@ type ErrorResponse = {
      * unrelated code (e.g. 1487194 on the creative), so branch on `code`, not on
      * `platformError`.
      *
+     * When Meta refuses a write because the Facebook user behind the connection's token
+     * lacks the Advertise permission on the ad account (Meta subcode 2490585, 2490591 or 4841020 on
+     * the write, or a code 200 refusal such as 1487194 whose cleanup deletes Meta refused
+     * with 2490591 or 4841020), any Meta ads write answers 403 `insufficient_permissions`.
+     * Meta may still accept the campaign and ad set and refuse only the ad. The message
+     * names the ad account, asks for the Advertise or Manage permission on it (or a token
+     * granted `ads_management`, by reconnecting), lists the objects left behind and ends
+     * with Meta's `error_user_title`, `error_user_msg` and subcode; the raw error stays in
+     * `platformError`.
+     *
      */
     details?: {
         /**
@@ -50998,10 +51008,20 @@ type BoostPostData = {
          * with the objective Meta derives from `goal`, not with the objective used
          * by `POST /v1/ads/create` for the same `goal` name: boost maps `goal:
          * "engagement"` to objective `OUTCOME_AWARENESS`, which accepts
-         * `REACH`, `IMPRESSIONS`, `AD_RECALL_LIFT`, or THRUPLAY-class values, and
-         * rejects `POST_ENGAGEMENT` (that value is only valid under
-         * `OUTCOME_ENGAGEMENT`, which create uses for the same goal name, and
-         * which `metaObjective` selects on a boost).
+         * `REACH`, `IMPRESSIONS`, `AD_RECALL_LIFT`, or THRUPLAY-class values.
+         * `POST_ENGAGEMENT` with `goal: engagement` opts the boost into objective
+         * `OUTCOME_ENGAGEMENT` with `destination_type` `ON_POST`, exactly as
+         * `metaObjective: OUTCOME_ENGAGEMENT` does (sending both is the same request).
+         * `POST_ENGAGEMENT` returns 400 with any other `goal`, with `leadGenFormId`, or
+         * with a `CALL_NOW` or messaging `callToAction`. With `adSetId` the ad joins an
+         * existing ad set and `optimizationGoal` is not read. Under
+         * `OUTCOME_ENGAGEMENT` the ad runs on the post itself, so `destinationType`
+         * is a 400 (messaging CTAs excepted) and `optimizationGoal` must be
+         * `POST_ENGAGEMENT` or `REACH`; anything else is a 400 (Meta no longer
+         * offers `IMPRESSIONS` there, while a plain engagement boost on
+         * `OUTCOME_AWARENESS` still accepts it). The created ad reports the objective
+         * and optimization goal Meta runs it with in `platformObjective` and
+         * `optimizationGoal` (on `adSetId`, those of the existing ad set).
          *
          */
         optimizationGoal?: string;
@@ -51009,10 +51029,12 @@ type BoostPostData = {
          * Meta only, with `goal: engagement` and without `adSetId` (400 otherwise).
          * `OUTCOME_ENGAGEMENT` creates the campaign with objective `OUTCOME_ENGAGEMENT`
          * and the ad set with `optimization_goal` `POST_ENGAGEMENT` (unless
-         * `optimizationGoal` is set) and `destination_type` `ON_POST` (unless
-         * `destinationType` is set), the shape Ads Manager uses to boost an existing
-         * post. When omitted, an engagement boost keeps `OUTCOME_AWARENESS` with
-         * `REACH`. Returns 400 with `leadGenFormId` or with a `callToAction` whose objective
+         * `optimizationGoal` is set) and `destination_type` `ON_POST`, the shape Ads
+         * Manager uses to boost an existing post. `optimizationGoal: POST_ENGAGEMENT`
+         * selects the same objective, so the two may be sent together. `destinationType`
+         * returns 400 (messaging CTAs excepted) and `optimizationGoal` must be
+         * `POST_ENGAGEMENT` or `REACH` (400 otherwise). When both are
+         * omitted, an engagement boost keeps `OUTCOME_AWARENESS` with `REACH`. Returns 400 with `leadGenFormId` or with a `callToAction` whose objective
          * is not `OUTCOME_ENGAGEMENT` (`CALL_NOW`); messaging CTAs keep their own
          * `CONVERSATIONS` ad set. Verified against Meta on Facebook posts; Instagram posts
          * are accepted but not yet verified.

package/dist/index.d.ts

@@ -8491,6 +8491,16 @@ type ErrorResponse = {
      * unrelated code (e.g. 1487194 on the creative), so branch on `code`, not on
      * `platformError`.
      *
+     * When Meta refuses a write because the Facebook user behind the connection's token
+     * lacks the Advertise permission on the ad account (Meta subcode 2490585, 2490591 or 4841020 on
+     * the write, or a code 200 refusal such as 1487194 whose cleanup deletes Meta refused
+     * with 2490591 or 4841020), any Meta ads write answers 403 `insufficient_permissions`.
+     * Meta may still accept the campaign and ad set and refuse only the ad. The message
+     * names the ad account, asks for the Advertise or Manage permission on it (or a token
+     * granted `ads_management`, by reconnecting), lists the objects left behind and ends
+     * with Meta's `error_user_title`, `error_user_msg` and subcode; the raw error stays in
+     * `platformError`.
+     *
      */
     details?: {
         /**
@@ -50998,10 +51008,20 @@ type BoostPostData = {
          * with the objective Meta derives from `goal`, not with the objective used
          * by `POST /v1/ads/create` for the same `goal` name: boost maps `goal:
          * "engagement"` to objective `OUTCOME_AWARENESS`, which accepts
-         * `REACH`, `IMPRESSIONS`, `AD_RECALL_LIFT`, or THRUPLAY-class values, and
-         * rejects `POST_ENGAGEMENT` (that value is only valid under
-         * `OUTCOME_ENGAGEMENT`, which create uses for the same goal name, and
-         * which `metaObjective` selects on a boost).
+         * `REACH`, `IMPRESSIONS`, `AD_RECALL_LIFT`, or THRUPLAY-class values.
+         * `POST_ENGAGEMENT` with `goal: engagement` opts the boost into objective
+         * `OUTCOME_ENGAGEMENT` with `destination_type` `ON_POST`, exactly as
+         * `metaObjective: OUTCOME_ENGAGEMENT` does (sending both is the same request).
+         * `POST_ENGAGEMENT` returns 400 with any other `goal`, with `leadGenFormId`, or
+         * with a `CALL_NOW` or messaging `callToAction`. With `adSetId` the ad joins an
+         * existing ad set and `optimizationGoal` is not read. Under
+         * `OUTCOME_ENGAGEMENT` the ad runs on the post itself, so `destinationType`
+         * is a 400 (messaging CTAs excepted) and `optimizationGoal` must be
+         * `POST_ENGAGEMENT` or `REACH`; anything else is a 400 (Meta no longer
+         * offers `IMPRESSIONS` there, while a plain engagement boost on
+         * `OUTCOME_AWARENESS` still accepts it). The created ad reports the objective
+         * and optimization goal Meta runs it with in `platformObjective` and
+         * `optimizationGoal` (on `adSetId`, those of the existing ad set).
          *
          */
         optimizationGoal?: string;
@@ -51009,10 +51029,12 @@ type BoostPostData = {
          * Meta only, with `goal: engagement` and without `adSetId` (400 otherwise).
          * `OUTCOME_ENGAGEMENT` creates the campaign with objective `OUTCOME_ENGAGEMENT`
          * and the ad set with `optimization_goal` `POST_ENGAGEMENT` (unless
-         * `optimizationGoal` is set) and `destination_type` `ON_POST` (unless
-         * `destinationType` is set), the shape Ads Manager uses to boost an existing
-         * post. When omitted, an engagement boost keeps `OUTCOME_AWARENESS` with
-         * `REACH`. Returns 400 with `leadGenFormId` or with a `callToAction` whose objective
+         * `optimizationGoal` is set) and `destination_type` `ON_POST`, the shape Ads
+         * Manager uses to boost an existing post. `optimizationGoal: POST_ENGAGEMENT`
+         * selects the same objective, so the two may be sent together. `destinationType`
+         * returns 400 (messaging CTAs excepted) and `optimizationGoal` must be
+         * `POST_ENGAGEMENT` or `REACH` (400 otherwise). When both are
+         * omitted, an engagement boost keeps `OUTCOME_AWARENESS` with `REACH`. Returns 400 with `leadGenFormId` or with a `callToAction` whose objective
          * is not `OUTCOME_ENGAGEMENT` (`CALL_NOW`); messaging CTAs keep their own
          * `CONVERSATIONS` ad set. Verified against Meta on Facebook posts; Instagram posts
          * are accepted but not yet verified.

package/dist/index.js

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

package/src/generated/types.gen.ts

@@ -6643,6 +6643,16 @@ export type ErrorResponse = {
      * unrelated code (e.g. 1487194 on the creative), so branch on `code`, not on
      * `platformError`.
      *
+     * When Meta refuses a write because the Facebook user behind the connection's token
+     * lacks the Advertise permission on the ad account (Meta subcode 2490585, 2490591 or 4841020 on
+     * the write, or a code 200 refusal such as 1487194 whose cleanup deletes Meta refused
+     * with 2490591 or 4841020), any Meta ads write answers 403 `insufficient_permissions`.
+     * Meta may still accept the campaign and ad set and refuse only the ad. The message
+     * names the ad account, asks for the Advertise or Manage permission on it (or a token
+     * granted `ads_management`, by reconnecting), lists the objects left behind and ends
+     * with Meta's `error_user_title`, `error_user_msg` and subcode; the raw error stays in
+     * `platformError`.
+     *
      */
     details?: {
         /**
@@ -51942,10 +51952,20 @@ export type BoostPostData = {
          * with the objective Meta derives from `goal`, not with the objective used
          * by `POST /v1/ads/create` for the same `goal` name: boost maps `goal:
          * "engagement"` to objective `OUTCOME_AWARENESS`, which accepts
-         * `REACH`, `IMPRESSIONS`, `AD_RECALL_LIFT`, or THRUPLAY-class values, and
-         * rejects `POST_ENGAGEMENT` (that value is only valid under
-         * `OUTCOME_ENGAGEMENT`, which create uses for the same goal name, and
-         * which `metaObjective` selects on a boost).
+         * `REACH`, `IMPRESSIONS`, `AD_RECALL_LIFT`, or THRUPLAY-class values.
+         * `POST_ENGAGEMENT` with `goal: engagement` opts the boost into objective
+         * `OUTCOME_ENGAGEMENT` with `destination_type` `ON_POST`, exactly as
+         * `metaObjective: OUTCOME_ENGAGEMENT` does (sending both is the same request).
+         * `POST_ENGAGEMENT` returns 400 with any other `goal`, with `leadGenFormId`, or
+         * with a `CALL_NOW` or messaging `callToAction`. With `adSetId` the ad joins an
+         * existing ad set and `optimizationGoal` is not read. Under
+         * `OUTCOME_ENGAGEMENT` the ad runs on the post itself, so `destinationType`
+         * is a 400 (messaging CTAs excepted) and `optimizationGoal` must be
+         * `POST_ENGAGEMENT` or `REACH`; anything else is a 400 (Meta no longer
+         * offers `IMPRESSIONS` there, while a plain engagement boost on
+         * `OUTCOME_AWARENESS` still accepts it). The created ad reports the objective
+         * and optimization goal Meta runs it with in `platformObjective` and
+         * `optimizationGoal` (on `adSetId`, those of the existing ad set).
          *
          */
         optimizationGoal?: string;
@@ -51953,10 +51973,12 @@ export type BoostPostData = {
          * Meta only, with `goal: engagement` and without `adSetId` (400 otherwise).
          * `OUTCOME_ENGAGEMENT` creates the campaign with objective `OUTCOME_ENGAGEMENT`
          * and the ad set with `optimization_goal` `POST_ENGAGEMENT` (unless
-         * `optimizationGoal` is set) and `destination_type` `ON_POST` (unless
-         * `destinationType` is set), the shape Ads Manager uses to boost an existing
-         * post. When omitted, an engagement boost keeps `OUTCOME_AWARENESS` with
-         * `REACH`. Returns 400 with `leadGenFormId` or with a `callToAction` whose objective
+         * `optimizationGoal` is set) and `destination_type` `ON_POST`, the shape Ads
+         * Manager uses to boost an existing post. `optimizationGoal: POST_ENGAGEMENT`
+         * selects the same objective, so the two may be sent together. `destinationType`
+         * returns 400 (messaging CTAs excepted) and `optimizationGoal` must be
+         * `POST_ENGAGEMENT` or `REACH` (400 otherwise). When both are
+         * omitted, an engagement boost keeps `OUTCOME_AWARENESS` with `REACH`. Returns 400 with `leadGenFormId` or with a `callToAction` whose objective
          * is not `OUTCOME_ENGAGEMENT` (`CALL_NOW`); messaging CTAs keep their own
          * `CONVERSATIONS` ad set. Verified against Meta on Facebook posts; Instagram posts
          * are accepted but not yet verified.