@zernio/node 0.2.999 → 0.2.1001

package/dist/index.d.mts

@@ -2045,7 +2045,7 @@ type Ad = {
      */
     status?: (AdStatus);
     /**
-     * The ad's own on/off switch as configured on the platform, independent of its parents: an ACTIVE ad under a paused ad set or campaign still reads ACTIVE here while `status` reads `paused`. Sources: Meta `configured_status`, TikTok ad `operation_status` (ENABLE -> ACTIVE, DISABLE -> PAUSED), ChatGPT (OpenAI) ad `status` (ACTIVE / PAUSED, plus ARCHIVED on OpenAI). On create it is read back from the platform, not copied from the request, so it can read ACTIVE for a `PAUSED` create where the platform holds the pause at the campaign (some Meta create flows). A TikTok ad created `PAUSED` is switched off at the ad, ad group and campaign and reads PAUSED. Distinct from `status`, which is the ancestor-cascaded delivery status. Only present for Meta, TikTok and OpenAI ads created or synced after the field was added for that platform; null otherwise.
+     * The ad's own on/off switch as configured on the platform, independent of its parents: an ACTIVE ad under a paused ad set or campaign still reads ACTIVE here while `status` reads `paused`. Sources: Meta `configured_status`, TikTok ad `operation_status` (ENABLE -> ACTIVE, DISABLE -> PAUSED), ChatGPT (OpenAI) ad `status` (ACTIVE / PAUSED, plus ARCHIVED on OpenAI). On create it is read back from the platform, not copied from the request: a `PAUSED` create pauses only the top-most object it creates, so an ad under a new paused campaign or ad set reads ACTIVE here with `status: paused`, and only an ad attached to an existing ad set reads PAUSED. Distinct from `status`, which is the ancestor-cascaded delivery status. Only present for Meta, TikTok and OpenAI ads created or synced after the field was added for that platform; null otherwise.
      */
     configuredStatus?: (string) | null;
     /**
@@ -6027,18 +6027,20 @@ type CtwaAdRequestBody = {
      */
     objective?: 'OUTCOME_ENGAGEMENT' | 'OUTCOME_SALES' | 'OUTCOME_LEADS';
     /**
-     * Ad-level status. Defaults to `ACTIVE`. `PAUSED` skips activating the
-     * newly created ad(s) after Meta accepts them.
+     * Defaults to `ACTIVE`. `PAUSED` pauses only the top-most object this
+     * call creates: the new campaign (ad set and ads switched on), or, with
+     * `adSetId`, the new ads themselves.
      *
      */
     status?: 'ACTIVE' | 'PAUSED';
     /**
      * Campaign-level status, same semantics as `POST /v1/ads/create`. Defaults
-     * to `ACTIVE`. `PAUSED` holds activation at the campaign so it never
-     * spends before the advertiser reviews it, while the ad set and ad still
-     * switch on (one resume call brings the whole hierarchy live). Only
-     * meaningful when a new campaign is being created; rejected with a 400
-     * alongside `adSetId` (the attach shape reuses an existing campaign).
+     * to `status`. `PAUSED` holds the new campaign off while the ad set and
+     * ads switch on (one resume call brings the whole hierarchy live);
+     * `ACTIVE` with `status: PAUSED` switches the campaign on and pauses the
+     * new ad set instead. Only meaningful when a new campaign is being
+     * created; rejected with a 400 alongside `adSetId` (the attach shape
+     * reuses an existing campaign).
      *
      */
     campaignStatus?: 'ACTIVE' | 'PAUSED';
@@ -6125,18 +6127,20 @@ type advantageAudience = 0 | 1;
  */
 type objective = 'OUTCOME_ENGAGEMENT' | 'OUTCOME_SALES' | 'OUTCOME_LEADS';
 /**
- * Ad-level status. Defaults to `ACTIVE`. `PAUSED` skips activating the
- * newly created ad(s) after Meta accepts them.
+ * Defaults to `ACTIVE`. `PAUSED` pauses only the top-most object this
+ * call creates: the new campaign (ad set and ads switched on), or, with
+ * `adSetId`, the new ads themselves.
  *
  */
 type status13 = 'ACTIVE' | 'PAUSED';
 /**
  * Campaign-level status, same semantics as `POST /v1/ads/create`. Defaults
- * to `ACTIVE`. `PAUSED` holds activation at the campaign so it never
- * spends before the advertiser reviews it, while the ad set and ad still
- * switch on (one resume call brings the whole hierarchy live). Only
- * meaningful when a new campaign is being created; rejected with a 400
- * alongside `adSetId` (the attach shape reuses an existing campaign).
+ * to `status`. `PAUSED` holds the new campaign off while the ad set and
+ * ads switch on (one resume call brings the whole hierarchy live);
+ * `ACTIVE` with `status: PAUSED` switches the campaign on and pauses the
+ * new ad set instead. Only meaningful when a new campaign is being
+ * created; rejected with a 400 alongside `adSetId` (the attach shape
+ * reuses an existing campaign).
  *
  */
 type campaignStatus = 'ACTIVE' | 'PAUSED';
@@ -32985,7 +32989,7 @@ type SubmitPhoneNumberKycData = {
          */
         areaCode?: string;
         /**
-         * With areaCode: pre-order that area when it has no stock (an area listed in soldOutAreas with preOrderable true) instead of failing with AREA_CODE_UNAVAILABLE. The carrier sources a number in that area.
+         * With areaCode: pre-order that area when it has no stock (an area listed in soldOutAreas with preOrderable true) instead of failing with AREA_CODE_UNAVAILABLE. The carrier sources a number in that area. Not needed without areaCode: a whole pair with no stock, or an address in a geographic-match country whose area has no stock, is pre-ordered on its own (see preOrder in the response).
          */
         preOrder?: boolean;
         /**
@@ -33040,7 +33044,7 @@ type SubmitPhoneNumberKycData = {
 type SubmitPhoneNumberKycResponse = ({
     status?: 'kyc_submitted' | 'kyc_reused' | 'kyc_already_submitted';
     /**
-     * True when nothing was in stock and this submission placed a pre-order. The number stays `pending_regulatory` until we get it, from regular stock the moment it returns or sourced by the carrier (usually 2 to 4 weeks), and is not billed until active. Releasing it (DELETE /v1/phone-numbers/{id}) cancels the pre-order. A pre-order is one number: `quantity` above 1 is rejected with 400.
+     * True when this submission placed a pre-order instead of an order from stock: the country and type had nothing deliverable, the picked areaCode was sold out (preOrder: true sent), or the country requires the number's area to cover the registered address and that area has no stock (the carrier is then asked for a number in exactly that area). The number stays `pending_regulatory` until we get it, from regular stock the moment it returns or sourced by the carrier (usually 2 to 4 weeks, never guaranteed), and is not billed until active. Releasing it (DELETE /v1/phone-numbers/{id}) cancels the pre-order. A pre-order is one number: `quantity` above 1 is rejected with 400.
      */
     preOrder?: boolean;
     /**
@@ -33807,7 +33811,7 @@ type SubmitWhatsAppNumberKycData = {
          */
         areaCode?: string;
         /**
-         * With areaCode: pre-order that area when it has no stock (an area listed in soldOutAreas with preOrderable true) instead of failing with AREA_CODE_UNAVAILABLE. The carrier sources a number in that area.
+         * With areaCode: pre-order that area when it has no stock (an area listed in soldOutAreas with preOrderable true) instead of failing with AREA_CODE_UNAVAILABLE. The carrier sources a number in that area. Not needed without areaCode: a whole pair with no stock, or an address in a geographic-match country whose area has no stock, is pre-ordered on its own (see preOrder in the response).
          */
         preOrder?: boolean;
         /**
@@ -33858,7 +33862,7 @@ type SubmitWhatsAppNumberKycData = {
 type SubmitWhatsAppNumberKycResponse = ({
     status?: 'kyc_submitted' | 'kyc_reused' | 'kyc_already_submitted';
     /**
-     * True when nothing was in stock and this submission placed a pre-order. The number stays `pending_regulatory` until we get it, from regular stock the moment it returns or sourced by the carrier (usually 2 to 4 weeks), and is not billed until active. Releasing it (DELETE /v1/phone-numbers/{id}) cancels the pre-order. A pre-order is one number: `quantity` above 1 is rejected with 400.
+     * True when this submission placed a pre-order instead of an order from stock: the country and type had nothing deliverable, the picked areaCode was sold out (preOrder: true sent), or the country requires the number's area to cover the registered address and that area has no stock (the carrier is then asked for a number in exactly that area). The number stays `pending_regulatory` until we get it, from regular stock the moment it returns or sourced by the carrier (usually 2 to 4 weeks, never guaranteed), and is not billed until active. Releasing it (DELETE /v1/phone-numbers/{id}) cancels the pre-order. A pre-order is one number: `quantity` above 1 is rejected with 400.
      */
     preOrder?: boolean;
     /**
@@ -44008,7 +44012,7 @@ type BoostPostData = {
          */
         leadGenFormId?: string;
         /**
-         * Meta, TikTok, LinkedIn, and Google. Publish state of the created entities. Omitted or ACTIVE publishes live (default); PAUSED creates them paused so you can review before they spend. On Meta a new campaign stays paused until explicitly activated; an attached ad is itself paused. On Google the pause is held on the campaign the boost creates (ad group and ad switched on), so PUT /v1/ads/campaigns/{campaignId}/status with `active` brings it live. On LinkedIn the whole campaign group, campaign, and creative hierarchy stays PAUSED (intendedStatus PAUSED on each).
+         * 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.
          */
         status?: 'ACTIVE' | 'PAUSED';
         /**
@@ -44322,11 +44326,11 @@ type CreateStandaloneAdData = {
          */
         budgetType?: 'daily' | 'lifetime';
         /**
-         * Google Performance Max accepts PAUSED only and always creates a paused campaign. Google Search and Display, Meta, TikTok, LinkedIn, and ChatGPT (OpenAI): 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`. Google Search and Display follow the same rule, and because Google keeps an independent switch at campaign, ad group and ad level, a PAUSED create leaves the campaign it creates PAUSED at Google. On TikTok the whole campaign > ad group > ad hierarchy stays paused. On LinkedIn the whole campaign group, campaign, and creative hierarchy stays PAUSED (intendedStatus PAUSED on each). ChatGPT (OpenAI) follows the Meta rule: the pause is held on the campaign this call creates.
+         * Publish state of the created entities, on every platform. Omitted or ACTIVE publishes live (default, back-compat); PAUSED pauses only the TOP-MOST object this call creates and switches everything below it on, so one resume of that object brings the new tree live and nothing that already existed is touched: a new campaign is held paused with its ad set and ad on; with `existingCampaignId` the new ad set is held paused with its ad on; with `adSetId` the new ad itself is paused. `campaignStatus: ACTIVE` with `status: PAUSED` moves the pause down to the new ad set. LinkedIn: a held campaign group is PAUSED with its campaign and creative ACTIVE; a new campaign in an existing group stays DRAFT. X has no per-ad switch, so its lowest level is the line item. Google Performance Max and Demand Gen accept PAUSED only (the campaign is created paused).
          */
         status?: 'ACTIVE' | 'PAUSED';
         /**
-         * Meta, Google, and ChatGPT (OpenAI). Overrides `status` for the campaign level alone, so you can create a live campaign whose ad set and ad stay paused, or the reverse. Omitted, it follows `status`.
+         * Meta, Google, and ChatGPT (OpenAI). Overrides `status` for the new campaign alone. `PAUSED` holds the campaign off with its ad set and ad on; `ACTIVE` with `status: PAUSED` switches the campaign on and holds the new ad set paused (its ad on). Omitted, it follows `status`.
          */
         campaignStatus?: 'ACTIVE' | 'PAUSED';
         /**

package/dist/index.d.ts

@@ -2045,7 +2045,7 @@ type Ad = {
      */
     status?: (AdStatus);
     /**
-     * The ad's own on/off switch as configured on the platform, independent of its parents: an ACTIVE ad under a paused ad set or campaign still reads ACTIVE here while `status` reads `paused`. Sources: Meta `configured_status`, TikTok ad `operation_status` (ENABLE -> ACTIVE, DISABLE -> PAUSED), ChatGPT (OpenAI) ad `status` (ACTIVE / PAUSED, plus ARCHIVED on OpenAI). On create it is read back from the platform, not copied from the request, so it can read ACTIVE for a `PAUSED` create where the platform holds the pause at the campaign (some Meta create flows). A TikTok ad created `PAUSED` is switched off at the ad, ad group and campaign and reads PAUSED. Distinct from `status`, which is the ancestor-cascaded delivery status. Only present for Meta, TikTok and OpenAI ads created or synced after the field was added for that platform; null otherwise.
+     * The ad's own on/off switch as configured on the platform, independent of its parents: an ACTIVE ad under a paused ad set or campaign still reads ACTIVE here while `status` reads `paused`. Sources: Meta `configured_status`, TikTok ad `operation_status` (ENABLE -> ACTIVE, DISABLE -> PAUSED), ChatGPT (OpenAI) ad `status` (ACTIVE / PAUSED, plus ARCHIVED on OpenAI). On create it is read back from the platform, not copied from the request: a `PAUSED` create pauses only the top-most object it creates, so an ad under a new paused campaign or ad set reads ACTIVE here with `status: paused`, and only an ad attached to an existing ad set reads PAUSED. Distinct from `status`, which is the ancestor-cascaded delivery status. Only present for Meta, TikTok and OpenAI ads created or synced after the field was added for that platform; null otherwise.
      */
     configuredStatus?: (string) | null;
     /**
@@ -6027,18 +6027,20 @@ type CtwaAdRequestBody = {
      */
     objective?: 'OUTCOME_ENGAGEMENT' | 'OUTCOME_SALES' | 'OUTCOME_LEADS';
     /**
-     * Ad-level status. Defaults to `ACTIVE`. `PAUSED` skips activating the
-     * newly created ad(s) after Meta accepts them.
+     * Defaults to `ACTIVE`. `PAUSED` pauses only the top-most object this
+     * call creates: the new campaign (ad set and ads switched on), or, with
+     * `adSetId`, the new ads themselves.
      *
      */
     status?: 'ACTIVE' | 'PAUSED';
     /**
      * Campaign-level status, same semantics as `POST /v1/ads/create`. Defaults
-     * to `ACTIVE`. `PAUSED` holds activation at the campaign so it never
-     * spends before the advertiser reviews it, while the ad set and ad still
-     * switch on (one resume call brings the whole hierarchy live). Only
-     * meaningful when a new campaign is being created; rejected with a 400
-     * alongside `adSetId` (the attach shape reuses an existing campaign).
+     * to `status`. `PAUSED` holds the new campaign off while the ad set and
+     * ads switch on (one resume call brings the whole hierarchy live);
+     * `ACTIVE` with `status: PAUSED` switches the campaign on and pauses the
+     * new ad set instead. Only meaningful when a new campaign is being
+     * created; rejected with a 400 alongside `adSetId` (the attach shape
+     * reuses an existing campaign).
      *
      */
     campaignStatus?: 'ACTIVE' | 'PAUSED';
@@ -6125,18 +6127,20 @@ type advantageAudience = 0 | 1;
  */
 type objective = 'OUTCOME_ENGAGEMENT' | 'OUTCOME_SALES' | 'OUTCOME_LEADS';
 /**
- * Ad-level status. Defaults to `ACTIVE`. `PAUSED` skips activating the
- * newly created ad(s) after Meta accepts them.
+ * Defaults to `ACTIVE`. `PAUSED` pauses only the top-most object this
+ * call creates: the new campaign (ad set and ads switched on), or, with
+ * `adSetId`, the new ads themselves.
  *
  */
 type status13 = 'ACTIVE' | 'PAUSED';
 /**
  * Campaign-level status, same semantics as `POST /v1/ads/create`. Defaults
- * to `ACTIVE`. `PAUSED` holds activation at the campaign so it never
- * spends before the advertiser reviews it, while the ad set and ad still
- * switch on (one resume call brings the whole hierarchy live). Only
- * meaningful when a new campaign is being created; rejected with a 400
- * alongside `adSetId` (the attach shape reuses an existing campaign).
+ * to `status`. `PAUSED` holds the new campaign off while the ad set and
+ * ads switch on (one resume call brings the whole hierarchy live);
+ * `ACTIVE` with `status: PAUSED` switches the campaign on and pauses the
+ * new ad set instead. Only meaningful when a new campaign is being
+ * created; rejected with a 400 alongside `adSetId` (the attach shape
+ * reuses an existing campaign).
  *
  */
 type campaignStatus = 'ACTIVE' | 'PAUSED';
@@ -32985,7 +32989,7 @@ type SubmitPhoneNumberKycData = {
          */
         areaCode?: string;
         /**
-         * With areaCode: pre-order that area when it has no stock (an area listed in soldOutAreas with preOrderable true) instead of failing with AREA_CODE_UNAVAILABLE. The carrier sources a number in that area.
+         * With areaCode: pre-order that area when it has no stock (an area listed in soldOutAreas with preOrderable true) instead of failing with AREA_CODE_UNAVAILABLE. The carrier sources a number in that area. Not needed without areaCode: a whole pair with no stock, or an address in a geographic-match country whose area has no stock, is pre-ordered on its own (see preOrder in the response).
          */
         preOrder?: boolean;
         /**
@@ -33040,7 +33044,7 @@ type SubmitPhoneNumberKycData = {
 type SubmitPhoneNumberKycResponse = ({
     status?: 'kyc_submitted' | 'kyc_reused' | 'kyc_already_submitted';
     /**
-     * True when nothing was in stock and this submission placed a pre-order. The number stays `pending_regulatory` until we get it, from regular stock the moment it returns or sourced by the carrier (usually 2 to 4 weeks), and is not billed until active. Releasing it (DELETE /v1/phone-numbers/{id}) cancels the pre-order. A pre-order is one number: `quantity` above 1 is rejected with 400.
+     * True when this submission placed a pre-order instead of an order from stock: the country and type had nothing deliverable, the picked areaCode was sold out (preOrder: true sent), or the country requires the number's area to cover the registered address and that area has no stock (the carrier is then asked for a number in exactly that area). The number stays `pending_regulatory` until we get it, from regular stock the moment it returns or sourced by the carrier (usually 2 to 4 weeks, never guaranteed), and is not billed until active. Releasing it (DELETE /v1/phone-numbers/{id}) cancels the pre-order. A pre-order is one number: `quantity` above 1 is rejected with 400.
      */
     preOrder?: boolean;
     /**
@@ -33807,7 +33811,7 @@ type SubmitWhatsAppNumberKycData = {
          */
         areaCode?: string;
         /**
-         * With areaCode: pre-order that area when it has no stock (an area listed in soldOutAreas with preOrderable true) instead of failing with AREA_CODE_UNAVAILABLE. The carrier sources a number in that area.
+         * With areaCode: pre-order that area when it has no stock (an area listed in soldOutAreas with preOrderable true) instead of failing with AREA_CODE_UNAVAILABLE. The carrier sources a number in that area. Not needed without areaCode: a whole pair with no stock, or an address in a geographic-match country whose area has no stock, is pre-ordered on its own (see preOrder in the response).
          */
         preOrder?: boolean;
         /**
@@ -33858,7 +33862,7 @@ type SubmitWhatsAppNumberKycData = {
 type SubmitWhatsAppNumberKycResponse = ({
     status?: 'kyc_submitted' | 'kyc_reused' | 'kyc_already_submitted';
     /**
-     * True when nothing was in stock and this submission placed a pre-order. The number stays `pending_regulatory` until we get it, from regular stock the moment it returns or sourced by the carrier (usually 2 to 4 weeks), and is not billed until active. Releasing it (DELETE /v1/phone-numbers/{id}) cancels the pre-order. A pre-order is one number: `quantity` above 1 is rejected with 400.
+     * True when this submission placed a pre-order instead of an order from stock: the country and type had nothing deliverable, the picked areaCode was sold out (preOrder: true sent), or the country requires the number's area to cover the registered address and that area has no stock (the carrier is then asked for a number in exactly that area). The number stays `pending_regulatory` until we get it, from regular stock the moment it returns or sourced by the carrier (usually 2 to 4 weeks, never guaranteed), and is not billed until active. Releasing it (DELETE /v1/phone-numbers/{id}) cancels the pre-order. A pre-order is one number: `quantity` above 1 is rejected with 400.
      */
     preOrder?: boolean;
     /**
@@ -44008,7 +44012,7 @@ type BoostPostData = {
          */
         leadGenFormId?: string;
         /**
-         * Meta, TikTok, LinkedIn, and Google. Publish state of the created entities. Omitted or ACTIVE publishes live (default); PAUSED creates them paused so you can review before they spend. On Meta a new campaign stays paused until explicitly activated; an attached ad is itself paused. On Google the pause is held on the campaign the boost creates (ad group and ad switched on), so PUT /v1/ads/campaigns/{campaignId}/status with `active` brings it live. On LinkedIn the whole campaign group, campaign, and creative hierarchy stays PAUSED (intendedStatus PAUSED on each).
+         * 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.
          */
         status?: 'ACTIVE' | 'PAUSED';
         /**
@@ -44322,11 +44326,11 @@ type CreateStandaloneAdData = {
          */
         budgetType?: 'daily' | 'lifetime';
         /**
-         * Google Performance Max accepts PAUSED only and always creates a paused campaign. Google Search and Display, Meta, TikTok, LinkedIn, and ChatGPT (OpenAI): 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`. Google Search and Display follow the same rule, and because Google keeps an independent switch at campaign, ad group and ad level, a PAUSED create leaves the campaign it creates PAUSED at Google. On TikTok the whole campaign > ad group > ad hierarchy stays paused. On LinkedIn the whole campaign group, campaign, and creative hierarchy stays PAUSED (intendedStatus PAUSED on each). ChatGPT (OpenAI) follows the Meta rule: the pause is held on the campaign this call creates.
+         * Publish state of the created entities, on every platform. Omitted or ACTIVE publishes live (default, back-compat); PAUSED pauses only the TOP-MOST object this call creates and switches everything below it on, so one resume of that object brings the new tree live and nothing that already existed is touched: a new campaign is held paused with its ad set and ad on; with `existingCampaignId` the new ad set is held paused with its ad on; with `adSetId` the new ad itself is paused. `campaignStatus: ACTIVE` with `status: PAUSED` moves the pause down to the new ad set. LinkedIn: a held campaign group is PAUSED with its campaign and creative ACTIVE; a new campaign in an existing group stays DRAFT. X has no per-ad switch, so its lowest level is the line item. Google Performance Max and Demand Gen accept PAUSED only (the campaign is created paused).
          */
         status?: 'ACTIVE' | 'PAUSED';
         /**
-         * Meta, Google, and ChatGPT (OpenAI). Overrides `status` for the campaign level alone, so you can create a live campaign whose ad set and ad stay paused, or the reverse. Omitted, it follows `status`.
+         * Meta, Google, and ChatGPT (OpenAI). Overrides `status` for the new campaign alone. `PAUSED` holds the campaign off with its ad set and ad on; `ACTIVE` with `status: PAUSED` switches the campaign on and holds the new ad set paused (its ad on). Omitted, it follows `status`.
          */
         campaignStatus?: '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.999",
+  version: "0.2.1001",
   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.999",
+  version: "0.2.1001",
   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.999",
+  "version": "0.2.1001",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/sdk.gen.ts

@@ -9324,9 +9324,8 @@ export const listAdCampaigns = <ThrowOnError extends boolean = false>(options?:
  * `budgetType: daily`). On OpenAI `goal` sets the campaign objective, and
  * `conversions` needs an active standard conversion event on the account. LinkedIn creates the
  * campaign GROUP (our campaign level) and rejects a budget, which lives on the
- * campaign (ad set) level there; it comes back `status: DRAFT`. TikTok campaigns are
- * created without a status and report `ENABLE`. Created `PAUSED` unless
- * `status: ACTIVE` where the platform supports it.
+ * campaign (ad set) level there; it comes back `status: DRAFT`. Created `PAUSED`
+ * (TikTok `DISABLE`) unless `status: ACTIVE` where the platform supports it.
  *
  * **Idempotency:** send an `Idempotency-Key` header to make retries safe.
  */

package/src/generated/types.gen.ts

@@ -92,7 +92,7 @@ export type Ad = {
      */
     status?: (AdStatus);
     /**
-     * The ad's own on/off switch as configured on the platform, independent of its parents: an ACTIVE ad under a paused ad set or campaign still reads ACTIVE here while `status` reads `paused`. Sources: Meta `configured_status`, TikTok ad `operation_status` (ENABLE -> ACTIVE, DISABLE -> PAUSED), ChatGPT (OpenAI) ad `status` (ACTIVE / PAUSED, plus ARCHIVED on OpenAI). On create it is read back from the platform, not copied from the request, so it can read ACTIVE for a `PAUSED` create where the platform holds the pause at the campaign (some Meta create flows). A TikTok ad created `PAUSED` is switched off at the ad, ad group and campaign and reads PAUSED. Distinct from `status`, which is the ancestor-cascaded delivery status. Only present for Meta, TikTok and OpenAI ads created or synced after the field was added for that platform; null otherwise.
+     * The ad's own on/off switch as configured on the platform, independent of its parents: an ACTIVE ad under a paused ad set or campaign still reads ACTIVE here while `status` reads `paused`. Sources: Meta `configured_status`, TikTok ad `operation_status` (ENABLE -> ACTIVE, DISABLE -> PAUSED), ChatGPT (OpenAI) ad `status` (ACTIVE / PAUSED, plus ARCHIVED on OpenAI). On create it is read back from the platform, not copied from the request: a `PAUSED` create pauses only the top-most object it creates, so an ad under a new paused campaign or ad set reads ACTIVE here with `status: paused`, and only an ad attached to an existing ad set reads PAUSED. Distinct from `status`, which is the ancestor-cascaded delivery status. Only present for Meta, TikTok and OpenAI ads created or synced after the field was added for that platform; null otherwise.
      */
     configuredStatus?: (string) | null;
     /**
@@ -4236,18 +4236,20 @@ export type CtwaAdRequestBody = {
      */
     objective?: 'OUTCOME_ENGAGEMENT' | 'OUTCOME_SALES' | 'OUTCOME_LEADS';
     /**
-     * Ad-level status. Defaults to `ACTIVE`. `PAUSED` skips activating the
-     * newly created ad(s) after Meta accepts them.
+     * Defaults to `ACTIVE`. `PAUSED` pauses only the top-most object this
+     * call creates: the new campaign (ad set and ads switched on), or, with
+     * `adSetId`, the new ads themselves.
      *
      */
     status?: 'ACTIVE' | 'PAUSED';
     /**
      * Campaign-level status, same semantics as `POST /v1/ads/create`. Defaults
-     * to `ACTIVE`. `PAUSED` holds activation at the campaign so it never
-     * spends before the advertiser reviews it, while the ad set and ad still
-     * switch on (one resume call brings the whole hierarchy live). Only
-     * meaningful when a new campaign is being created; rejected with a 400
-     * alongside `adSetId` (the attach shape reuses an existing campaign).
+     * to `status`. `PAUSED` holds the new campaign off while the ad set and
+     * ads switch on (one resume call brings the whole hierarchy live);
+     * `ACTIVE` with `status: PAUSED` switches the campaign on and pauses the
+     * new ad set instead. Only meaningful when a new campaign is being
+     * created; rejected with a 400 alongside `adSetId` (the attach shape
+     * reuses an existing campaign).
      *
      */
     campaignStatus?: 'ACTIVE' | 'PAUSED';
@@ -4338,19 +4340,21 @@ export type advantageAudience = 0 | 1;
 export type objective = 'OUTCOME_ENGAGEMENT' | 'OUTCOME_SALES' | 'OUTCOME_LEADS';
 
 /**
- * Ad-level status. Defaults to `ACTIVE`. `PAUSED` skips activating the
- * newly created ad(s) after Meta accepts them.
+ * Defaults to `ACTIVE`. `PAUSED` pauses only the top-most object this
+ * call creates: the new campaign (ad set and ads switched on), or, with
+ * `adSetId`, the new ads themselves.
  *
  */
 export type status13 = 'ACTIVE' | 'PAUSED';
 
 /**
  * Campaign-level status, same semantics as `POST /v1/ads/create`. Defaults
- * to `ACTIVE`. `PAUSED` holds activation at the campaign so it never
- * spends before the advertiser reviews it, while the ad set and ad still
- * switch on (one resume call brings the whole hierarchy live). Only
- * meaningful when a new campaign is being created; rejected with a 400
- * alongside `adSetId` (the attach shape reuses an existing campaign).
+ * to `status`. `PAUSED` holds the new campaign off while the ad set and
+ * ads switch on (one resume call brings the whole hierarchy live);
+ * `ACTIVE` with `status: PAUSED` switches the campaign on and pauses the
+ * new ad set instead. Only meaningful when a new campaign is being
+ * created; rejected with a 400 alongside `adSetId` (the attach shape
+ * reuses an existing campaign).
  *
  */
 export type campaignStatus = 'ACTIVE' | 'PAUSED';
@@ -32877,7 +32881,7 @@ export type SubmitPhoneNumberKycData = {
          */
         areaCode?: string;
         /**
-         * With areaCode: pre-order that area when it has no stock (an area listed in soldOutAreas with preOrderable true) instead of failing with AREA_CODE_UNAVAILABLE. The carrier sources a number in that area.
+         * With areaCode: pre-order that area when it has no stock (an area listed in soldOutAreas with preOrderable true) instead of failing with AREA_CODE_UNAVAILABLE. The carrier sources a number in that area. Not needed without areaCode: a whole pair with no stock, or an address in a geographic-match country whose area has no stock, is pre-ordered on its own (see preOrder in the response).
          */
         preOrder?: boolean;
         /**
@@ -32933,7 +32937,7 @@ export type SubmitPhoneNumberKycData = {
 export type SubmitPhoneNumberKycResponse = ({
     status?: 'kyc_submitted' | 'kyc_reused' | 'kyc_already_submitted';
     /**
-     * True when nothing was in stock and this submission placed a pre-order. The number stays `pending_regulatory` until we get it, from regular stock the moment it returns or sourced by the carrier (usually 2 to 4 weeks), and is not billed until active. Releasing it (DELETE /v1/phone-numbers/{id}) cancels the pre-order. A pre-order is one number: `quantity` above 1 is rejected with 400.
+     * True when this submission placed a pre-order instead of an order from stock: the country and type had nothing deliverable, the picked areaCode was sold out (preOrder: true sent), or the country requires the number's area to cover the registered address and that area has no stock (the carrier is then asked for a number in exactly that area). The number stays `pending_regulatory` until we get it, from regular stock the moment it returns or sourced by the carrier (usually 2 to 4 weeks, never guaranteed), and is not billed until active. Releasing it (DELETE /v1/phone-numbers/{id}) cancels the pre-order. A pre-order is one number: `quantity` above 1 is rejected with 400.
      */
     preOrder?: boolean;
     /**
@@ -33755,7 +33759,7 @@ export type SubmitWhatsAppNumberKycData = {
          */
         areaCode?: string;
         /**
-         * With areaCode: pre-order that area when it has no stock (an area listed in soldOutAreas with preOrderable true) instead of failing with AREA_CODE_UNAVAILABLE. The carrier sources a number in that area.
+         * With areaCode: pre-order that area when it has no stock (an area listed in soldOutAreas with preOrderable true) instead of failing with AREA_CODE_UNAVAILABLE. The carrier sources a number in that area. Not needed without areaCode: a whole pair with no stock, or an address in a geographic-match country whose area has no stock, is pre-ordered on its own (see preOrder in the response).
          */
         preOrder?: boolean;
         /**
@@ -33807,7 +33811,7 @@ export type SubmitWhatsAppNumberKycData = {
 export type SubmitWhatsAppNumberKycResponse = ({
     status?: 'kyc_submitted' | 'kyc_reused' | 'kyc_already_submitted';
     /**
-     * True when nothing was in stock and this submission placed a pre-order. The number stays `pending_regulatory` until we get it, from regular stock the moment it returns or sourced by the carrier (usually 2 to 4 weeks), and is not billed until active. Releasing it (DELETE /v1/phone-numbers/{id}) cancels the pre-order. A pre-order is one number: `quantity` above 1 is rejected with 400.
+     * True when this submission placed a pre-order instead of an order from stock: the country and type had nothing deliverable, the picked areaCode was sold out (preOrder: true sent), or the country requires the number's area to cover the registered address and that area has no stock (the carrier is then asked for a number in exactly that area). The number stays `pending_regulatory` until we get it, from regular stock the moment it returns or sourced by the carrier (usually 2 to 4 weeks, never guaranteed), and is not billed until active. Releasing it (DELETE /v1/phone-numbers/{id}) cancels the pre-order. A pre-order is one number: `quantity` above 1 is rejected with 400.
      */
     preOrder?: boolean;
     /**
@@ -44694,7 +44698,7 @@ export type BoostPostData = {
          */
         leadGenFormId?: string;
         /**
-         * Meta, TikTok, LinkedIn, and Google. Publish state of the created entities. Omitted or ACTIVE publishes live (default); PAUSED creates them paused so you can review before they spend. On Meta a new campaign stays paused until explicitly activated; an attached ad is itself paused. On Google the pause is held on the campaign the boost creates (ad group and ad switched on), so PUT /v1/ads/campaigns/{campaignId}/status with `active` brings it live. On LinkedIn the whole campaign group, campaign, and creative hierarchy stays PAUSED (intendedStatus PAUSED on each).
+         * 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.
          */
         status?: 'ACTIVE' | 'PAUSED';
         /**
@@ -45032,11 +45036,11 @@ export type CreateStandaloneAdData = {
          */
         budgetType?: 'daily' | 'lifetime';
         /**
-         * Google Performance Max accepts PAUSED only and always creates a paused campaign. Google Search and Display, Meta, TikTok, LinkedIn, and ChatGPT (OpenAI): 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`. Google Search and Display follow the same rule, and because Google keeps an independent switch at campaign, ad group and ad level, a PAUSED create leaves the campaign it creates PAUSED at Google. On TikTok the whole campaign > ad group > ad hierarchy stays paused. On LinkedIn the whole campaign group, campaign, and creative hierarchy stays PAUSED (intendedStatus PAUSED on each). ChatGPT (OpenAI) follows the Meta rule: the pause is held on the campaign this call creates.
+         * Publish state of the created entities, on every platform. Omitted or ACTIVE publishes live (default, back-compat); PAUSED pauses only the TOP-MOST object this call creates and switches everything below it on, so one resume of that object brings the new tree live and nothing that already existed is touched: a new campaign is held paused with its ad set and ad on; with `existingCampaignId` the new ad set is held paused with its ad on; with `adSetId` the new ad itself is paused. `campaignStatus: ACTIVE` with `status: PAUSED` moves the pause down to the new ad set. LinkedIn: a held campaign group is PAUSED with its campaign and creative ACTIVE; a new campaign in an existing group stays DRAFT. X has no per-ad switch, so its lowest level is the line item. Google Performance Max and Demand Gen accept PAUSED only (the campaign is created paused).
          */
         status?: 'ACTIVE' | 'PAUSED';
         /**
-         * Meta, Google, and ChatGPT (OpenAI). Overrides `status` for the campaign level alone, so you can create a live campaign whose ad set and ad stay paused, or the reverse. Omitted, it follows `status`.
+         * Meta, Google, and ChatGPT (OpenAI). Overrides `status` for the new campaign alone. `PAUSED` holds the campaign off with its ad set and ad on; `ACTIVE` with `status: PAUSED` switches the campaign on and holds the new ad set paused (its ad on). Omitted, it follows `status`.
          */
         campaignStatus?: 'ACTIVE' | 'PAUSED';
         /**