@zernio/node 0.2.1488 → 0.2.1490

package/dist/index.d.mts

@@ -52189,6 +52189,13 @@ type DuplicateAdCampaignResponse = ({
     adIdMap?: {
         [key: string]: (string);
     };
+    /**
+     * The copy exists on the platform in all three cases.
+     *
+     * - `triggered`: an ads sync started and runs after this response, so the copy may not be readable through Zernio yet.
+     * - `skipped`: no sync started, so the copy appears on a later scheduled sync.
+     * - `failed`: the sync could not start. A sync that errors after the response is not reported here.
+     */
     discovery?: 'triggered' | 'skipped' | 'failed';
     /**
      * Platform-native response from the copy (TikTok and LinkedIn). Absent on Meta, which returns `adSetIdMap` and `adIdMap` instead.
@@ -52791,6 +52798,13 @@ type DuplicateAdSetResponse = ({
     adIdMap?: {
         [key: string]: (string);
     };
+    /**
+     * The copy exists on the platform in all three cases.
+     *
+     * - `triggered`: an ads sync started and runs after this response, so the copy may not be readable through Zernio yet.
+     * - `skipped`: no sync started, so the copy appears on a later scheduled sync.
+     * - `failed`: the sync could not start. A sync that errors after the response is not reported here.
+     */
     discovery?: 'triggered' | 'skipped' | 'failed';
     /**
      * Platform-native response from the copy (TikTok). Absent on Meta, which returns `adIdMap` instead.
@@ -52855,6 +52869,13 @@ type DuplicateAdResponse = ({
      * Platform ID of the new ad
      */
     copiedAdId?: string;
+    /**
+     * The copy exists on the platform in all three cases.
+     *
+     * - `triggered`: an ads sync started and runs after this response, so the copy may not be readable through Zernio yet.
+     * - `skipped`: no sync started, so the copy appears on a later scheduled sync.
+     * - `failed`: the sync could not start. A sync that errors after the response is not reported here.
+     */
     discovery?: 'triggered' | 'skipped' | 'failed';
     raw?: {
         [key: string]: unknown;
@@ -58114,7 +58135,7 @@ type ListAdAccountsResponse = ({
          */
         minimumDailyBudget?: number;
         /**
-         * Meta only. Meta's `funding_source` ID for the ad account, forwarded unchanged. ABSENT both when this connection's token cannot see billing and when the account has no payment method; read `billingStatus` to tell the two apart.
+         * Meta only. Meta's `funding_source` ID for the ad account, forwarded unchanged. ABSENT when this connection's token cannot see billing, when the account has no payment method, and for accounts paid through Business Billing Hub, which still create ads. Absence alone is not a missing payment method.
          */
         fundingSource?: string;
         /**
@@ -58141,10 +58162,10 @@ type ListAdAccountsResponse = ({
         /**
          * Meta only. Whether the ad account has a payment method:
          *
-         * - `missing`: `accountStatus` is `3` (UNSETTLED) or `9` (IN_GRACE_PERIOD), `disableReason` is `3` (RISK_PAYMENT), or the connected person has the MANAGE task on the account (admin, who always sees billing) and Meta returns no funding source.
+         * - `missing`: `accountStatus` is `3` (UNSETTLED) or `9` (IN_GRACE_PERIOD), or `disableReason` is `3` (RISK_PAYMENT).
          * - `missing`, effect: ad creation fails at the ad step with Meta code 100 / subcode 1359188. Add a payment method in Meta's Billing & payments center.
          * - `ok`: Meta returns a funding source. This is presence, not validity: Meta can still refuse the card or balance at ad creation.
-         * - `unknown`: the connected person is not an admin of the account, or the token cannot read the billing fields.
+         * - `unknown`: Meta returns no funding source. The token may not see billing, the account may have no payment method, or it is paid through Business Billing Hub (Meta omits the funding source there even for admins). Meta decides at ad creation.
          *
          */
         billingStatus?: 'ok' | 'missing' | 'unknown';

package/dist/index.d.ts

@@ -52189,6 +52189,13 @@ type DuplicateAdCampaignResponse = ({
     adIdMap?: {
         [key: string]: (string);
     };
+    /**
+     * The copy exists on the platform in all three cases.
+     *
+     * - `triggered`: an ads sync started and runs after this response, so the copy may not be readable through Zernio yet.
+     * - `skipped`: no sync started, so the copy appears on a later scheduled sync.
+     * - `failed`: the sync could not start. A sync that errors after the response is not reported here.
+     */
     discovery?: 'triggered' | 'skipped' | 'failed';
     /**
      * Platform-native response from the copy (TikTok and LinkedIn). Absent on Meta, which returns `adSetIdMap` and `adIdMap` instead.
@@ -52791,6 +52798,13 @@ type DuplicateAdSetResponse = ({
     adIdMap?: {
         [key: string]: (string);
     };
+    /**
+     * The copy exists on the platform in all three cases.
+     *
+     * - `triggered`: an ads sync started and runs after this response, so the copy may not be readable through Zernio yet.
+     * - `skipped`: no sync started, so the copy appears on a later scheduled sync.
+     * - `failed`: the sync could not start. A sync that errors after the response is not reported here.
+     */
     discovery?: 'triggered' | 'skipped' | 'failed';
     /**
      * Platform-native response from the copy (TikTok). Absent on Meta, which returns `adIdMap` instead.
@@ -52855,6 +52869,13 @@ type DuplicateAdResponse = ({
      * Platform ID of the new ad
      */
     copiedAdId?: string;
+    /**
+     * The copy exists on the platform in all three cases.
+     *
+     * - `triggered`: an ads sync started and runs after this response, so the copy may not be readable through Zernio yet.
+     * - `skipped`: no sync started, so the copy appears on a later scheduled sync.
+     * - `failed`: the sync could not start. A sync that errors after the response is not reported here.
+     */
     discovery?: 'triggered' | 'skipped' | 'failed';
     raw?: {
         [key: string]: unknown;
@@ -58114,7 +58135,7 @@ type ListAdAccountsResponse = ({
          */
         minimumDailyBudget?: number;
         /**
-         * Meta only. Meta's `funding_source` ID for the ad account, forwarded unchanged. ABSENT both when this connection's token cannot see billing and when the account has no payment method; read `billingStatus` to tell the two apart.
+         * Meta only. Meta's `funding_source` ID for the ad account, forwarded unchanged. ABSENT when this connection's token cannot see billing, when the account has no payment method, and for accounts paid through Business Billing Hub, which still create ads. Absence alone is not a missing payment method.
          */
         fundingSource?: string;
         /**
@@ -58141,10 +58162,10 @@ type ListAdAccountsResponse = ({
         /**
          * Meta only. Whether the ad account has a payment method:
          *
-         * - `missing`: `accountStatus` is `3` (UNSETTLED) or `9` (IN_GRACE_PERIOD), `disableReason` is `3` (RISK_PAYMENT), or the connected person has the MANAGE task on the account (admin, who always sees billing) and Meta returns no funding source.
+         * - `missing`: `accountStatus` is `3` (UNSETTLED) or `9` (IN_GRACE_PERIOD), or `disableReason` is `3` (RISK_PAYMENT).
          * - `missing`, effect: ad creation fails at the ad step with Meta code 100 / subcode 1359188. Add a payment method in Meta's Billing & payments center.
          * - `ok`: Meta returns a funding source. This is presence, not validity: Meta can still refuse the card or balance at ad creation.
-         * - `unknown`: the connected person is not an admin of the account, or the token cannot read the billing fields.
+         * - `unknown`: Meta returns no funding source. The token may not see billing, the account may have no payment method, or it is paid through Business Billing Hub (Meta omits the funding source there even for admins). Meta decides at ad creation.
          *
          */
         billingStatus?: 'ok' | 'missing' | 'unknown';

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -13115,7 +13115,9 @@ export const bulkUpdateAdCampaignStatus = <ThrowOnError extends boolean = false>
  *
  * ### Sync
  *
- * The new hierarchy is asynchronous to materialize in our DB, and we trigger sync discovery automatically. Set `syncAfter: false` to skip and poll `/v1/ads/tree` on your own cadence.
+ * The copy exists on the platform when this call returns. The new hierarchy reaches our DB through a sync discovery that starts automatically and runs after the response, usually within a few minutes.
+ *
+ * Poll `/v1/ads/tree` until it appears; until then, calls that take a copied id return 404, so retry them. Set `syncAfter: false` to skip the sync; the copy then appears on a later scheduled sync.
  *
  */
 export const duplicateAdCampaign = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<DuplicateAdCampaignData, ThrowOnError>) => {
@@ -13319,7 +13321,7 @@ export const createAdSet = <ThrowOnError extends boolean = false>(options: Optio
  * - So an ad set with any number of ads copies: Meta refuses a single deep copy of 3 or more objects.
  * - `statusOption` applies to the ad set and every ad.
  * - If an ad copy fails, the partial ad set copy is deleted and the request fails with Meta's error.
- * - Sync discovery is triggered automatically (`syncAfter: false` to skip).
+ * - A sync discovery starts automatically and runs after the response (`syncAfter: false` to skip). The copy is readable through Zernio once it finishes, usually within a few minutes. Until then, calls that take a copied id return 404, so retry them.
  *
  * TikTok: the ad group is read and recreated under the campaign with its targeting, bidding,
  * budget and schedule (start reset to now); `deepCopy: true` recreates its ads too (default
@@ -13342,7 +13344,7 @@ export const duplicateAdSet = <ThrowOnError extends boolean = false>(options: Op
  *
  * - `adSetId` retargets the copy into another ad set; omitted = the source's own ad set.
  * - Accepts the Zernio ad id or the platform ad id.
- * - Sync discovery is triggered automatically (`syncAfter: false` to skip).
+ * - A sync discovery starts automatically and runs after the response (`syncAfter: false` to skip). The copy is readable through Zernio once it finishes, usually within a few minutes. Until then, calls that take a copied id return 404, so retry them.
  *
  * ### Creative settings
  *

package/src/generated/types.gen.ts

@@ -53013,6 +53013,13 @@ export type DuplicateAdCampaignResponse = ({
     adIdMap?: {
         [key: string]: (string);
     };
+    /**
+     * The copy exists on the platform in all three cases.
+     *
+     * - `triggered`: an ads sync started and runs after this response, so the copy may not be readable through Zernio yet.
+     * - `skipped`: no sync started, so the copy appears on a later scheduled sync.
+     * - `failed`: the sync could not start. A sync that errors after the response is not reported here.
+     */
     discovery?: 'triggered' | 'skipped' | 'failed';
     /**
      * Platform-native response from the copy (TikTok and LinkedIn). Absent on Meta, which returns `adSetIdMap` and `adIdMap` instead.
@@ -53630,6 +53637,13 @@ export type DuplicateAdSetResponse = ({
     adIdMap?: {
         [key: string]: (string);
     };
+    /**
+     * The copy exists on the platform in all three cases.
+     *
+     * - `triggered`: an ads sync started and runs after this response, so the copy may not be readable through Zernio yet.
+     * - `skipped`: no sync started, so the copy appears on a later scheduled sync.
+     * - `failed`: the sync could not start. A sync that errors after the response is not reported here.
+     */
     discovery?: 'triggered' | 'skipped' | 'failed';
     /**
      * Platform-native response from the copy (TikTok). Absent on Meta, which returns `adIdMap` instead.
@@ -53697,6 +53711,13 @@ export type DuplicateAdResponse = ({
      * Platform ID of the new ad
      */
     copiedAdId?: string;
+    /**
+     * The copy exists on the platform in all three cases.
+     *
+     * - `triggered`: an ads sync started and runs after this response, so the copy may not be readable through Zernio yet.
+     * - `skipped`: no sync started, so the copy appears on a later scheduled sync.
+     * - `failed`: the sync could not start. A sync that errors after the response is not reported here.
+     */
     discovery?: 'triggered' | 'skipped' | 'failed';
     raw?: {
         [key: string]: unknown;
@@ -59301,7 +59322,7 @@ export type ListAdAccountsResponse = ({
          */
         minimumDailyBudget?: number;
         /**
-         * Meta only. Meta's `funding_source` ID for the ad account, forwarded unchanged. ABSENT both when this connection's token cannot see billing and when the account has no payment method; read `billingStatus` to tell the two apart.
+         * Meta only. Meta's `funding_source` ID for the ad account, forwarded unchanged. ABSENT when this connection's token cannot see billing, when the account has no payment method, and for accounts paid through Business Billing Hub, which still create ads. Absence alone is not a missing payment method.
          */
         fundingSource?: string;
         /**
@@ -59328,10 +59349,10 @@ export type ListAdAccountsResponse = ({
         /**
          * Meta only. Whether the ad account has a payment method:
          *
-         * - `missing`: `accountStatus` is `3` (UNSETTLED) or `9` (IN_GRACE_PERIOD), `disableReason` is `3` (RISK_PAYMENT), or the connected person has the MANAGE task on the account (admin, who always sees billing) and Meta returns no funding source.
+         * - `missing`: `accountStatus` is `3` (UNSETTLED) or `9` (IN_GRACE_PERIOD), or `disableReason` is `3` (RISK_PAYMENT).
          * - `missing`, effect: ad creation fails at the ad step with Meta code 100 / subcode 1359188. Add a payment method in Meta's Billing & payments center.
          * - `ok`: Meta returns a funding source. This is presence, not validity: Meta can still refuse the card or balance at ad creation.
-         * - `unknown`: the connected person is not an admin of the account, or the token cannot read the billing fields.
+         * - `unknown`: Meta returns no funding source. The token may not see billing, the account may have no payment method, or it is paid through Business Billing Hub (Meta omits the funding source there even for admins). Meta decides at ad creation.
          *
          */
         billingStatus?: 'ok' | 'missing' | 'unknown';