@getlatedev/node 0.2.1095 → 0.2.1097

package/dist/index.d.mts

@@ -6961,6 +6961,16 @@ type ErrorResponse = {
      * create with a 5xx or dropped the connection and Zernio could not confirm
      * whether the object exists: check that parent before creating it again.
      *
+     * When Meta refuses a write because the ad account's status is ineligible to manage
+     * ads (Meta subcode 2490592 or 4841021, on the write itself or on a cleanup delete),
+     * any Meta ads write (create, boost, CTWA, campaign / ad set / ad updates and status
+     * changes) answers 422 `ad_account_unusable`. The message names the ad account when
+     * known, links Meta's fix (https://www.facebook.com/business/help/422289316306981),
+     * lists the objects left behind and ends with Meta's original error, which also stays
+     * verbatim in `platformError`. Meta often reports the first failure under an
+     * unrelated code (e.g. 1487194 on the creative), so branch on `code`, not on
+     * `platformError`.
+     *
      */
     details?: {
         /**
@@ -44791,9 +44801,29 @@ type BoostPostData = {
          */
         leadGenFormId?: string;
         /**
-         * Publish state of the created entities, on every platform. Omitted or ACTIVE publishes live (default); PAUSED pauses only the top-most object this boost creates and switches everything below it on: a new campaign is held paused with its ad set and ad on (one PUT /v1/ads/campaigns/{campaignId}/status with `active` brings it live); into an existing campaign (TikTok `existingCampaignId`) the new ad set is held paused; attached to an existing ad set (`adSetId`) the new ad itself is paused. On LinkedIn the held campaign group is PAUSED, its campaign and creative ACTIVE. X has no per-ad switch, so its lowest level is the line item.
+         * Publish state of the created entities, on every platform. Omitted or ACTIVE publishes live (default); PAUSED pauses only the top-most object this boost creates and switches everything below it on: a new campaign is held paused with its ad set and ad on (one PUT /v1/ads/campaigns/{campaignId}/status with `active` brings it live); into an existing campaign (TikTok `existingCampaignId`) the new ad set is held paused; attached to an existing ad set (`adSetId`) the new ad itself is paused. On LinkedIn the held campaign group is PAUSED, its campaign and creative ACTIVE. X has no per-ad switch, so its lowest level is the line item. `campaignStatus`, `adSetStatus` and `adStatus` set one level each and always win for that level; `status: PAUSED` adds a hold of its own only when none of them is PAUSED. To create every object paused, send all three as PAUSED.
          */
         status?: 'ACTIVE' | 'PAUSED';
+        /**
+         * Every platform, same semantics as POST /v1/ads/create. Sets the switch of the new campaign alone (LinkedIn: the campaign group) and overrides `status` for it. `ACTIVE` with `status: PAUSED` switches the campaign on and holds the new ad set paused (its ad on). Omitted, it follows `status`. Rejected with a 400 alongside `adSetId` or `existingCampaignId`, where no campaign is created (change an existing one with PUT /v1/ads/campaigns/{campaignId}/status).
+         */
+        campaignStatus?: 'ACTIVE' | 'PAUSED';
+        /**
+         * Every platform, same semantics as POST /v1/ads/create. Sets the switch of the new ad set alone (Google, TikTok and Pinterest: the ad group; LinkedIn: the campaign, which stays DRAFT when held; X: the line item) and overrides `status` for it. Omitted, it follows `status`.
+         *
+         * Precedence: a level status (`campaignStatus`, `adSetStatus`, `adStatus`) always wins for its level. `status: PAUSED` then holds the top-most new object that has no level status, and only when no level status is PAUSED; every other new object is switched on. So `campaignStatus: ACTIVE` + `adSetStatus: PAUSED` + `adStatus: PAUSED` keeps the campaign on with the new ad set and ad off, and all three PAUSED create the whole tree paused.
+         *
+         * Rejected with a 400 alongside `adSetId` (that ad set already exists; change it with PUT /v1/ads/ad-sets/{adSetId}/status).
+         *
+         */
+        adSetStatus?: 'ACTIVE' | 'PAUSED';
+        /**
+         * Sets the switch of the new ad alone, also when attaching to an existing ad set with `adSetId` (Meta, TikTok Smart+), and overrides `status` for it. Same precedence as `adSetStatus`. Omitted, it follows `status`.
+         *
+         * X returns a 400: a promoted post has no switch of its own, so hold the line item with `adSetStatus`.
+         *
+         */
+        adStatus?: AdActivationStatus;
         /**
          * Meta only, same semantics as POST /v1/ads/create: campaign = Advantage campaign budget (CBO), the budget and bid strategy sit on the campaign and the ad set inherits them. Default adset. Not allowed with adSetId.
          */

package/dist/index.d.ts

@@ -6961,6 +6961,16 @@ type ErrorResponse = {
      * create with a 5xx or dropped the connection and Zernio could not confirm
      * whether the object exists: check that parent before creating it again.
      *
+     * When Meta refuses a write because the ad account's status is ineligible to manage
+     * ads (Meta subcode 2490592 or 4841021, on the write itself or on a cleanup delete),
+     * any Meta ads write (create, boost, CTWA, campaign / ad set / ad updates and status
+     * changes) answers 422 `ad_account_unusable`. The message names the ad account when
+     * known, links Meta's fix (https://www.facebook.com/business/help/422289316306981),
+     * lists the objects left behind and ends with Meta's original error, which also stays
+     * verbatim in `platformError`. Meta often reports the first failure under an
+     * unrelated code (e.g. 1487194 on the creative), so branch on `code`, not on
+     * `platformError`.
+     *
      */
     details?: {
         /**
@@ -44791,9 +44801,29 @@ type BoostPostData = {
          */
         leadGenFormId?: string;
         /**
-         * Publish state of the created entities, on every platform. Omitted or ACTIVE publishes live (default); PAUSED pauses only the top-most object this boost creates and switches everything below it on: a new campaign is held paused with its ad set and ad on (one PUT /v1/ads/campaigns/{campaignId}/status with `active` brings it live); into an existing campaign (TikTok `existingCampaignId`) the new ad set is held paused; attached to an existing ad set (`adSetId`) the new ad itself is paused. On LinkedIn the held campaign group is PAUSED, its campaign and creative ACTIVE. X has no per-ad switch, so its lowest level is the line item.
+         * Publish state of the created entities, on every platform. Omitted or ACTIVE publishes live (default); PAUSED pauses only the top-most object this boost creates and switches everything below it on: a new campaign is held paused with its ad set and ad on (one PUT /v1/ads/campaigns/{campaignId}/status with `active` brings it live); into an existing campaign (TikTok `existingCampaignId`) the new ad set is held paused; attached to an existing ad set (`adSetId`) the new ad itself is paused. On LinkedIn the held campaign group is PAUSED, its campaign and creative ACTIVE. X has no per-ad switch, so its lowest level is the line item. `campaignStatus`, `adSetStatus` and `adStatus` set one level each and always win for that level; `status: PAUSED` adds a hold of its own only when none of them is PAUSED. To create every object paused, send all three as PAUSED.
          */
         status?: 'ACTIVE' | 'PAUSED';
+        /**
+         * Every platform, same semantics as POST /v1/ads/create. Sets the switch of the new campaign alone (LinkedIn: the campaign group) and overrides `status` for it. `ACTIVE` with `status: PAUSED` switches the campaign on and holds the new ad set paused (its ad on). Omitted, it follows `status`. Rejected with a 400 alongside `adSetId` or `existingCampaignId`, where no campaign is created (change an existing one with PUT /v1/ads/campaigns/{campaignId}/status).
+         */
+        campaignStatus?: 'ACTIVE' | 'PAUSED';
+        /**
+         * Every platform, same semantics as POST /v1/ads/create. Sets the switch of the new ad set alone (Google, TikTok and Pinterest: the ad group; LinkedIn: the campaign, which stays DRAFT when held; X: the line item) and overrides `status` for it. Omitted, it follows `status`.
+         *
+         * Precedence: a level status (`campaignStatus`, `adSetStatus`, `adStatus`) always wins for its level. `status: PAUSED` then holds the top-most new object that has no level status, and only when no level status is PAUSED; every other new object is switched on. So `campaignStatus: ACTIVE` + `adSetStatus: PAUSED` + `adStatus: PAUSED` keeps the campaign on with the new ad set and ad off, and all three PAUSED create the whole tree paused.
+         *
+         * Rejected with a 400 alongside `adSetId` (that ad set already exists; change it with PUT /v1/ads/ad-sets/{adSetId}/status).
+         *
+         */
+        adSetStatus?: 'ACTIVE' | 'PAUSED';
+        /**
+         * Sets the switch of the new ad alone, also when attaching to an existing ad set with `adSetId` (Meta, TikTok Smart+), and overrides `status` for it. Same precedence as `adSetStatus`. Omitted, it follows `status`.
+         *
+         * X returns a 400: a promoted post has no switch of its own, so hold the line item with `adSetStatus`.
+         *
+         */
+        adStatus?: AdActivationStatus;
         /**
          * Meta only, same semantics as POST /v1/ads/create: campaign = Advantage campaign budget (CBO), the budget and bid strategy sit on the campaign and the ad set inherits them. Default adset. Not allowed with adSetId.
          */

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -10228,7 +10228,10 @@ export const updateAd = <ThrowOnError extends boolean = false>(options: OptionsL
 
 /**
  * Cancel an ad
- * Cancels the ad on the platform and marks it as cancelled in the database. The ad is preserved for history. OpenAI Ads has no delete API; the ad is archived instead (a terminal state, the closest equivalent).
+ * Deletes the ad on the platform and marks it as cancelled in the database. The ad is preserved for history. OpenAI Ads has no delete API; the ad is archived instead (a terminal state, the closest equivalent).
+ *
+ * Only the ad is deleted; a campaign or ad set is never deleted while it still holds another ad. On Meta, when the ad set and campaign were created by Zernio (by `POST /v1/ads/create` or `POST /v1/ads/boost`) and Meta lists no other ad in the ad set (archived ads count), the emptied ad set is deleted too, then the campaign once it holds no other ad set. Parents created outside Zernio, and the parents of an ad imported from the platform, are always kept. To delete a whole campaign on purpose use `DELETE /v1/ads/campaigns/{campaignId}`.
+ *
  */
 export const deleteAd = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<DeleteAdData, ThrowOnError>) => {
     return (options?.client ?? client).delete<DeleteAdResponse, DeleteAdError, ThrowOnError>({

package/src/generated/types.gen.ts

@@ -5183,6 +5183,16 @@ export type ErrorResponse = {
      * create with a 5xx or dropped the connection and Zernio could not confirm
      * whether the object exists: check that parent before creating it again.
      *
+     * When Meta refuses a write because the ad account's status is ineligible to manage
+     * ads (Meta subcode 2490592 or 4841021, on the write itself or on a cleanup delete),
+     * any Meta ads write (create, boost, CTWA, campaign / ad set / ad updates and status
+     * changes) answers 422 `ad_account_unusable`. The message names the ad account when
+     * known, links Meta's fix (https://www.facebook.com/business/help/422289316306981),
+     * lists the objects left behind and ends with Meta's original error, which also stays
+     * verbatim in `platformError`. Meta often reports the first failure under an
+     * unrelated code (e.g. 1487194 on the creative), so branch on `code`, not on
+     * `platformError`.
+     *
      */
     details?: {
         /**
@@ -45510,9 +45520,29 @@ export type BoostPostData = {
          */
         leadGenFormId?: string;
         /**
-         * Publish state of the created entities, on every platform. Omitted or ACTIVE publishes live (default); PAUSED pauses only the top-most object this boost creates and switches everything below it on: a new campaign is held paused with its ad set and ad on (one PUT /v1/ads/campaigns/{campaignId}/status with `active` brings it live); into an existing campaign (TikTok `existingCampaignId`) the new ad set is held paused; attached to an existing ad set (`adSetId`) the new ad itself is paused. On LinkedIn the held campaign group is PAUSED, its campaign and creative ACTIVE. X has no per-ad switch, so its lowest level is the line item.
+         * Publish state of the created entities, on every platform. Omitted or ACTIVE publishes live (default); PAUSED pauses only the top-most object this boost creates and switches everything below it on: a new campaign is held paused with its ad set and ad on (one PUT /v1/ads/campaigns/{campaignId}/status with `active` brings it live); into an existing campaign (TikTok `existingCampaignId`) the new ad set is held paused; attached to an existing ad set (`adSetId`) the new ad itself is paused. On LinkedIn the held campaign group is PAUSED, its campaign and creative ACTIVE. X has no per-ad switch, so its lowest level is the line item. `campaignStatus`, `adSetStatus` and `adStatus` set one level each and always win for that level; `status: PAUSED` adds a hold of its own only when none of them is PAUSED. To create every object paused, send all three as PAUSED.
          */
         status?: 'ACTIVE' | 'PAUSED';
+        /**
+         * Every platform, same semantics as POST /v1/ads/create. Sets the switch of the new campaign alone (LinkedIn: the campaign group) and overrides `status` for it. `ACTIVE` with `status: PAUSED` switches the campaign on and holds the new ad set paused (its ad on). Omitted, it follows `status`. Rejected with a 400 alongside `adSetId` or `existingCampaignId`, where no campaign is created (change an existing one with PUT /v1/ads/campaigns/{campaignId}/status).
+         */
+        campaignStatus?: 'ACTIVE' | 'PAUSED';
+        /**
+         * Every platform, same semantics as POST /v1/ads/create. Sets the switch of the new ad set alone (Google, TikTok and Pinterest: the ad group; LinkedIn: the campaign, which stays DRAFT when held; X: the line item) and overrides `status` for it. Omitted, it follows `status`.
+         *
+         * Precedence: a level status (`campaignStatus`, `adSetStatus`, `adStatus`) always wins for its level. `status: PAUSED` then holds the top-most new object that has no level status, and only when no level status is PAUSED; every other new object is switched on. So `campaignStatus: ACTIVE` + `adSetStatus: PAUSED` + `adStatus: PAUSED` keeps the campaign on with the new ad set and ad off, and all three PAUSED create the whole tree paused.
+         *
+         * Rejected with a 400 alongside `adSetId` (that ad set already exists; change it with PUT /v1/ads/ad-sets/{adSetId}/status).
+         *
+         */
+        adSetStatus?: 'ACTIVE' | 'PAUSED';
+        /**
+         * Sets the switch of the new ad alone, also when attaching to an existing ad set with `adSetId` (Meta, TikTok Smart+), and overrides `status` for it. Same precedence as `adSetStatus`. Omitted, it follows `status`.
+         *
+         * X returns a 400: a promoted post has no switch of its own, so hold the line item with `adSetStatus`.
+         *
+         */
+        adStatus?: AdActivationStatus;
         /**
          * Meta only, same semantics as POST /v1/ads/create: campaign = Advantage campaign budget (CBO), the budget and bid strategy sit on the campaign and the ad set inherits them. Default adset. Not allowed with adSetId.
          */