@zernio/node 0.2.890 → 0.2.892

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.**
              *
@@ -16265,6 +16286,10 @@ type GetAccountHealthResponse = ({
             subcode?: number;
             message?: string;
         } | null;
+        /**
+         * From the phone number's Meta health_status. `false` = Meta says Zernio is not subscribed to the message webhook for this number, so inbound messages are not delivered even though the number is CONNECTED and can still send. Fix by re-subscribing (reconnect the number); if it stays `false`, the number is routed to a different WhatsApp Business Account (typically after linking it to a Facebook Page). `true` = Meta reports no such problem. `null` = Meta did not report it (read failed or no health_status), not evidence either way.
+         */
+        inboundWebhookSubscribed?: (boolean) | null;
     };
 });
 type GetAccountHealthError = (ErrorResponse | {
@@ -23441,17 +23466,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;

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.**
              *
@@ -16265,6 +16286,10 @@ type GetAccountHealthResponse = ({
             subcode?: number;
             message?: string;
         } | null;
+        /**
+         * From the phone number's Meta health_status. `false` = Meta says Zernio is not subscribed to the message webhook for this number, so inbound messages are not delivered even though the number is CONNECTED and can still send. Fix by re-subscribing (reconnect the number); if it stays `false`, the number is routed to a different WhatsApp Business Account (typically after linking it to a Facebook Page). `true` = Meta reports no such problem. `null` = Meta did not report it (read failed or no health_status), not evidence either way.
+         */
+        inboundWebhookSubscribed?: (boolean) | null;
     };
 });
 type GetAccountHealthError = (ErrorResponse | {
@@ -23441,17 +23466,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;

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -1386,7 +1386,9 @@ export const verifyWhatsAppNumber = <ThrowOnError extends boolean = false>(optio
  * token can be perfectly valid while Meta refuses to serve the phone-number object (for
  * example after a phone-side coexistence disconnect), so `tokenStatus` alone is not a
  * liveness signal for WhatsApp. When the Meta link is dead, `platformConnection.status` is
- * `disconnected` and the overall `status` is `error`.
+ * `disconnected` and the overall `status` is `error`. When Meta reports that the number's
+ * inbound message webhook does not reach Zernio, `platformConnection.inboundWebhookSubscribed`
+ * is `false`, an entry is added to `issues`, and the overall `status` is at least `warning`.
  *
  */
 export const getAccountHealth = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetAccountHealthData, ThrowOnError>) => {

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.**
              *
@@ -15270,6 +15291,10 @@ export type GetAccountHealthResponse = ({
             subcode?: number;
             message?: string;
         } | null;
+        /**
+         * From the phone number's Meta health_status. `false` = Meta says Zernio is not subscribed to the message webhook for this number, so inbound messages are not delivered even though the number is CONNECTED and can still send. Fix by re-subscribing (reconnect the number); if it stays `false`, the number is routed to a different WhatsApp Business Account (typically after linking it to a Facebook Page). `true` = Meta reports no such problem. `null` = Meta did not report it (read failed or no health_status), not evidence either way.
+         */
+        inboundWebhookSubscribed?: (boolean) | null;
     };
 });
 
@@ -22899,17 +22924,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;