@zernio/node 0.2.986 → 0.2.988

package/dist/index.d.mts

@@ -38725,11 +38725,11 @@ type UpdateAdSetData = {
              */
             billingEvent?: string;
             /**
-             * Ad set start_time (ISO 8601).
+             * Ad set start_time (ISO 8601). A value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone.
              */
             startDate?: string;
             /**
-             * Ad set end_time (ISO 8601).
+             * Ad set end_time (ISO 8601). A value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone.
              */
             endDate?: string;
             /**
@@ -38785,7 +38785,7 @@ type UpdateAdSetResponse = ({
     budget?: AdBudget;
     budgetLevel?: 'adset';
     /**
-     * The status written to the ad set. Absent when nothing was written (see statusMessage).
+     * The status written to the ad set switch
      */
     status?: 'active' | 'paused';
     /**
@@ -38800,10 +38800,6 @@ type UpdateAdSetResponse = ({
      * 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;
@@ -38846,7 +38842,7 @@ type UpdateAdSetStatusData = {
 };
 type UpdateAdSetStatusResponse = ({
     /**
-     * The status written to the ad set. Absent when nothing was written (see message).
+     * The status written to the ad set switch
      */
     status?: 'active' | 'paused';
     /**
@@ -38858,13 +38854,9 @@ type UpdateAdSetStatusResponse = ({
      */
     skipped?: number;
     /**
-     * Why each group of ads was skipped
+     * Why each group of ads was skipped (for example "2 ads already switched off", read from each ad's own switch)
      */
     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;
@@ -39247,15 +39239,23 @@ type UpdateAdStatusData = {
 };
 type UpdateAdStatusResponse = ({
     /**
-     * 1 when the status changed, 0 when skipped
+     * 1 when the switch was written, 0 when skipped
      */
     updated?: number;
     /**
-     * 1 when skipped (terminal status or already in target state), else 0
+     * 1 when skipped (terminal status, or the ad's own switch already in the target state), else 0
      */
     skipped?: number;
     /**
-     * Human-readable summary (present only when skipped)
+     * The ad's delivery status after the call, as the platform reports it when it can be read back (e.g. `paused` for an ad switched on under a paused campaign)
+     */
+    status?: string;
+    /**
+     * The ad's own on/off switch (`ACTIVE` / `PAUSED`), re-read from the platform after the write. Null where the platform exposes no per-ad switch (X) or the read-back failed and the platform does not store one.
+     */
+    configuredStatus?: (string) | null;
+    /**
+     * Human-readable summary (present only when skipped), e.g. "No change: the ad's own switch is already off"
      */
     message?: string;
 });
@@ -42967,11 +42967,11 @@ type BoostPostData = {
          */
         currency?: string;
         /**
-         * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's `start_time`. When omitted the ad starts delivering immediately. Same field as on POST /v1/ads/create.
+         * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's `start_time`. When omitted the ad starts delivering immediately. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone. Same field as on POST /v1/ads/create.
          */
         startDate?: string;
         /**
-         * Ad-set end time (ISO 8601), mapped to the ad set's `end_time`. Required for lifetime budgets. Same field as on POST /v1/ads/create.
+         * Ad-set end time (ISO 8601), mapped to the ad set's `end_time`. Required for lifetime budgets. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone, and a date-only end runs to 23:59:59 local. Same field as on POST /v1/ads/create.
          */
         endDate?: string;
         /**
@@ -44110,17 +44110,18 @@ type CreateStandaloneAdData = {
             [key: string]: (number);
         };
         /**
-         * Required for lifetime budgets. On TikTok a value without an offset (`YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`) is read in the ad account timezone.
+         * Required for lifetime budgets. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone, and a date-only end runs to 23:59:59 local.
          */
         endDate?: string;
         /**
          * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's
          * start (Meta `start_time`, TikTok ad group `schedule_start_time`, LinkedIn / Pinterest / X
          * / Google campaign start). When omitted the ad starts delivering immediately. For lifetime
-         * budgets Meta also requires `endDate`. On TikTok a value without an offset
-         * (`YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`) is read in the ad account timezone. The created
-         * ad's `schedule` echoes the start and end the platform stored, as UTC instants. Same field
-         * as on `POST /v1/ads/boost`.
+         * budgets Meta also requires `endDate`. On Meta and TikTok a value without an offset
+         * (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account
+         * timezone (Meta itself would read it as UTC). The created ad's `schedule` echoes the start
+         * and end the platform stored, as UTC instants; when attaching to an existing ad set
+         * (`adSetId`) it is that ad set's start and end. Same field as on `POST /v1/ads/boost`.
          *
          */
         startDate?: string;

package/dist/index.d.ts

@@ -38725,11 +38725,11 @@ type UpdateAdSetData = {
              */
             billingEvent?: string;
             /**
-             * Ad set start_time (ISO 8601).
+             * Ad set start_time (ISO 8601). A value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone.
              */
             startDate?: string;
             /**
-             * Ad set end_time (ISO 8601).
+             * Ad set end_time (ISO 8601). A value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone.
              */
             endDate?: string;
             /**
@@ -38785,7 +38785,7 @@ type UpdateAdSetResponse = ({
     budget?: AdBudget;
     budgetLevel?: 'adset';
     /**
-     * The status written to the ad set. Absent when nothing was written (see statusMessage).
+     * The status written to the ad set switch
      */
     status?: 'active' | 'paused';
     /**
@@ -38800,10 +38800,6 @@ type UpdateAdSetResponse = ({
      * 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;
@@ -38846,7 +38842,7 @@ type UpdateAdSetStatusData = {
 };
 type UpdateAdSetStatusResponse = ({
     /**
-     * The status written to the ad set. Absent when nothing was written (see message).
+     * The status written to the ad set switch
      */
     status?: 'active' | 'paused';
     /**
@@ -38858,13 +38854,9 @@ type UpdateAdSetStatusResponse = ({
      */
     skipped?: number;
     /**
-     * Why each group of ads was skipped
+     * Why each group of ads was skipped (for example "2 ads already switched off", read from each ad's own switch)
      */
     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;
@@ -39247,15 +39239,23 @@ type UpdateAdStatusData = {
 };
 type UpdateAdStatusResponse = ({
     /**
-     * 1 when the status changed, 0 when skipped
+     * 1 when the switch was written, 0 when skipped
      */
     updated?: number;
     /**
-     * 1 when skipped (terminal status or already in target state), else 0
+     * 1 when skipped (terminal status, or the ad's own switch already in the target state), else 0
      */
     skipped?: number;
     /**
-     * Human-readable summary (present only when skipped)
+     * The ad's delivery status after the call, as the platform reports it when it can be read back (e.g. `paused` for an ad switched on under a paused campaign)
+     */
+    status?: string;
+    /**
+     * The ad's own on/off switch (`ACTIVE` / `PAUSED`), re-read from the platform after the write. Null where the platform exposes no per-ad switch (X) or the read-back failed and the platform does not store one.
+     */
+    configuredStatus?: (string) | null;
+    /**
+     * Human-readable summary (present only when skipped), e.g. "No change: the ad's own switch is already off"
      */
     message?: string;
 });
@@ -42967,11 +42967,11 @@ type BoostPostData = {
          */
         currency?: string;
         /**
-         * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's `start_time`. When omitted the ad starts delivering immediately. Same field as on POST /v1/ads/create.
+         * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's `start_time`. When omitted the ad starts delivering immediately. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone. Same field as on POST /v1/ads/create.
          */
         startDate?: string;
         /**
-         * Ad-set end time (ISO 8601), mapped to the ad set's `end_time`. Required for lifetime budgets. Same field as on POST /v1/ads/create.
+         * Ad-set end time (ISO 8601), mapped to the ad set's `end_time`. Required for lifetime budgets. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone, and a date-only end runs to 23:59:59 local. Same field as on POST /v1/ads/create.
          */
         endDate?: string;
         /**
@@ -44110,17 +44110,18 @@ type CreateStandaloneAdData = {
             [key: string]: (number);
         };
         /**
-         * Required for lifetime budgets. On TikTok a value without an offset (`YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`) is read in the ad account timezone.
+         * Required for lifetime budgets. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone, and a date-only end runs to 23:59:59 local.
          */
         endDate?: string;
         /**
          * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's
          * start (Meta `start_time`, TikTok ad group `schedule_start_time`, LinkedIn / Pinterest / X
          * / Google campaign start). When omitted the ad starts delivering immediately. For lifetime
-         * budgets Meta also requires `endDate`. On TikTok a value without an offset
-         * (`YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`) is read in the ad account timezone. The created
-         * ad's `schedule` echoes the start and end the platform stored, as UTC instants. Same field
-         * as on `POST /v1/ads/boost`.
+         * budgets Meta also requires `endDate`. On Meta and TikTok a value without an offset
+         * (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account
+         * timezone (Meta itself would read it as UTC). The created ad's `schedule` echoes the start
+         * and end the platform stored, as UTC instants; when attaching to an existing ad set
+         * (`adSetId`) it is that ad set's start and end. Same field as on `POST /v1/ads/boost`.
          *
          */
         startDate?: string;

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -9786,13 +9786,13 @@ export const deleteAdSet = <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`.
+ * Writes the ad set's own on/off switch on every platform (Meta
+ * `configured_status`, TikTok ad group `operation_status`, Google ad group
+ * status, LinkedIn campaign, Pinterest ad group, X line item, OpenAI ad
+ * group), whatever delivery status its ads report: an ad still in review
+ * or paused by its campaign does not block it. The echoed `status` is the
+ * confirmation that it landed. On TikTok, Pinterest and OpenAI the ads
+ * whose own switch is not yet in the target state are flipped with it.
  *
  * `updated` / `skipped` describe only the ads whose own stored status
  * CHANGED alongside the switch, so `updated: 0` is a normal successful
@@ -10007,16 +10007,28 @@ export const deleteAd = <ThrowOnError extends boolean = false>(options: OptionsL
 
 /**
  * Pause or resume a single ad
- * Ad-scoped pause/resume: touches ONLY this ad, never its parent ad set or
- * campaign (so sibling ads keep running). Thin wrapper over the `status`
- * field of PUT /v1/ads/{adId}, for callers that want a URL symmetric to
+ * Ad-scoped pause/resume: flips ONLY this ad's own switch (Meta
+ * `configured_status`, TikTok `operation_status`, Google ad group ad
+ * status, LinkedIn creative, Pinterest ad), never its parent ad set or
+ * campaign, so sibling ads keep running. X is the exception: its smallest
+ * switch is the line item. Thin wrapper over the `status` field of
+ * PUT /v1/ads/{adId}, for callers that want a URL symmetric to
  * /v1/ads/campaigns/{campaignId}/status and /v1/ads/ad-sets/{adSetId}/status.
  *
+ * The ad's own switch is independent of its delivery status. An ad paused
+ * only because its campaign or ad set is off (`status: paused`,
+ * `configuredStatus: ACTIVE`) can still be switched off here, and
+ * switching an ad on under a paused campaign leaves it `paused` until the
+ * campaign is resumed. After the write the switch is read back from the
+ * platform and returned as `configuredStatus`, together with the
+ * resulting delivery `status`.
+ *
  * `{adId}` accepts the same identifier dialects as GET/PUT /v1/ads/{adId}
  * (Zernio hex `_id`, Meta numeric `platformAdId`, or the creative's
  * effective story/media IDs). `platform` is inferred from the ad, so it's
  * not required in the body. Ads in terminal statuses (rejected, completed,
- * cancelled) and no-op flips (already in the target state) are skipped.
+ * cancelled) are skipped, and so is a request whose target already matches
+ * the ad's own switch. The rolled-up `status` never decides a skip.
  *
  */
 export const updateAdStatus = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<UpdateAdStatusData, ThrowOnError>) => {

package/src/generated/types.gen.ts

@@ -39139,11 +39139,11 @@ export type UpdateAdSetData = {
              */
             billingEvent?: string;
             /**
-             * Ad set start_time (ISO 8601).
+             * Ad set start_time (ISO 8601). A value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone.
              */
             startDate?: string;
             /**
-             * Ad set end_time (ISO 8601).
+             * Ad set end_time (ISO 8601). A value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone.
              */
             endDate?: string;
             /**
@@ -39200,7 +39200,7 @@ export type UpdateAdSetResponse = ({
     budget?: AdBudget;
     budgetLevel?: 'adset';
     /**
-     * The status written to the ad set. Absent when nothing was written (see statusMessage).
+     * The status written to the ad set switch
      */
     status?: 'active' | 'paused';
     /**
@@ -39215,10 +39215,6 @@ export type UpdateAdSetResponse = ({
      * 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;
@@ -39267,7 +39263,7 @@ export type UpdateAdSetStatusData = {
 
 export type UpdateAdSetStatusResponse = ({
     /**
-     * The status written to the ad set. Absent when nothing was written (see message).
+     * The status written to the ad set switch
      */
     status?: 'active' | 'paused';
     /**
@@ -39279,13 +39275,9 @@ export type UpdateAdSetStatusResponse = ({
      */
     skipped?: number;
     /**
-     * Why each group of ads was skipped
+     * Why each group of ads was skipped (for example "2 ads already switched off", read from each ad's own switch)
      */
     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 | {
@@ -39686,15 +39678,23 @@ export type UpdateAdStatusData = {
 
 export type UpdateAdStatusResponse = ({
     /**
-     * 1 when the status changed, 0 when skipped
+     * 1 when the switch was written, 0 when skipped
      */
     updated?: number;
     /**
-     * 1 when skipped (terminal status or already in target state), else 0
+     * 1 when skipped (terminal status, or the ad's own switch already in the target state), else 0
      */
     skipped?: number;
     /**
-     * Human-readable summary (present only when skipped)
+     * The ad's delivery status after the call, as the platform reports it when it can be read back (e.g. `paused` for an ad switched on under a paused campaign)
+     */
+    status?: string;
+    /**
+     * The ad's own on/off switch (`ACTIVE` / `PAUSED`), re-read from the platform after the write. Null where the platform exposes no per-ad switch (X) or the read-back failed and the platform does not store one.
+     */
+    configuredStatus?: (string) | null;
+    /**
+     * Human-readable summary (present only when skipped), e.g. "No change: the ad's own switch is already off"
      */
     message?: string;
 });
@@ -43684,11 +43684,11 @@ export type BoostPostData = {
          */
         currency?: string;
         /**
-         * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's `start_time`. When omitted the ad starts delivering immediately. Same field as on POST /v1/ads/create.
+         * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's `start_time`. When omitted the ad starts delivering immediately. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone. Same field as on POST /v1/ads/create.
          */
         startDate?: string;
         /**
-         * Ad-set end time (ISO 8601), mapped to the ad set's `end_time`. Required for lifetime budgets. Same field as on POST /v1/ads/create.
+         * Ad-set end time (ISO 8601), mapped to the ad set's `end_time`. Required for lifetime budgets. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone, and a date-only end runs to 23:59:59 local. Same field as on POST /v1/ads/create.
          */
         endDate?: string;
         /**
@@ -44851,17 +44851,18 @@ export type CreateStandaloneAdData = {
             [key: string]: (number);
         };
         /**
-         * Required for lifetime budgets. On TikTok a value without an offset (`YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`) is read in the ad account timezone.
+         * Required for lifetime budgets. On Meta and TikTok a value without an offset (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account timezone, and a date-only end runs to 23:59:59 local.
          */
         endDate?: string;
         /**
          * Ad-set start time (ISO 8601, e.g. "2026-06-10T09:00:00Z"), mapped to the ad set's
          * start (Meta `start_time`, TikTok ad group `schedule_start_time`, LinkedIn / Pinterest / X
          * / Google campaign start). When omitted the ad starts delivering immediately. For lifetime
-         * budgets Meta also requires `endDate`. On TikTok a value without an offset
-         * (`YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DD`) is read in the ad account timezone. The created
-         * ad's `schedule` echoes the start and end the platform stored, as UTC instants. Same field
-         * as on `POST /v1/ads/boost`.
+         * budgets Meta also requires `endDate`. On Meta and TikTok a value without an offset
+         * (`YYYY-MM-DD`, `YYYY-MM-DD HH:MM:SS` or `YYYY-MM-DDTHH:MM:SS`) is read in the ad account
+         * timezone (Meta itself would read it as UTC). The created ad's `schedule` echoes the start
+         * and end the platform stored, as UTC instants; when attaching to an existing ad set
+         * (`adSetId`) it is that ad set's start and end. Same field as on `POST /v1/ads/boost`.
          *
          */
         startDate?: string;