@zernio/node 0.2.580 → 0.2.581

package/dist/index.d.mts

@@ -27453,18 +27453,21 @@ type UpdateAdCampaignStatusData = {
 };
 type UpdateAdCampaignStatusResponse = ({
     /**
-     * Number of ads updated
+     * The status written to the campaign
+     */
+    status?: 'active' | 'paused';
+    /**
+     * Number of ads whose own stored status changed too. 0 is normal on a resume whose ads are all awaiting the platform.
      */
     updated?: number;
     /**
-     * Number of ads skipped
+     * Number of ads whose own status was left as it was
      */
     skipped?: number;
-    skippedReasons?: Array<(string)>;
     /**
-     * Human-readable summary (present when no ads were actionable)
+     * Why each group of ads was skipped
      */
-    message?: string;
+    skippedReasons?: Array<(string)>;
 });
 type UpdateAdCampaignStatusError = (unknown | {
     error?: string;
@@ -27774,7 +27777,7 @@ type UpdateAdSetData = {
             type?: 'daily' | 'lifetime';
         };
         /**
-         * Omit if not toggling delivery state
+         * Writes the ad set's own on/off switch (Meta: `configured_status`) on Meta and LinkedIn, whatever delivery status its ads report. Omit if not toggling delivery state.
          */
         status?: 'active' | 'paused';
         /**
@@ -27879,9 +27882,26 @@ type UpdateAdSetData = {
 type UpdateAdSetResponse = ({
     budget?: AdBudget;
     budgetLevel?: 'adset';
+    /**
+     * The status written to the ad set. Absent when nothing was written (see statusMessage).
+     */
     status?: 'active' | 'paused';
+    /**
+     * Number of ads whose own stored status changed alongside the ad set switch
+     */
     statusUpdated?: number;
+    /**
+     * Number of ads whose own status was left as it was
+     */
     statusSkipped?: number;
+    /**
+     * Why each group of ads was skipped
+     */
+    statusSkippedReasons?: Array<(string)>;
+    /**
+     * Present only where the platform has no ad-set switch and no child ad was actionable; `status` is then absent because nothing was written
+     */
+    statusMessage?: string;
     bidStrategy?: BidStrategy;
     bidAmount?: (number) | null;
     roasAverageFloor?: (number) | null;
@@ -27905,8 +27925,26 @@ type UpdateAdSetStatusData = {
     };
 };
 type UpdateAdSetStatusResponse = ({
+    /**
+     * The status written to the ad set. Absent when nothing was written (see message).
+     */
+    status?: 'active' | 'paused';
+    /**
+     * Number of ads whose own stored status changed too. 0 is normal on a resume whose ads are all awaiting the platform.
+     */
     updated?: number;
+    /**
+     * Number of ads whose own status was left as it was
+     */
     skipped?: number;
+    /**
+     * Why each group of ads was skipped
+     */
+    skippedReasons?: Array<(string)>;
+    /**
+     * Present only where the platform has no ad-set switch and no child ad was actionable
+     */
+    message?: string;
 });
 type UpdateAdSetStatusError = (unknown | {
     error?: string;
@@ -30031,7 +30069,7 @@ type CreateStandaloneAdData = {
          */
         budgetType?: 'daily' | 'lifetime';
         /**
-         * Meta and TikTok. Publish state of the created entities. Omitted or ACTIVE publishes live (default, back-compat); PAUSED creates them paused and skips activation, so you can review before they spend. On TikTok the whole campaign > ad group > ad hierarchy stays paused.
+         * Meta and TikTok. Publish state of the created entities. Omitted or ACTIVE publishes live (default, back-compat); PAUSED creates them paused so you can review before they spend. On Meta the pause is held on the campaign this call creates, leaving the ad set and ad switched on, so a single PUT /v1/ads/campaigns/{campaignId}/status with `active` brings the whole thing live. It is held at every level instead when the pause cannot rely on the campaign: `existingCampaignId` (that campaign may be running and is never touched) or `campaignStatus: ACTIVE`. On TikTok the whole campaign > ad group > ad hierarchy stays paused.
          */
         status?: 'ACTIVE' | 'PAUSED';
         /**

package/dist/index.d.ts

@@ -27453,18 +27453,21 @@ type UpdateAdCampaignStatusData = {
 };
 type UpdateAdCampaignStatusResponse = ({
     /**
-     * Number of ads updated
+     * The status written to the campaign
+     */
+    status?: 'active' | 'paused';
+    /**
+     * Number of ads whose own stored status changed too. 0 is normal on a resume whose ads are all awaiting the platform.
      */
     updated?: number;
     /**
-     * Number of ads skipped
+     * Number of ads whose own status was left as it was
      */
     skipped?: number;
-    skippedReasons?: Array<(string)>;
     /**
-     * Human-readable summary (present when no ads were actionable)
+     * Why each group of ads was skipped
      */
-    message?: string;
+    skippedReasons?: Array<(string)>;
 });
 type UpdateAdCampaignStatusError = (unknown | {
     error?: string;
@@ -27774,7 +27777,7 @@ type UpdateAdSetData = {
             type?: 'daily' | 'lifetime';
         };
         /**
-         * Omit if not toggling delivery state
+         * Writes the ad set's own on/off switch (Meta: `configured_status`) on Meta and LinkedIn, whatever delivery status its ads report. Omit if not toggling delivery state.
          */
         status?: 'active' | 'paused';
         /**
@@ -27879,9 +27882,26 @@ type UpdateAdSetData = {
 type UpdateAdSetResponse = ({
     budget?: AdBudget;
     budgetLevel?: 'adset';
+    /**
+     * The status written to the ad set. Absent when nothing was written (see statusMessage).
+     */
     status?: 'active' | 'paused';
+    /**
+     * Number of ads whose own stored status changed alongside the ad set switch
+     */
     statusUpdated?: number;
+    /**
+     * Number of ads whose own status was left as it was
+     */
     statusSkipped?: number;
+    /**
+     * Why each group of ads was skipped
+     */
+    statusSkippedReasons?: Array<(string)>;
+    /**
+     * Present only where the platform has no ad-set switch and no child ad was actionable; `status` is then absent because nothing was written
+     */
+    statusMessage?: string;
     bidStrategy?: BidStrategy;
     bidAmount?: (number) | null;
     roasAverageFloor?: (number) | null;
@@ -27905,8 +27925,26 @@ type UpdateAdSetStatusData = {
     };
 };
 type UpdateAdSetStatusResponse = ({
+    /**
+     * The status written to the ad set. Absent when nothing was written (see message).
+     */
+    status?: 'active' | 'paused';
+    /**
+     * Number of ads whose own stored status changed too. 0 is normal on a resume whose ads are all awaiting the platform.
+     */
     updated?: number;
+    /**
+     * Number of ads whose own status was left as it was
+     */
     skipped?: number;
+    /**
+     * Why each group of ads was skipped
+     */
+    skippedReasons?: Array<(string)>;
+    /**
+     * Present only where the platform has no ad-set switch and no child ad was actionable
+     */
+    message?: string;
 });
 type UpdateAdSetStatusError = (unknown | {
     error?: string;
@@ -30031,7 +30069,7 @@ type CreateStandaloneAdData = {
          */
         budgetType?: 'daily' | 'lifetime';
         /**
-         * Meta and TikTok. Publish state of the created entities. Omitted or ACTIVE publishes live (default, back-compat); PAUSED creates them paused and skips activation, so you can review before they spend. On TikTok the whole campaign > ad group > ad hierarchy stays paused.
+         * Meta and TikTok. Publish state of the created entities. Omitted or ACTIVE publishes live (default, back-compat); PAUSED creates them paused so you can review before they spend. On Meta the pause is held on the campaign this call creates, leaving the ad set and ad switched on, so a single PUT /v1/ads/campaigns/{campaignId}/status with `active` brings the whole thing live. It is held at every level instead when the pause cannot rely on the campaign: `existingCampaignId` (that campaign may be running and is never touched) or `campaignStatus: ACTIVE`. On TikTok the whole campaign > ad group > ad hierarchy stays paused.
          */
         status?: 'ACTIVE' | 'PAUSED';
         /**

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -7109,8 +7109,20 @@ export const createAdCampaign = <ThrowOnError extends boolean = false>(options:
 
 /**
  * Pause or resume a campaign
- * Updates the status of all ads in a campaign. Makes one platform API call (not per-ad) since status cascades through the campaign hierarchy.
- * Ads in terminal statuses (rejected, completed, cancelled) are automatically skipped.
+ * Writes the campaign's own on/off switch, then lets the platform cascade delivery to its ad sets and ads.
+ * Makes one platform API call, not one per ad.
+ *
+ * The switch is always written, whatever delivery status the ads underneath report: an ad still in review
+ * does not block resuming its campaign. The echoed `status` is the confirmation that it landed.
+ *
+ * `updated` / `skipped` describe only the ads whose own stored status CHANGED alongside it, so
+ * `updated: 0` is a normal successful response, not a no-op. Ads are skipped when they are in a terminal
+ * status (rejected, completed, cancelled), already in the target state, or switched on but not yet
+ * delivering — the last group keeps its `pending_review` / `error` status until the platform reports what
+ * it became. `skippedReasons` names which case applies.
+ *
+ * On Meta this flips the campaign only. An ad set paused in its own right stays paused, so pair this with
+ * PUT /v1/ads/ad-sets/{adSetId}/status when you also need the ad set switched back on.
  *
  */
 export const updateAdCampaignStatus = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<UpdateAdCampaignStatusData, ThrowOnError>) => {
@@ -7328,6 +7340,23 @@ export const updateAdSet = <ThrowOnError extends boolean = false>(options: Optio
  * status toggle and prefer a symmetric URL to
  * /v1/ads/campaigns/{campaignId}/status.
  *
+ * On Meta and LinkedIn this writes the ad set's own on/off switch
+ * (Meta: `configured_status`), whatever delivery status its ads report —
+ * an ad still in review does not block resuming its ad set. The echoed
+ * `status` is the confirmation that it landed. Where the platform has no
+ * ad-set switch (TikTok and others) the toggle is emulated by flipping the
+ * child ads; a call with no actionable ad then writes nothing and returns a
+ * `message` with no `status`.
+ *
+ * `updated` / `skipped` describe only the ads whose own stored status
+ * CHANGED alongside the switch, so `updated: 0` is a normal successful
+ * response. See `skippedReasons` for which of the three cases applies
+ * (terminal, already in the target state, or switched on but not yet
+ * delivering).
+ *
+ * A campaign created paused needs its campaign resumed as well: pair this
+ * with PUT /v1/ads/campaigns/{campaignId}/status.
+ *
  */
 export const updateAdSetStatus = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<UpdateAdSetStatusData, ThrowOnError>) => {
     return (options?.client ?? client).put<UpdateAdSetStatusResponse, UpdateAdSetStatusError, ThrowOnError>({

package/src/generated/types.gen.ts

@@ -27826,18 +27826,21 @@ export type UpdateAdCampaignStatusData = {
 
 export type UpdateAdCampaignStatusResponse = ({
     /**
-     * Number of ads updated
+     * The status written to the campaign
+     */
+    status?: 'active' | 'paused';
+    /**
+     * Number of ads whose own stored status changed too. 0 is normal on a resume whose ads are all awaiting the platform.
      */
     updated?: number;
     /**
-     * Number of ads skipped
+     * Number of ads whose own status was left as it was
      */
     skipped?: number;
-    skippedReasons?: Array<(string)>;
     /**
-     * Human-readable summary (present when no ads were actionable)
+     * Why each group of ads was skipped
      */
-    message?: string;
+    skippedReasons?: Array<(string)>;
 });
 
 export type UpdateAdCampaignStatusError = (unknown | {
@@ -28170,7 +28173,7 @@ export type UpdateAdSetData = {
             type?: 'daily' | 'lifetime';
         };
         /**
-         * Omit if not toggling delivery state
+         * Writes the ad set's own on/off switch (Meta: `configured_status`) on Meta and LinkedIn, whatever delivery status its ads report. Omit if not toggling delivery state.
          */
         status?: 'active' | 'paused';
         /**
@@ -28276,9 +28279,26 @@ export type UpdateAdSetData = {
 export type UpdateAdSetResponse = ({
     budget?: AdBudget;
     budgetLevel?: 'adset';
+    /**
+     * The status written to the ad set. Absent when nothing was written (see statusMessage).
+     */
     status?: 'active' | 'paused';
+    /**
+     * Number of ads whose own stored status changed alongside the ad set switch
+     */
     statusUpdated?: number;
+    /**
+     * Number of ads whose own status was left as it was
+     */
     statusSkipped?: number;
+    /**
+     * Why each group of ads was skipped
+     */
+    statusSkippedReasons?: Array<(string)>;
+    /**
+     * Present only where the platform has no ad-set switch and no child ad was actionable; `status` is then absent because nothing was written
+     */
+    statusMessage?: string;
     bidStrategy?: BidStrategy;
     bidAmount?: (number) | null;
     roasAverageFloor?: (number) | null;
@@ -28305,8 +28325,26 @@ export type UpdateAdSetStatusData = {
 };
 
 export type UpdateAdSetStatusResponse = ({
+    /**
+     * The status written to the ad set. Absent when nothing was written (see message).
+     */
+    status?: 'active' | 'paused';
+    /**
+     * Number of ads whose own stored status changed too. 0 is normal on a resume whose ads are all awaiting the platform.
+     */
     updated?: number;
+    /**
+     * Number of ads whose own status was left as it was
+     */
     skipped?: number;
+    /**
+     * Why each group of ads was skipped
+     */
+    skippedReasons?: Array<(string)>;
+    /**
+     * Present only where the platform has no ad-set switch and no child ad was actionable
+     */
+    message?: string;
 });
 
 export type UpdateAdSetStatusError = (unknown | {
@@ -30568,7 +30606,7 @@ export type CreateStandaloneAdData = {
          */
         budgetType?: 'daily' | 'lifetime';
         /**
-         * Meta and TikTok. Publish state of the created entities. Omitted or ACTIVE publishes live (default, back-compat); PAUSED creates them paused and skips activation, so you can review before they spend. On TikTok the whole campaign > ad group > ad hierarchy stays paused.
+         * Meta and TikTok. Publish state of the created entities. Omitted or ACTIVE publishes live (default, back-compat); PAUSED creates them paused so you can review before they spend. On Meta the pause is held on the campaign this call creates, leaving the ad set and ad switched on, so a single PUT /v1/ads/campaigns/{campaignId}/status with `active` brings the whole thing live. It is held at every level instead when the pause cannot rely on the campaign: `existingCampaignId` (that campaign may be running and is never touched) or `campaignStatus: ACTIVE`. On TikTok the whole campaign > ad group > ad hierarchy stays paused.
          */
         status?: 'ACTIVE' | 'PAUSED';
         /**