@getlatedev/node 0.2.876 → 0.2.878

package/dist/index.d.mts

@@ -8990,6 +8990,9 @@ type SocialAccount = {
      * - profileData.bio: The member's headline for personal accounts, or the organization description for organization accounts. null when the member has not set one.
      * - profileData.extraData.vanityName: The member's profile slug, i.e. the /in/{vanityName} segment of profileUrl. Personal accounts only; an organization's own slug is in metadata.organizationInfo.vanityName.
      *
+     * For Instagram accounts:
+     * - loginMethod: "facebook_login" when the account was connected through Facebook Login. Absent on accounts connected with Instagram Login. On facebook_login accounts, comment reads leave hidden comments out entirely instead of returning them with isHidden true.
+     *
      * For X (Twitter) accounts:
      * - profileData.extraData.isPremium: Whether X reports a paid subscription (Basic, Premium, Premium+, or a blue verified badge), which raises the post length limit from 280 to 25,000 characters. Read live at connect and reconnect and refreshed by the daily follower snapshot; because X intermittently reports no subscription for subscribed accounts, a cancellation is stored on the fourth consecutive daily snapshot that reports it (about four days). Accounts connected before the extraData layout carry the same flag at profileData.isPremium.
      *
@@ -11854,9 +11857,15 @@ type WebhookPayloadMessageSent = {
     conversation: InboxWebhookConversation;
     account: InboxWebhookAccount;
     /**
-     * Platform-specific context for the sent message: a quote-reply reference, a WhatsApp location pin, WhatsApp contact cards or the TikTok message type. The key is present only when the send carried some context, and absent otherwise: it is never null and never an empty object. Read it to tell a location or contact-card message from a text one without a GET on the message.
+     * Platform-specific context for the sent message: a quote-reply reference, a WhatsApp location pin, WhatsApp contact cards, the TikTok message type, or outgoing Instagram/Facebook buttons, quick replies and template. The key is present only when the send carried some context, and absent otherwise: it is never null and never an empty object. Read it to tell a location or contact-card message from a text one without a GET on the message.
      */
     metadata?: {
+        /**
+         * Instagram/Facebook only. The buttons, quickReplies and/or template this outgoing message carried, as sent (tracked urls included when link tracking wrapped a button). Absent when the send carried none.
+         */
+        metaInteractive?: {
+            [key: string]: unknown;
+        };
         /**
          * WhatsApp only. The location pin this message carries, in the same
          * shape the inbox send API accepts. Present on API sends that passed
@@ -23440,11 +23449,13 @@ type GetInboxConversationMessagesResponse = ({
          * delivered as `message.platformMessageId` on webhooks),
          * `waInteractive` (a compact descriptor of WhatsApp interactive
          * content sent: buttons / list / cta_url / flow / location_request),
-         * and for inbound interactive taps `interactiveType` / `interactiveId`.
-         * It can also carry `source` (`whatsapp_business_app` /
-         * `coexistence_history` on a WhatsApp Coexistence number, `bulk-api` on
-         * a POST /v1/whatsapp/bulk send), which is where the message reached us
-         * from rather than who produced it: read `sentVia` for that.
+         * `metaInteractive` (outgoing Instagram/Facebook buttons, quickReplies
+         * and template, as sent), and for inbound interactive taps
+         * `interactiveType` / `interactiveId`. It can also carry `source`
+         * (`whatsapp_business_app` / `coexistence_history` on a WhatsApp
+         * Coexistence number, `bulk-api` on a POST /v1/whatsapp/bulk send),
+         * which is where the message reached us from rather than who produced
+         * it: read `sentVia` for that.
          *
          */
         metadata?: {
@@ -24714,7 +24725,7 @@ type ListInboxCommentsError = ({
 type GetInboxPostCommentsData = {
     path: {
         /**
-         * Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. LinkedIn third-party posts accept full activity URN or numeric ID. On Facebook and Instagram, a comment ID is also accepted here and returns that comment's replies.
+         * Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. LinkedIn third-party posts accept full activity URN or numeric ID. On Facebook, a comment ID is also accepted here and returns that comment's replies (not supported on Instagram).
          */
         postId: string;
     };
@@ -24786,7 +24797,7 @@ type GetInboxPostCommentsResponse = ({
          */
         canLike?: boolean;
         /**
-         * Whether the comment is currently hidden
+         * Whether the comment is currently hidden. On Instagram accounts connected through Facebook Login, Meta leaves hidden comments (and their replies) out of the list entirely, so they never appear with isHidden true; Instagram Login accounts and Facebook Pages return them with isHidden true.
          */
         isHidden?: boolean;
         /**

package/dist/index.d.ts

@@ -8990,6 +8990,9 @@ type SocialAccount = {
      * - profileData.bio: The member's headline for personal accounts, or the organization description for organization accounts. null when the member has not set one.
      * - profileData.extraData.vanityName: The member's profile slug, i.e. the /in/{vanityName} segment of profileUrl. Personal accounts only; an organization's own slug is in metadata.organizationInfo.vanityName.
      *
+     * For Instagram accounts:
+     * - loginMethod: "facebook_login" when the account was connected through Facebook Login. Absent on accounts connected with Instagram Login. On facebook_login accounts, comment reads leave hidden comments out entirely instead of returning them with isHidden true.
+     *
      * For X (Twitter) accounts:
      * - profileData.extraData.isPremium: Whether X reports a paid subscription (Basic, Premium, Premium+, or a blue verified badge), which raises the post length limit from 280 to 25,000 characters. Read live at connect and reconnect and refreshed by the daily follower snapshot; because X intermittently reports no subscription for subscribed accounts, a cancellation is stored on the fourth consecutive daily snapshot that reports it (about four days). Accounts connected before the extraData layout carry the same flag at profileData.isPremium.
      *
@@ -11854,9 +11857,15 @@ type WebhookPayloadMessageSent = {
     conversation: InboxWebhookConversation;
     account: InboxWebhookAccount;
     /**
-     * Platform-specific context for the sent message: a quote-reply reference, a WhatsApp location pin, WhatsApp contact cards or the TikTok message type. The key is present only when the send carried some context, and absent otherwise: it is never null and never an empty object. Read it to tell a location or contact-card message from a text one without a GET on the message.
+     * Platform-specific context for the sent message: a quote-reply reference, a WhatsApp location pin, WhatsApp contact cards, the TikTok message type, or outgoing Instagram/Facebook buttons, quick replies and template. The key is present only when the send carried some context, and absent otherwise: it is never null and never an empty object. Read it to tell a location or contact-card message from a text one without a GET on the message.
      */
     metadata?: {
+        /**
+         * Instagram/Facebook only. The buttons, quickReplies and/or template this outgoing message carried, as sent (tracked urls included when link tracking wrapped a button). Absent when the send carried none.
+         */
+        metaInteractive?: {
+            [key: string]: unknown;
+        };
         /**
          * WhatsApp only. The location pin this message carries, in the same
          * shape the inbox send API accepts. Present on API sends that passed
@@ -23440,11 +23449,13 @@ type GetInboxConversationMessagesResponse = ({
          * delivered as `message.platformMessageId` on webhooks),
          * `waInteractive` (a compact descriptor of WhatsApp interactive
          * content sent: buttons / list / cta_url / flow / location_request),
-         * and for inbound interactive taps `interactiveType` / `interactiveId`.
-         * It can also carry `source` (`whatsapp_business_app` /
-         * `coexistence_history` on a WhatsApp Coexistence number, `bulk-api` on
-         * a POST /v1/whatsapp/bulk send), which is where the message reached us
-         * from rather than who produced it: read `sentVia` for that.
+         * `metaInteractive` (outgoing Instagram/Facebook buttons, quickReplies
+         * and template, as sent), and for inbound interactive taps
+         * `interactiveType` / `interactiveId`. It can also carry `source`
+         * (`whatsapp_business_app` / `coexistence_history` on a WhatsApp
+         * Coexistence number, `bulk-api` on a POST /v1/whatsapp/bulk send),
+         * which is where the message reached us from rather than who produced
+         * it: read `sentVia` for that.
          *
          */
         metadata?: {
@@ -24714,7 +24725,7 @@ type ListInboxCommentsError = ({
 type GetInboxPostCommentsData = {
     path: {
         /**
-         * Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. LinkedIn third-party posts accept full activity URN or numeric ID. On Facebook and Instagram, a comment ID is also accepted here and returns that comment's replies.
+         * Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. LinkedIn third-party posts accept full activity URN or numeric ID. On Facebook, a comment ID is also accepted here and returns that comment's replies (not supported on Instagram).
          */
         postId: string;
     };
@@ -24786,7 +24797,7 @@ type GetInboxPostCommentsResponse = ({
          */
         canLike?: boolean;
         /**
-         * Whether the comment is currently hidden
+         * Whether the comment is currently hidden. On Instagram accounts connected through Facebook Login, Meta leaves hidden comments (and their replies) out of the list entirely, so they never appear with isHidden true; Instagram Login accounts and Facebook Pages return them with isHidden true.
          */
         isHidden?: boolean;
         /**

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -4246,9 +4246,10 @@ export const listInboxComments = <ThrowOnError extends boolean = false>(options?
  * Get post comments
  * Fetch comments for a specific post. Requires accountId query parameter.
  *
- * On Facebook and Instagram, passing a COMMENT id as `postId` is also supported and
- * returns that comment's replies instead of the post's top-level comments. This is not
- * available on YouTube, where `postId` must be a video id.
+ * On Facebook, passing a COMMENT id as `postId` is also supported and returns that
+ * comment's replies instead of the post's top-level comments. Instagram does not support
+ * this and returns 400: its replies come nested in each comment's `replies` array, with no
+ * separate paging. YouTube does not support it either, `postId` must be a video id.
  *
  * Responses are cached for up to 10 minutes, so a page may lag new comments by that
  * window. Do not poll this endpoint for real-time updates: subscribe to the
@@ -4260,6 +4261,11 @@ export const listInboxComments = <ThrowOnError extends boolean = false>(options?
  * `commentId` pages the full reply list of one comment. Developer-app TikTok accounts
  * return 400 with code `PLATFORM_LIMITATION`.
  *
+ * Hidden comments: Facebook Pages and Instagram accounts connected through Instagram Login
+ * return them with `isHidden: true`. Instagram accounts connected through Facebook Login do
+ * not return them at all (Meta omits them, together with their replies), so a hidden comment
+ * and a deleted one look the same on this read.
+ *
  */
 export const getInboxPostComments = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<GetInboxPostCommentsData, ThrowOnError>) => {
     return (options?.client ?? client).get<GetInboxPostCommentsResponse, GetInboxPostCommentsError, ThrowOnError>({

package/src/generated/types.gen.ts

@@ -7614,6 +7614,9 @@ export type SocialAccount = {
      * - profileData.bio: The member's headline for personal accounts, or the organization description for organization accounts. null when the member has not set one.
      * - profileData.extraData.vanityName: The member's profile slug, i.e. the /in/{vanityName} segment of profileUrl. Personal accounts only; an organization's own slug is in metadata.organizationInfo.vanityName.
      *
+     * For Instagram accounts:
+     * - loginMethod: "facebook_login" when the account was connected through Facebook Login. Absent on accounts connected with Instagram Login. On facebook_login accounts, comment reads leave hidden comments out entirely instead of returning them with isHidden true.
+     *
      * For X (Twitter) accounts:
      * - profileData.extraData.isPremium: Whether X reports a paid subscription (Basic, Premium, Premium+, or a blue verified badge), which raises the post length limit from 280 to 25,000 characters. Read live at connect and reconnect and refreshed by the daily follower snapshot; because X intermittently reports no subscription for subscribed accounts, a cancellation is stored on the fourth consecutive daily snapshot that reports it (about four days). Accounts connected before the extraData layout carry the same flag at profileData.isPremium.
      *
@@ -10572,9 +10575,15 @@ export type WebhookPayloadMessageSent = {
     conversation: InboxWebhookConversation;
     account: InboxWebhookAccount;
     /**
-     * Platform-specific context for the sent message: a quote-reply reference, a WhatsApp location pin, WhatsApp contact cards or the TikTok message type. The key is present only when the send carried some context, and absent otherwise: it is never null and never an empty object. Read it to tell a location or contact-card message from a text one without a GET on the message.
+     * Platform-specific context for the sent message: a quote-reply reference, a WhatsApp location pin, WhatsApp contact cards, the TikTok message type, or outgoing Instagram/Facebook buttons, quick replies and template. The key is present only when the send carried some context, and absent otherwise: it is never null and never an empty object. Read it to tell a location or contact-card message from a text one without a GET on the message.
      */
     metadata?: {
+        /**
+         * Instagram/Facebook only. The buttons, quickReplies and/or template this outgoing message carried, as sent (tracked urls included when link tracking wrapped a button). Absent when the send carried none.
+         */
+        metaInteractive?: {
+            [key: string]: unknown;
+        };
         /**
          * WhatsApp only. The location pin this message carries, in the same
          * shape the inbox send API accepts. Present on API sends that passed
@@ -22901,11 +22910,13 @@ export type GetInboxConversationMessagesResponse = ({
          * delivered as `message.platformMessageId` on webhooks),
          * `waInteractive` (a compact descriptor of WhatsApp interactive
          * content sent: buttons / list / cta_url / flow / location_request),
-         * and for inbound interactive taps `interactiveType` / `interactiveId`.
-         * It can also carry `source` (`whatsapp_business_app` /
-         * `coexistence_history` on a WhatsApp Coexistence number, `bulk-api` on
-         * a POST /v1/whatsapp/bulk send), which is where the message reached us
-         * from rather than who produced it: read `sentVia` for that.
+         * `metaInteractive` (outgoing Instagram/Facebook buttons, quickReplies
+         * and template, as sent), and for inbound interactive taps
+         * `interactiveType` / `interactiveId`. It can also carry `source`
+         * (`whatsapp_business_app` / `coexistence_history` on a WhatsApp
+         * Coexistence number, `bulk-api` on a POST /v1/whatsapp/bulk send),
+         * which is where the message reached us from rather than who produced
+         * it: read `sentVia` for that.
          *
          */
         metadata?: {
@@ -24240,7 +24251,7 @@ export type ListInboxCommentsError = ({
 export type GetInboxPostCommentsData = {
     path: {
         /**
-         * Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. LinkedIn third-party posts accept full activity URN or numeric ID. On Facebook and Instagram, a comment ID is also accepted here and returns that comment's replies.
+         * Zernio post ID or platform-specific post ID. Zernio IDs are auto-resolved. LinkedIn third-party posts accept full activity URN or numeric ID. On Facebook, a comment ID is also accepted here and returns that comment's replies (not supported on Instagram).
          */
         postId: string;
     };
@@ -24313,7 +24324,7 @@ export type GetInboxPostCommentsResponse = ({
          */
         canLike?: boolean;
         /**
-         * Whether the comment is currently hidden
+         * Whether the comment is currently hidden. On Instagram accounts connected through Facebook Login, Meta leaves hidden comments (and their replies) out of the list entirely, so they never appear with isHidden true; Instagram Login accounts and Facebook Pages return them with isHidden true.
          */
         isHidden?: boolean;
         /**