@zernio/node 0.2.662 → 0.2.664

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
@@ -8939,7 +8939,7 @@ type event15 = 'message.delivered' | 'message.read' | 'message.failed';
8939
8939
  /**
8940
8940
  * Webhook payload for message.edited events. Fires when the sender
8941
8941
  * edits a previously-sent message. Supported platforms: Instagram,
8942
- * Facebook Messenger, Telegram. The message object reflects the
8942
+ * Facebook Messenger, Telegram, WhatsApp. The message object reflects the
8943
8943
  * LATEST state; editHistory contains every prior version in order
8944
8944
  * (oldest first), so the last entry is the version immediately before
8945
8945
  * the current content.
@@ -19928,6 +19928,38 @@ type SendInboxMessageResponse = ({
19928
19928
  type?: string;
19929
19929
  url?: string;
19930
19930
  }>;
19931
+ /**
19932
+ * Facebook/Instagram only. Present when an attachment and text were both requested: Meta has no single body shape for both, so the send is two Meta messages under the hood. First element === messageId (the attachment); second is the follow-up text.
19933
+ */
19934
+ messageIds?: Array<(string)>;
19935
+ /**
19936
+ * Facebook/Instagram only. The attachment was delivered but the follow-up text message was rejected by Meta and was not stored; the response is still a 200 because the attachment send succeeded.
19937
+ */
19938
+ partialFailure?: {
19939
+ part?: 'text';
19940
+ error?: string;
19941
+ /**
19942
+ * Meta's own diagnostic fields for the rejected follow-up, same shape as the 400 response's platformError.
19943
+ */
19944
+ platformError?: {
19945
+ /**
19946
+ * Meta error code
19947
+ */
19948
+ code?: number;
19949
+ /**
19950
+ * Meta error_subcode
19951
+ */
19952
+ subcode?: number;
19953
+ /**
19954
+ * Meta fbtrace_id, quote this in a Meta bug report
19955
+ */
19956
+ fbtraceId?: string;
19957
+ /**
19958
+ * Meta error type (e.g. OAuthException)
19959
+ */
19960
+ type?: string;
19961
+ };
19962
+ };
19931
19963
  };
19932
19964
  });
19933
19965
  type SendInboxMessageError = ({
package/dist/index.d.ts CHANGED
@@ -8939,7 +8939,7 @@ type event15 = 'message.delivered' | 'message.read' | 'message.failed';
8939
8939
  /**
8940
8940
  * Webhook payload for message.edited events. Fires when the sender
8941
8941
  * edits a previously-sent message. Supported platforms: Instagram,
8942
- * Facebook Messenger, Telegram. The message object reflects the
8942
+ * Facebook Messenger, Telegram, WhatsApp. The message object reflects the
8943
8943
  * LATEST state; editHistory contains every prior version in order
8944
8944
  * (oldest first), so the last entry is the version immediately before
8945
8945
  * the current content.
@@ -19928,6 +19928,38 @@ type SendInboxMessageResponse = ({
19928
19928
  type?: string;
19929
19929
  url?: string;
19930
19930
  }>;
19931
+ /**
19932
+ * Facebook/Instagram only. Present when an attachment and text were both requested: Meta has no single body shape for both, so the send is two Meta messages under the hood. First element === messageId (the attachment); second is the follow-up text.
19933
+ */
19934
+ messageIds?: Array<(string)>;
19935
+ /**
19936
+ * Facebook/Instagram only. The attachment was delivered but the follow-up text message was rejected by Meta and was not stored; the response is still a 200 because the attachment send succeeded.
19937
+ */
19938
+ partialFailure?: {
19939
+ part?: 'text';
19940
+ error?: string;
19941
+ /**
19942
+ * Meta's own diagnostic fields for the rejected follow-up, same shape as the 400 response's platformError.
19943
+ */
19944
+ platformError?: {
19945
+ /**
19946
+ * Meta error code
19947
+ */
19948
+ code?: number;
19949
+ /**
19950
+ * Meta error_subcode
19951
+ */
19952
+ subcode?: number;
19953
+ /**
19954
+ * Meta fbtrace_id, quote this in a Meta bug report
19955
+ */
19956
+ fbtraceId?: string;
19957
+ /**
19958
+ * Meta error type (e.g. OAuthException)
19959
+ */
19960
+ type?: string;
19961
+ };
19962
+ };
19931
19963
  };
19932
19964
  });
19933
19965
  type SendInboxMessageError = ({
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.662",
39
+ version: "0.2.664",
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.662",
8
+ version: "0.2.664",
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.662",
3
+ "version": "0.2.664",
4
4
  "description": "The official Node.js library for the Zernio API",
5
5
  "main": "dist/index.js",
6
6
  "module": "dist/index.mjs",
@@ -7891,7 +7891,7 @@ export type event15 = 'message.delivered' | 'message.read' | 'message.failed';
7891
7891
  /**
7892
7892
  * Webhook payload for message.edited events. Fires when the sender
7893
7893
  * edits a previously-sent message. Supported platforms: Instagram,
7894
- * Facebook Messenger, Telegram. The message object reflects the
7894
+ * Facebook Messenger, Telegram, WhatsApp. The message object reflects the
7895
7895
  * LATEST state; editHistory contains every prior version in order
7896
7896
  * (oldest first), so the last entry is the version immediately before
7897
7897
  * the current content.
@@ -19583,6 +19583,38 @@ export type SendInboxMessageResponse = ({
19583
19583
  type?: string;
19584
19584
  url?: string;
19585
19585
  }>;
19586
+ /**
19587
+ * Facebook/Instagram only. Present when an attachment and text were both requested: Meta has no single body shape for both, so the send is two Meta messages under the hood. First element === messageId (the attachment); second is the follow-up text.
19588
+ */
19589
+ messageIds?: Array<(string)>;
19590
+ /**
19591
+ * Facebook/Instagram only. The attachment was delivered but the follow-up text message was rejected by Meta and was not stored; the response is still a 200 because the attachment send succeeded.
19592
+ */
19593
+ partialFailure?: {
19594
+ part?: 'text';
19595
+ error?: string;
19596
+ /**
19597
+ * Meta's own diagnostic fields for the rejected follow-up, same shape as the 400 response's platformError.
19598
+ */
19599
+ platformError?: {
19600
+ /**
19601
+ * Meta error code
19602
+ */
19603
+ code?: number;
19604
+ /**
19605
+ * Meta error_subcode
19606
+ */
19607
+ subcode?: number;
19608
+ /**
19609
+ * Meta fbtrace_id, quote this in a Meta bug report
19610
+ */
19611
+ fbtraceId?: string;
19612
+ /**
19613
+ * Meta error type (e.g. OAuthException)
19614
+ */
19615
+ type?: string;
19616
+ };
19617
+ };
19586
19618
  };
19587
19619
  });
19588
19620