@zernio/node 0.2.1489 → 0.2.1490

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
@@ -58135,7 +58135,7 @@ type ListAdAccountsResponse = ({
58135
58135
  */
58136
58136
  minimumDailyBudget?: number;
58137
58137
  /**
58138
- * 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.
58138
+ * 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.
58139
58139
  */
58140
58140
  fundingSource?: string;
58141
58141
  /**
@@ -58162,10 +58162,10 @@ type ListAdAccountsResponse = ({
58162
58162
  /**
58163
58163
  * Meta only. Whether the ad account has a payment method:
58164
58164
  *
58165
- * - `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.
58165
+ * - `missing`: `accountStatus` is `3` (UNSETTLED) or `9` (IN_GRACE_PERIOD), or `disableReason` is `3` (RISK_PAYMENT).
58166
58166
  * - `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.
58167
58167
  * - `ok`: Meta returns a funding source. This is presence, not validity: Meta can still refuse the card or balance at ad creation.
58168
- * - `unknown`: the connected person is not an admin of the account, or the token cannot read the billing fields.
58168
+ * - `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.
58169
58169
  *
58170
58170
  */
58171
58171
  billingStatus?: 'ok' | 'missing' | 'unknown';
package/dist/index.d.ts CHANGED
@@ -58135,7 +58135,7 @@ type ListAdAccountsResponse = ({
58135
58135
  */
58136
58136
  minimumDailyBudget?: number;
58137
58137
  /**
58138
- * 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.
58138
+ * 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.
58139
58139
  */
58140
58140
  fundingSource?: string;
58141
58141
  /**
@@ -58162,10 +58162,10 @@ type ListAdAccountsResponse = ({
58162
58162
  /**
58163
58163
  * Meta only. Whether the ad account has a payment method:
58164
58164
  *
58165
- * - `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.
58165
+ * - `missing`: `accountStatus` is `3` (UNSETTLED) or `9` (IN_GRACE_PERIOD), or `disableReason` is `3` (RISK_PAYMENT).
58166
58166
  * - `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.
58167
58167
  * - `ok`: Meta returns a funding source. This is presence, not validity: Meta can still refuse the card or balance at ad creation.
58168
- * - `unknown`: the connected person is not an admin of the account, or the token cannot read the billing fields.
58168
+ * - `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.
58169
58169
  *
58170
58170
  */
58171
58171
  billingStatus?: 'ok' | 'missing' | 'unknown';
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.1489",
39
+ version: "0.2.1490",
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.1489",
8
+ version: "0.2.1490",
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.1489",
3
+ "version": "0.2.1490",
4
4
  "description": "The official Node.js library for the Zernio API",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
@@ -59322,7 +59322,7 @@ export type ListAdAccountsResponse = ({
59322
59322
  */
59323
59323
  minimumDailyBudget?: number;
59324
59324
  /**
59325
- * 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.
59325
+ * 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.
59326
59326
  */
59327
59327
  fundingSource?: string;
59328
59328
  /**
@@ -59349,10 +59349,10 @@ export type ListAdAccountsResponse = ({
59349
59349
  /**
59350
59350
  * Meta only. Whether the ad account has a payment method:
59351
59351
  *
59352
- * - `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.
59352
+ * - `missing`: `accountStatus` is `3` (UNSETTLED) or `9` (IN_GRACE_PERIOD), or `disableReason` is `3` (RISK_PAYMENT).
59353
59353
  * - `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.
59354
59354
  * - `ok`: Meta returns a funding source. This is presence, not validity: Meta can still refuse the card or balance at ad creation.
59355
- * - `unknown`: the connected person is not an admin of the account, or the token cannot read the billing fields.
59355
+ * - `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.
59356
59356
  *
59357
59357
  */
59358
59358
  billingStatus?: 'ok' | 'missing' | 'unknown';