@zernio/node 0.2.1484 → 0.2.1485

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.mts CHANGED
@@ -16723,6 +16723,13 @@ type SocialAccount = {
16723
16723
  *
16724
16724
  */
16725
16725
  enabled?: boolean;
16726
+ /**
16727
+ * Facebook accounts only (absent on every other platform). Whether this Facebook account syncs the Meta ads of the ad accounts it reaches, the way a `metaads` connection does.
16728
+ *
16729
+ * Off by default; set it with `PUT /v1/accounts/{accountId}`. Synced active ads count on the managed ads meter like ads from a Meta Ads connection.
16730
+ *
16731
+ */
16732
+ metaAdsSyncEnabled?: boolean;
16726
16733
  /**
16727
16734
  * End of the account's publishing cooldown. Compare it with the current time: a value in the past means the cooldown has ended (the field is cleared on the next successful publish); null means no cooldown since the last successful publish.
16728
16735
  *
@@ -28934,6 +28941,28 @@ type UpdateAccountData = {
28934
28941
  */
28935
28942
  inbox?: boolean;
28936
28943
  };
28944
+ /**
28945
+ * Facebook only (400 `invalid_field_value` on any other platform). Off by default for every Facebook account.
28946
+ *
28947
+ * `true` makes this account sync the Meta ads of the ad accounts it reaches, like a `metaads` connection.
28948
+ *
28949
+ * - The first sync starts at once (14 days, then 90 days of history in the background) and fires `account.ads.initial_sync_completed` for this `accountId` with `platform: metaads`.
28950
+ * - It then refreshes on the Meta Ads schedule.
28951
+ * - Each switch from `false` to `true` runs another initial sync and fires the webhook again. Sending `true` while it is on changes nothing.
28952
+ * - Needs `ads_management` and `ads_read` on the account (403 `reconnect_required` otherwise, with `details.requiredPermissions`).
28953
+ * - Needs ads access (403 `ads_addon_required`) and room in the managed ads allowance (403 `ads_allowance_exceeded`).
28954
+ * - While a `metaads` connection has this account as `parentAccountId`, that connection syncs the ads instead.
28955
+ *
28956
+ * Synced active ads count on the managed ads meter like ads from a Meta Ads
28957
+ * connection.
28958
+ *
28959
+ * `false` stops the sync. Ads already synced are kept, never deleted: they
28960
+ * stop updating and stop counting on the meter, and a `metaads` connection
28961
+ * of yours that reaches the same ad account takes them over. Posting, inbox
28962
+ * and comments on the account are not affected.
28963
+ *
28964
+ */
28965
+ metaAdsSyncEnabled?: boolean;
28937
28966
  };
28938
28967
  path: {
28939
28968
  accountId: string;
@@ -28952,8 +28981,12 @@ type UpdateAccountResponse = ({
28952
28981
  analytics?: boolean;
28953
28982
  inbox?: boolean;
28954
28983
  };
28984
+ /**
28985
+ * The resulting setting, returned only when the request body included `metaAdsSyncEnabled`.
28986
+ */
28987
+ metaAdsSyncEnabled?: boolean;
28955
28988
  });
28956
- type UpdateAccountError = (unknown | ErrorResponse | {
28989
+ type UpdateAccountError = (ErrorResponse | unknown | {
28957
28990
  error?: string;
28958
28991
  });
28959
28992
  type MoveAccountToProfileData = {
package/dist/index.d.ts CHANGED
@@ -16723,6 +16723,13 @@ type SocialAccount = {
16723
16723
  *
16724
16724
  */
16725
16725
  enabled?: boolean;
16726
+ /**
16727
+ * Facebook accounts only (absent on every other platform). Whether this Facebook account syncs the Meta ads of the ad accounts it reaches, the way a `metaads` connection does.
16728
+ *
16729
+ * Off by default; set it with `PUT /v1/accounts/{accountId}`. Synced active ads count on the managed ads meter like ads from a Meta Ads connection.
16730
+ *
16731
+ */
16732
+ metaAdsSyncEnabled?: boolean;
16726
16733
  /**
16727
16734
  * End of the account's publishing cooldown. Compare it with the current time: a value in the past means the cooldown has ended (the field is cleared on the next successful publish); null means no cooldown since the last successful publish.
16728
16735
  *
@@ -28934,6 +28941,28 @@ type UpdateAccountData = {
28934
28941
  */
28935
28942
  inbox?: boolean;
28936
28943
  };
28944
+ /**
28945
+ * Facebook only (400 `invalid_field_value` on any other platform). Off by default for every Facebook account.
28946
+ *
28947
+ * `true` makes this account sync the Meta ads of the ad accounts it reaches, like a `metaads` connection.
28948
+ *
28949
+ * - The first sync starts at once (14 days, then 90 days of history in the background) and fires `account.ads.initial_sync_completed` for this `accountId` with `platform: metaads`.
28950
+ * - It then refreshes on the Meta Ads schedule.
28951
+ * - Each switch from `false` to `true` runs another initial sync and fires the webhook again. Sending `true` while it is on changes nothing.
28952
+ * - Needs `ads_management` and `ads_read` on the account (403 `reconnect_required` otherwise, with `details.requiredPermissions`).
28953
+ * - Needs ads access (403 `ads_addon_required`) and room in the managed ads allowance (403 `ads_allowance_exceeded`).
28954
+ * - While a `metaads` connection has this account as `parentAccountId`, that connection syncs the ads instead.
28955
+ *
28956
+ * Synced active ads count on the managed ads meter like ads from a Meta Ads
28957
+ * connection.
28958
+ *
28959
+ * `false` stops the sync. Ads already synced are kept, never deleted: they
28960
+ * stop updating and stop counting on the meter, and a `metaads` connection
28961
+ * of yours that reaches the same ad account takes them over. Posting, inbox
28962
+ * and comments on the account are not affected.
28963
+ *
28964
+ */
28965
+ metaAdsSyncEnabled?: boolean;
28937
28966
  };
28938
28967
  path: {
28939
28968
  accountId: string;
@@ -28952,8 +28981,12 @@ type UpdateAccountResponse = ({
28952
28981
  analytics?: boolean;
28953
28982
  inbox?: boolean;
28954
28983
  };
28984
+ /**
28985
+ * The resulting setting, returned only when the request body included `metaAdsSyncEnabled`.
28986
+ */
28987
+ metaAdsSyncEnabled?: boolean;
28955
28988
  });
28956
- type UpdateAccountError = (unknown | ErrorResponse | {
28989
+ type UpdateAccountError = (ErrorResponse | unknown | {
28957
28990
  error?: string;
28958
28991
  });
28959
28992
  type MoveAccountToProfileData = {
package/dist/index.js CHANGED
@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
36
36
  // package.json
37
37
  var package_default = {
38
38
  name: "@zernio/node",
39
- version: "0.2.1484",
39
+ version: "0.2.1485",
40
40
  description: "The official Node.js library for the Zernio API",
41
41
  main: "dist/index.js",
42
42
  module: "dist/index.mjs",
package/dist/index.mjs CHANGED
@@ -5,7 +5,7 @@ var __publicField = (obj, key, value) => __defNormalProp(obj, typeof key !== "sy
5
5
  // package.json
6
6
  var package_default = {
7
7
  name: "@zernio/node",
8
- version: "0.2.1484",
8
+ version: "0.2.1485",
9
9
  description: "The official Node.js library for the Zernio API",
10
10
  main: "dist/index.js",
11
11
  module: "dist/index.mjs",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@zernio/node",
3
- "version": "0.2.1484",
3
+ "version": "0.2.1485",
4
4
  "description": "The official Node.js library for the Zernio API",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
@@ -2265,6 +2265,10 @@ export const getFollowerStats = <ThrowOnError extends boolean = false>(options?:
2265
2265
  * - Publishing and deleting posts are always available regardless of these toggles.
2266
2266
  * - Setting `xCapabilities` on a non-X account returns 400.
2267
2267
  *
2268
+ * ### Meta ads sync
2269
+ *
2270
+ * For Facebook accounts, also accepts `metaAdsSyncEnabled` to sync the Meta ads of the ad accounts the account reaches without a Meta Ads connection. See the field for what turning it on and off does.
2271
+ *
2268
2272
  */
2269
2273
  export const updateAccount = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<UpdateAccountData, ThrowOnError>) => {
2270
2274
  return (options?.client ?? client).put<UpdateAccountResponse, UpdateAccountError, ThrowOnError>({
@@ -15086,6 +15086,13 @@ export type SocialAccount = {
15086
15086
  *
15087
15087
  */
15088
15088
  enabled?: boolean;
15089
+ /**
15090
+ * Facebook accounts only (absent on every other platform). Whether this Facebook account syncs the Meta ads of the ad accounts it reaches, the way a `metaads` connection does.
15091
+ *
15092
+ * Off by default; set it with `PUT /v1/accounts/{accountId}`. Synced active ads count on the managed ads meter like ads from a Meta Ads connection.
15093
+ *
15094
+ */
15095
+ metaAdsSyncEnabled?: boolean;
15089
15096
  /**
15090
15097
  * End of the account's publishing cooldown. Compare it with the current time: a value in the past means the cooldown has ended (the field is cleared on the next successful publish); null means no cooldown since the last successful publish.
15091
15098
  *
@@ -27948,6 +27955,28 @@ export type UpdateAccountData = {
27948
27955
  */
27949
27956
  inbox?: boolean;
27950
27957
  };
27958
+ /**
27959
+ * Facebook only (400 `invalid_field_value` on any other platform). Off by default for every Facebook account.
27960
+ *
27961
+ * `true` makes this account sync the Meta ads of the ad accounts it reaches, like a `metaads` connection.
27962
+ *
27963
+ * - The first sync starts at once (14 days, then 90 days of history in the background) and fires `account.ads.initial_sync_completed` for this `accountId` with `platform: metaads`.
27964
+ * - It then refreshes on the Meta Ads schedule.
27965
+ * - Each switch from `false` to `true` runs another initial sync and fires the webhook again. Sending `true` while it is on changes nothing.
27966
+ * - Needs `ads_management` and `ads_read` on the account (403 `reconnect_required` otherwise, with `details.requiredPermissions`).
27967
+ * - Needs ads access (403 `ads_addon_required`) and room in the managed ads allowance (403 `ads_allowance_exceeded`).
27968
+ * - While a `metaads` connection has this account as `parentAccountId`, that connection syncs the ads instead.
27969
+ *
27970
+ * Synced active ads count on the managed ads meter like ads from a Meta Ads
27971
+ * connection.
27972
+ *
27973
+ * `false` stops the sync. Ads already synced are kept, never deleted: they
27974
+ * stop updating and stop counting on the meter, and a `metaads` connection
27975
+ * of yours that reaches the same ad account takes them over. Posting, inbox
27976
+ * and comments on the account are not affected.
27977
+ *
27978
+ */
27979
+ metaAdsSyncEnabled?: boolean;
27951
27980
  };
27952
27981
  path: {
27953
27982
  accountId: string;
@@ -27967,9 +27996,13 @@ export type UpdateAccountResponse = ({
27967
27996
  analytics?: boolean;
27968
27997
  inbox?: boolean;
27969
27998
  };
27999
+ /**
28000
+ * The resulting setting, returned only when the request body included `metaAdsSyncEnabled`.
28001
+ */
28002
+ metaAdsSyncEnabled?: boolean;
27970
28003
  });
27971
28004
 
27972
- export type UpdateAccountError = (unknown | ErrorResponse | {
28005
+ export type UpdateAccountError = (ErrorResponse | unknown | {
27973
28006
  error?: string;
27974
28007
  });
27975
28008