@zernio/node 0.2.889 → 0.2.891

package/dist/index.d.mts

@@ -11120,7 +11120,15 @@ type WebhookPayloadMessage = {
         text: (string) | null;
         attachments: Array<{
             /**
-             * Attachment type (image, video, file, sticker, audio, share)
+             * Attachment type (image, video, file, sticker, audio, share).
+             *
+             * Instagram and Facebook deliver a shared reel, post or ad with no
+             * type of its own (Meta's `unsupported_type`). Zernio resolves it
+             * from the media's Content-Type at ingest, so it arrives as `image`,
+             * `video`, `audio` or `file` with `originalType: "unsupported_type"`.
+             * `type: "unsupported_type"` itself is emitted only when the CDN
+             * could not be classified in time; the `url` still works.
+             *
              */
             type: string;
             /**
@@ -11135,8 +11143,21 @@ type WebhookPayloadMessage = {
              * unrecognized type as a generic document shows your agent
              * "document received" for what is usually a lead.
              *
+             * `originalType: "unsupported_type"` marks a share Meta did not
+             * classify, resolved by content type. **Download it on receipt**:
+             * Meta answers `is_unsupported` with no attachments when the
+             * message node is read back, so the attachment-resolve endpoint
+             * cannot re-mint this url once it expires.
+             *
              */
             originalType?: string;
+            /**
+             * MIME type of the media when Zernio knows it. On Instagram and
+             * Facebook it is set for shares resolved by content type
+             * (`originalType: "unsupported_type"`).
+             *
+             */
+            mimeType?: string;
             /**
              * Where to fetch the attachment. **The contract differs by platform.**
              *
@@ -23441,17 +23462,24 @@ type GetInboxConversationMessagesResponse = ({
         createdAt?: string;
         attachments?: Array<{
             id?: string;
-            type?: 'image' | 'video' | 'audio' | 'file' | 'sticker' | 'share' | 'template';
             /**
-             * Instagram and Facebook only, and present only when it differs from `type`. Meta's own type before normalization: `ig_reel` and `reel` become `video`, while `ig_post`, `post`, `ig_story` and `story_mention` become `share`. A story mention is `type: "share"` with `originalType: "story_mention"`; render on this field, since `share` alone is ambiguous.
+             * On Instagram and Facebook a shared reel, post or ad reaches Zernio with no type of its own (Meta's `unsupported_type`) and is resolved from the media's Content-Type at ingest into `image`, `video`, `audio` or `file` with `originalType: "unsupported_type"`. `unsupported_type` is returned only when the CDN could not be classified in time.
+             */
+            type?: 'image' | 'video' | 'audio' | 'file' | 'sticker' | 'share' | 'template' | 'unsupported_type';
+            /**
+             * Instagram and Facebook only, and present only when it differs from `type`. Meta's own type before normalization: `ig_reel` and `reel` become `video`, while `ig_post`, `post`, `ig_story` and `story_mention` become `share`. A story mention is `type: "share"` with `originalType: "story_mention"`; render on this field, since `share` alone is ambiguous. `originalType: "unsupported_type"` marks a share Meta did not classify, resolved by content type: `refreshUrl` cannot re-mint it (Meta answers `is_unsupported` with no attachments for the message node), so download it when the `message.received` webhook arrives.
              */
             originalType?: string;
+            /**
+             * MIME type of the media when Zernio knows it. On Instagram and Facebook it is set for shares resolved by content type (`originalType: "unsupported_type"`).
+             */
+            mimeType?: string;
             /**
              * Direct media link. On Instagram and Facebook this is a signed Meta CDN url that EXPIRES: use it now, do not store it. Persist `refreshUrl` instead.
              */
             url?: string;
             /**
-             * Instagram and Facebook only. Endpoint that resolves this attachment to a working url every time, re-minting it from Meta when the stored one has expired. Safe to store and render indefinitely.
+             * Instagram and Facebook only. Endpoint that resolves this attachment to a working url every time, re-minting it from Meta when the stored one has expired. Safe to store and render indefinitely, except for an attachment with `originalType: "unsupported_type"`: Meta cannot re-serve those, so the endpoint answers 404 once the url has expired.
              */
             refreshUrl?: (string) | null;
             filename?: (string) | null;
@@ -23468,13 +23496,26 @@ type GetInboxConversationMessagesResponse = ({
          */
         subject?: (string) | null;
         /**
-         * Instagram story reply
+         * Instagram only. Present when the message replies to one of the account's stories. Also set on history imported after connecting, read off Meta's `story.reply_to`.
          */
-        storyReply?: (boolean) | null;
+        storyReply?: {
+            /**
+             * The Instagram story ID the user replied to.
+             */
+            storyId?: string;
+            /**
+             * Meta CDN URL for the story media. Expires roughly 24 hours after the story posted; fetch promptly or treat 404s as expected.
+             */
+            storyUrl?: string;
+        };
+        /**
+         * Instagram only. True when the message is the user mentioning the account in their own story. The story itself is the `share` attachment with `originalType: "story_mention"`. Also set on imported history, read off Meta's `story.mention`.
+         */
+        isStoryMention?: boolean;
         /**
-         * Instagram story mention
+         * Instagram and Facebook Messenger only. True when Meta withholds the content of this message from the API (its `is_unsupported` flag): `message` is empty, `attachments` is empty, and there is nothing to fetch, now or later. Distinguishes such a message from an ordinary empty one such as a story reply with no text. Absent on other platforms.
          */
-        isStoryMention?: (boolean) | null;
+        noRenderableContent?: boolean;
         /**
          * True if the sender has edited this message at least once.
          */

package/dist/index.d.ts

@@ -11120,7 +11120,15 @@ type WebhookPayloadMessage = {
         text: (string) | null;
         attachments: Array<{
             /**
-             * Attachment type (image, video, file, sticker, audio, share)
+             * Attachment type (image, video, file, sticker, audio, share).
+             *
+             * Instagram and Facebook deliver a shared reel, post or ad with no
+             * type of its own (Meta's `unsupported_type`). Zernio resolves it
+             * from the media's Content-Type at ingest, so it arrives as `image`,
+             * `video`, `audio` or `file` with `originalType: "unsupported_type"`.
+             * `type: "unsupported_type"` itself is emitted only when the CDN
+             * could not be classified in time; the `url` still works.
+             *
              */
             type: string;
             /**
@@ -11135,8 +11143,21 @@ type WebhookPayloadMessage = {
              * unrecognized type as a generic document shows your agent
              * "document received" for what is usually a lead.
              *
+             * `originalType: "unsupported_type"` marks a share Meta did not
+             * classify, resolved by content type. **Download it on receipt**:
+             * Meta answers `is_unsupported` with no attachments when the
+             * message node is read back, so the attachment-resolve endpoint
+             * cannot re-mint this url once it expires.
+             *
              */
             originalType?: string;
+            /**
+             * MIME type of the media when Zernio knows it. On Instagram and
+             * Facebook it is set for shares resolved by content type
+             * (`originalType: "unsupported_type"`).
+             *
+             */
+            mimeType?: string;
             /**
              * Where to fetch the attachment. **The contract differs by platform.**
              *
@@ -23441,17 +23462,24 @@ type GetInboxConversationMessagesResponse = ({
         createdAt?: string;
         attachments?: Array<{
             id?: string;
-            type?: 'image' | 'video' | 'audio' | 'file' | 'sticker' | 'share' | 'template';
             /**
-             * Instagram and Facebook only, and present only when it differs from `type`. Meta's own type before normalization: `ig_reel` and `reel` become `video`, while `ig_post`, `post`, `ig_story` and `story_mention` become `share`. A story mention is `type: "share"` with `originalType: "story_mention"`; render on this field, since `share` alone is ambiguous.
+             * On Instagram and Facebook a shared reel, post or ad reaches Zernio with no type of its own (Meta's `unsupported_type`) and is resolved from the media's Content-Type at ingest into `image`, `video`, `audio` or `file` with `originalType: "unsupported_type"`. `unsupported_type` is returned only when the CDN could not be classified in time.
+             */
+            type?: 'image' | 'video' | 'audio' | 'file' | 'sticker' | 'share' | 'template' | 'unsupported_type';
+            /**
+             * Instagram and Facebook only, and present only when it differs from `type`. Meta's own type before normalization: `ig_reel` and `reel` become `video`, while `ig_post`, `post`, `ig_story` and `story_mention` become `share`. A story mention is `type: "share"` with `originalType: "story_mention"`; render on this field, since `share` alone is ambiguous. `originalType: "unsupported_type"` marks a share Meta did not classify, resolved by content type: `refreshUrl` cannot re-mint it (Meta answers `is_unsupported` with no attachments for the message node), so download it when the `message.received` webhook arrives.
              */
             originalType?: string;
+            /**
+             * MIME type of the media when Zernio knows it. On Instagram and Facebook it is set for shares resolved by content type (`originalType: "unsupported_type"`).
+             */
+            mimeType?: string;
             /**
              * Direct media link. On Instagram and Facebook this is a signed Meta CDN url that EXPIRES: use it now, do not store it. Persist `refreshUrl` instead.
              */
             url?: string;
             /**
-             * Instagram and Facebook only. Endpoint that resolves this attachment to a working url every time, re-minting it from Meta when the stored one has expired. Safe to store and render indefinitely.
+             * Instagram and Facebook only. Endpoint that resolves this attachment to a working url every time, re-minting it from Meta when the stored one has expired. Safe to store and render indefinitely, except for an attachment with `originalType: "unsupported_type"`: Meta cannot re-serve those, so the endpoint answers 404 once the url has expired.
              */
             refreshUrl?: (string) | null;
             filename?: (string) | null;
@@ -23468,13 +23496,26 @@ type GetInboxConversationMessagesResponse = ({
          */
         subject?: (string) | null;
         /**
-         * Instagram story reply
+         * Instagram only. Present when the message replies to one of the account's stories. Also set on history imported after connecting, read off Meta's `story.reply_to`.
          */
-        storyReply?: (boolean) | null;
+        storyReply?: {
+            /**
+             * The Instagram story ID the user replied to.
+             */
+            storyId?: string;
+            /**
+             * Meta CDN URL for the story media. Expires roughly 24 hours after the story posted; fetch promptly or treat 404s as expected.
+             */
+            storyUrl?: string;
+        };
+        /**
+         * Instagram only. True when the message is the user mentioning the account in their own story. The story itself is the `share` attachment with `originalType: "story_mention"`. Also set on imported history, read off Meta's `story.mention`.
+         */
+        isStoryMention?: boolean;
         /**
-         * Instagram story mention
+         * Instagram and Facebook Messenger only. True when Meta withholds the content of this message from the API (its `is_unsupported` flag): `message` is empty, `attachments` is empty, and there is nothing to fetch, now or later. Distinguishes such a message from an ordinary empty one such as a story reply with no text. Absent on other platforms.
          */
-        isStoryMention?: (boolean) | null;
+        noRenderableContent?: boolean;
         /**
          * True if the sender has edited this message at least once.
          */

package/dist/index.js

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(index_exports);
 // package.json
 var package_default = {
   name: "@zernio/node",
-  version: "0.2.889",
+  version: "0.2.891",
   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.889",
+  version: "0.2.891",
   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.889",
+  "version": "0.2.891",
   "description": "The official Node.js library for the Zernio API",
   "main": "dist/index.js",
   "module": "dist/index.mjs",

package/src/generated/types.gen.ts

@@ -9824,7 +9824,15 @@ export type WebhookPayloadMessage = {
         text: (string) | null;
         attachments: Array<{
             /**
-             * Attachment type (image, video, file, sticker, audio, share)
+             * Attachment type (image, video, file, sticker, audio, share).
+             *
+             * Instagram and Facebook deliver a shared reel, post or ad with no
+             * type of its own (Meta's `unsupported_type`). Zernio resolves it
+             * from the media's Content-Type at ingest, so it arrives as `image`,
+             * `video`, `audio` or `file` with `originalType: "unsupported_type"`.
+             * `type: "unsupported_type"` itself is emitted only when the CDN
+             * could not be classified in time; the `url` still works.
+             *
              */
             type: string;
             /**
@@ -9839,8 +9847,21 @@ export type WebhookPayloadMessage = {
              * unrecognized type as a generic document shows your agent
              * "document received" for what is usually a lead.
              *
+             * `originalType: "unsupported_type"` marks a share Meta did not
+             * classify, resolved by content type. **Download it on receipt**:
+             * Meta answers `is_unsupported` with no attachments when the
+             * message node is read back, so the attachment-resolve endpoint
+             * cannot re-mint this url once it expires.
+             *
              */
             originalType?: string;
+            /**
+             * MIME type of the media when Zernio knows it. On Instagram and
+             * Facebook it is set for shares resolved by content type
+             * (`originalType: "unsupported_type"`).
+             *
+             */
+            mimeType?: string;
             /**
              * Where to fetch the attachment. **The contract differs by platform.**
              *
@@ -22899,17 +22920,24 @@ export type GetInboxConversationMessagesResponse = ({
         createdAt?: string;
         attachments?: Array<{
             id?: string;
-            type?: 'image' | 'video' | 'audio' | 'file' | 'sticker' | 'share' | 'template';
             /**
-             * Instagram and Facebook only, and present only when it differs from `type`. Meta's own type before normalization: `ig_reel` and `reel` become `video`, while `ig_post`, `post`, `ig_story` and `story_mention` become `share`. A story mention is `type: "share"` with `originalType: "story_mention"`; render on this field, since `share` alone is ambiguous.
+             * On Instagram and Facebook a shared reel, post or ad reaches Zernio with no type of its own (Meta's `unsupported_type`) and is resolved from the media's Content-Type at ingest into `image`, `video`, `audio` or `file` with `originalType: "unsupported_type"`. `unsupported_type` is returned only when the CDN could not be classified in time.
+             */
+            type?: 'image' | 'video' | 'audio' | 'file' | 'sticker' | 'share' | 'template' | 'unsupported_type';
+            /**
+             * Instagram and Facebook only, and present only when it differs from `type`. Meta's own type before normalization: `ig_reel` and `reel` become `video`, while `ig_post`, `post`, `ig_story` and `story_mention` become `share`. A story mention is `type: "share"` with `originalType: "story_mention"`; render on this field, since `share` alone is ambiguous. `originalType: "unsupported_type"` marks a share Meta did not classify, resolved by content type: `refreshUrl` cannot re-mint it (Meta answers `is_unsupported` with no attachments for the message node), so download it when the `message.received` webhook arrives.
              */
             originalType?: string;
+            /**
+             * MIME type of the media when Zernio knows it. On Instagram and Facebook it is set for shares resolved by content type (`originalType: "unsupported_type"`).
+             */
+            mimeType?: string;
             /**
              * Direct media link. On Instagram and Facebook this is a signed Meta CDN url that EXPIRES: use it now, do not store it. Persist `refreshUrl` instead.
              */
             url?: string;
             /**
-             * Instagram and Facebook only. Endpoint that resolves this attachment to a working url every time, re-minting it from Meta when the stored one has expired. Safe to store and render indefinitely.
+             * Instagram and Facebook only. Endpoint that resolves this attachment to a working url every time, re-minting it from Meta when the stored one has expired. Safe to store and render indefinitely, except for an attachment with `originalType: "unsupported_type"`: Meta cannot re-serve those, so the endpoint answers 404 once the url has expired.
              */
             refreshUrl?: (string) | null;
             filename?: (string) | null;
@@ -22926,13 +22954,26 @@ export type GetInboxConversationMessagesResponse = ({
          */
         subject?: (string) | null;
         /**
-         * Instagram story reply
+         * Instagram only. Present when the message replies to one of the account's stories. Also set on history imported after connecting, read off Meta's `story.reply_to`.
          */
-        storyReply?: (boolean) | null;
+        storyReply?: {
+            /**
+             * The Instagram story ID the user replied to.
+             */
+            storyId?: string;
+            /**
+             * Meta CDN URL for the story media. Expires roughly 24 hours after the story posted; fetch promptly or treat 404s as expected.
+             */
+            storyUrl?: string;
+        };
+        /**
+         * Instagram only. True when the message is the user mentioning the account in their own story. The story itself is the `share` attachment with `originalType: "story_mention"`. Also set on imported history, read off Meta's `story.mention`.
+         */
+        isStoryMention?: boolean;
         /**
-         * Instagram story mention
+         * Instagram and Facebook Messenger only. True when Meta withholds the content of this message from the API (its `is_unsupported` flag): `message` is empty, `attachments` is empty, and there is nothing to fetch, now or later. Distinguishes such a message from an ordinary empty one such as a story reply with no text. Absent on other platforms.
          */
-        isStoryMention?: (boolean) | null;
+        noRenderableContent?: boolean;
         /**
          * True if the sender has edited this message at least once.
          */