@zernio/node 0.2.883 → 0.2.884

package/dist/index.d.mts

@@ -17056,7 +17056,12 @@ type ConnectAdsData = {
          * gives one, `details.disableReason`. Unsettled and in-grace accounts
          * are accepted, matching the `selectable` flag of `GET /v1/ads/accounts`.
          * Setting a scope also removes already synced ads from de-scoped ad
-         * accounts. For multiple accounts use `adAccountIds` instead.
+         * accounts. On Meta the scope also decides which ad accounts Zernio
+         * subscribes to ad-account webhooks: only the scoped ones, instead of
+         * every ad account the login can reach. The scope is kept when this
+         * call returns an `authUrl`, so the Meta Ads account created after
+         * OAuth is scoped (and only its scoped ad accounts synced and
+         * subscribed) from the start. For multiple accounts use `adAccountIds` instead.
          *
          */
         adAccountId?: string;
@@ -17066,8 +17071,10 @@ type ConnectAdsData = {
          * (`?adAccountIds=act_1&adAccountIds=act_2`) or comma-separate
          * (`?adAccountIds=act_1,act_2`). Persisted server-side; latest call
          * wins, and de-scoped ad accounts have their synced ads removed.
+         * On Meta only the scoped ad accounts get webhook subscriptions,
+         * including when the call starts a fresh OAuth.
          * Omitting both `adAccountId` and `adAccountIds` keeps any previously
-         * persisted scope unchanged.
+         * persisted scope unchanged (no scope means every reachable ad account).
          *
          */
         adAccountIds?: Array<(string)>;

package/dist/index.d.ts

@@ -17056,7 +17056,12 @@ type ConnectAdsData = {
          * gives one, `details.disableReason`. Unsettled and in-grace accounts
          * are accepted, matching the `selectable` flag of `GET /v1/ads/accounts`.
          * Setting a scope also removes already synced ads from de-scoped ad
-         * accounts. For multiple accounts use `adAccountIds` instead.
+         * accounts. On Meta the scope also decides which ad accounts Zernio
+         * subscribes to ad-account webhooks: only the scoped ones, instead of
+         * every ad account the login can reach. The scope is kept when this
+         * call returns an `authUrl`, so the Meta Ads account created after
+         * OAuth is scoped (and only its scoped ad accounts synced and
+         * subscribed) from the start. For multiple accounts use `adAccountIds` instead.
          *
          */
         adAccountId?: string;
@@ -17066,8 +17071,10 @@ type ConnectAdsData = {
          * (`?adAccountIds=act_1&adAccountIds=act_2`) or comma-separate
          * (`?adAccountIds=act_1,act_2`). Persisted server-side; latest call
          * wins, and de-scoped ad accounts have their synced ads removed.
+         * On Meta only the scoped ad accounts get webhook subscriptions,
+         * including when the call starts a fresh OAuth.
          * Omitting both `adAccountId` and `adAccountIds` keeps any previously
-         * persisted scope unchanged.
+         * persisted scope unchanged (no scope means every reachable ad account).
          *
          */
         adAccountIds?: Array<(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.883",
+  version: "0.2.884",
   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.883",
+  version: "0.2.884",
   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.883",
+  "version": "0.2.884",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/types.gen.ts

@@ -16102,7 +16102,12 @@ export type ConnectAdsData = {
          * gives one, `details.disableReason`. Unsettled and in-grace accounts
          * are accepted, matching the `selectable` flag of `GET /v1/ads/accounts`.
          * Setting a scope also removes already synced ads from de-scoped ad
-         * accounts. For multiple accounts use `adAccountIds` instead.
+         * accounts. On Meta the scope also decides which ad accounts Zernio
+         * subscribes to ad-account webhooks: only the scoped ones, instead of
+         * every ad account the login can reach. The scope is kept when this
+         * call returns an `authUrl`, so the Meta Ads account created after
+         * OAuth is scoped (and only its scoped ad accounts synced and
+         * subscribed) from the start. For multiple accounts use `adAccountIds` instead.
          *
          */
         adAccountId?: string;
@@ -16112,8 +16117,10 @@ export type ConnectAdsData = {
          * (`?adAccountIds=act_1&adAccountIds=act_2`) or comma-separate
          * (`?adAccountIds=act_1,act_2`). Persisted server-side; latest call
          * wins, and de-scoped ad accounts have their synced ads removed.
+         * On Meta only the scoped ad accounts get webhook subscriptions,
+         * including when the call starts a fresh OAuth.
          * Omitting both `adAccountId` and `adAccountIds` keeps any previously
-         * persisted scope unchanged.
+         * persisted scope unchanged (no scope means every reachable ad account).
          *
          */
         adAccountIds?: Array<(string)>;