@zernio/node 0.2.1027 → 0.2.1028

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.
Files changed (6) hide show
  1. package/dist/index.d.mts +20 -6
  2. package/dist/index.d.ts +20 -6
  3. package/dist/index.js +1 -1
  4. package/dist/index.mjs +1 -1
  5. package/package.json +1 -1
  6. package/src/generated/types.gen.ts +20 -6
package/dist/index.d.mts CHANGED
@@ -19186,11 +19186,18 @@ type GetAllAccountsHealthResponse = ({
19186
19186
  needsReconnect?: boolean;
19187
19187
  issues?: Array<(string)>;
19188
19188
  /**
19189
- * Observed from Meta's own error subcodes on our own sends (2534122, 1893063, 2534029), not a live probe. Set on the first refused send and cleared when a later send succeeds, so it lags reality by one send in each direction.
19189
+ * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction.
19190
19190
  */
19191
19191
  messagingRestriction?: {
19192
- subcode?: number;
19193
- message?: string;
19192
+ /**
19193
+ * WhatsApp Cloud API error code. Null on Facebook and Instagram.
19194
+ */
19195
+ code?: (number) | null;
19196
+ /**
19197
+ * Meta error subcode (Facebook and Instagram). Null on WhatsApp.
19198
+ */
19199
+ subcode?: (number) | null;
19200
+ message?: (string) | null;
19194
19201
  firstSeenAt?: string;
19195
19202
  lastSeenAt?: string;
19196
19203
  } | null;
@@ -19331,11 +19338,18 @@ type GetAccountHealthResponse = ({
19331
19338
  */
19332
19339
  recommendations?: Array<(string)>;
19333
19340
  /**
19334
- * Observed from Meta's own error subcodes on our own sends (2534122, 1893063, 2534029), not a live probe. Set on the first refused send and cleared when a later send succeeds, so it lags reality by one send in each direction.
19341
+ * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction.
19335
19342
  */
19336
19343
  messagingRestriction?: {
19337
- subcode?: number;
19338
- message?: string;
19344
+ /**
19345
+ * WhatsApp Cloud API error code. Null on Facebook and Instagram.
19346
+ */
19347
+ code?: (number) | null;
19348
+ /**
19349
+ * Meta error subcode (Facebook and Instagram). Null on WhatsApp.
19350
+ */
19351
+ subcode?: (number) | null;
19352
+ message?: (string) | null;
19339
19353
  firstSeenAt?: string;
19340
19354
  lastSeenAt?: string;
19341
19355
  } | null;
package/dist/index.d.ts CHANGED
@@ -19186,11 +19186,18 @@ type GetAllAccountsHealthResponse = ({
19186
19186
  needsReconnect?: boolean;
19187
19187
  issues?: Array<(string)>;
19188
19188
  /**
19189
- * Observed from Meta's own error subcodes on our own sends (2534122, 1893063, 2534029), not a live probe. Set on the first refused send and cleared when a later send succeeds, so it lags reality by one send in each direction.
19189
+ * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction.
19190
19190
  */
19191
19191
  messagingRestriction?: {
19192
- subcode?: number;
19193
- message?: string;
19192
+ /**
19193
+ * WhatsApp Cloud API error code. Null on Facebook and Instagram.
19194
+ */
19195
+ code?: (number) | null;
19196
+ /**
19197
+ * Meta error subcode (Facebook and Instagram). Null on WhatsApp.
19198
+ */
19199
+ subcode?: (number) | null;
19200
+ message?: (string) | null;
19194
19201
  firstSeenAt?: string;
19195
19202
  lastSeenAt?: string;
19196
19203
  } | null;
@@ -19331,11 +19338,18 @@ type GetAccountHealthResponse = ({
19331
19338
  */
19332
19339
  recommendations?: Array<(string)>;
19333
19340
  /**
19334
- * Observed from Meta's own error subcodes on our own sends (2534122, 1893063, 2534029), not a live probe. Set on the first refused send and cleared when a later send succeeds, so it lags reality by one send in each direction.
19341
+ * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction.
19335
19342
  */
19336
19343
  messagingRestriction?: {
19337
- subcode?: number;
19338
- message?: string;
19344
+ /**
19345
+ * WhatsApp Cloud API error code. Null on Facebook and Instagram.
19346
+ */
19347
+ code?: (number) | null;
19348
+ /**
19349
+ * Meta error subcode (Facebook and Instagram). Null on WhatsApp.
19350
+ */
19351
+ subcode?: (number) | null;
19352
+ message?: (string) | null;
19339
19353
  firstSeenAt?: string;
19340
19354
  lastSeenAt?: string;
19341
19355
  } | null;
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.1027",
39
+ version: "0.2.1028",
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.1027",
8
+ version: "0.2.1028",
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.1027",
3
+ "version": "0.2.1028",
4
4
  "description": "The official Node.js library for the Zernio API",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
package/src/generated/types.gen.ts CHANGED
@@ -18065,11 +18065,18 @@ export type GetAllAccountsHealthResponse = ({
18065
18065
  needsReconnect?: boolean;
18066
18066
  issues?: Array<(string)>;
18067
18067
  /**
18068
- * Observed from Meta's own error subcodes on our own sends (2534122, 1893063, 2534029), not a live probe. Set on the first refused send and cleared when a later send succeeds, so it lags reality by one send in each direction.
18068
+ * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction.
18069
18069
  */
18070
18070
  messagingRestriction?: {
18071
- subcode?: number;
18072
- message?: string;
18071
+ /**
18072
+ * WhatsApp Cloud API error code. Null on Facebook and Instagram.
18073
+ */
18074
+ code?: (number) | null;
18075
+ /**
18076
+ * Meta error subcode (Facebook and Instagram). Null on WhatsApp.
18077
+ */
18078
+ subcode?: (number) | null;
18079
+ message?: (string) | null;
18073
18080
  firstSeenAt?: string;
18074
18081
  lastSeenAt?: string;
18075
18082
  } | null;
@@ -18222,11 +18229,18 @@ export type GetAccountHealthResponse = ({
18222
18229
  */
18223
18230
  recommendations?: Array<(string)>;
18224
18231
  /**
18225
- * Observed from Meta's own error subcodes on our own sends (2534122, 1893063, 2534029), not a live probe. Set on the first refused send and cleared when a later send succeeds, so it lags reality by one send in each direction.
18232
+ * Observed from Meta's own errors on our own sends, not a live probe. Facebook/Instagram: error subcodes 2534122, 1893063, 2534029, set on the first refused send and cleared when a later send succeeds. WhatsApp: Cloud API error codes 131042 (payment or eligibility issue), 131031 (Business Account locked) and 368 (policy block), set when a send or a delivery status fails with one and cleared when a later message is delivered. It lags reality by one message in each direction.
18226
18233
  */
18227
18234
  messagingRestriction?: {
18228
- subcode?: number;
18229
- message?: string;
18235
+ /**
18236
+ * WhatsApp Cloud API error code. Null on Facebook and Instagram.
18237
+ */
18238
+ code?: (number) | null;
18239
+ /**
18240
+ * Meta error subcode (Facebook and Instagram). Null on WhatsApp.
18241
+ */
18242
+ subcode?: (number) | null;
18243
+ message?: (string) | null;
18230
18244
  firstSeenAt?: string;
18231
18245
  lastSeenAt?: string;
18232
18246
  } | null;