@getlatedev/node 0.2.1109 → 0.2.1111

package/dist/index.d.mts

@@ -15037,8 +15037,15 @@ type WebhookPayloadMessage = {
         isStoryMention?: boolean;
         /**
          * Click attribution forwarded verbatim from Meta. Populated only on
-         * the FIRST inbound message after the click; absent on subsequent
-         * messages of the same conversation. On Instagram and Messenger a
+         * the first inbound message Meta attaches it to, and absent on the
+         * other messages of the same conversation. That is not always the
+         * first message after the click: on Instagram Click-to-Direct Meta
+         * usually delivers the ad post itself first, as an attachment-only
+         * `share` / `ig_post` message with no referral, and attaches the
+         * referral to the message right after it. The first referral of a
+         * conversation is also stored on the conversation as
+         * `metadata.meta_ad_*` (`GET /v1/inbox/conversations/{conversationId}`),
+         * so read it there instead of matching webhooks. On Instagram and Messenger a
          * RETURNING click also attaches it to the first message that
          * follows, so read it on every `message.received` for per-click
          * attribution; a click that opens an existing thread WITHOUT a
@@ -21885,6 +21892,10 @@ type ListFacebookPagesResponse = ({
          */
         tasks?: Array<(string)>;
     }>;
+    /**
+     * True when Meta still had more Pages after the listing hit its time budget or the 10,000 Page cap, so `pages` is incomplete. Do not ask the user to reconnect with fewer Pages ticked: Meta replaces the Page grant on every authorization, so unticked Pages lose access.
+     */
+    truncated?: boolean;
 });
 type ListFacebookPagesError = (unknown | ErrorResponse | {
     error?: string;
@@ -27714,10 +27725,12 @@ type GetInboxConversationResponse = ({
          * Ad-click attribution for a conversation that started from a Meta ad.
          * Absent when the conversation did not originate from an ad click.
          *
-         * Captured once, on the first inbound message after the click, and never
-         * overwritten. If the same person later clicks a different ad, the
-         * original values are kept. Meta only sends the referral on that first
-         * message.
+         * Captured once, from the first inbound message Meta attaches the referral
+         * to, and never overwritten. If the same person later clicks a different
+         * ad, the original values are kept. On Instagram Click-to-Direct that is
+         * usually not the first message: Meta first delivers the ad post as an
+         * attachment-only `share` / `ig_post` message with no referral, then
+         * attaches the referral to the next message.
          *
          * This operation currently returns only the `meta_ad_*` family, which
          * covers Instagram Click-to-Direct and Facebook Messenger

package/dist/index.d.ts

@@ -15037,8 +15037,15 @@ type WebhookPayloadMessage = {
         isStoryMention?: boolean;
         /**
          * Click attribution forwarded verbatim from Meta. Populated only on
-         * the FIRST inbound message after the click; absent on subsequent
-         * messages of the same conversation. On Instagram and Messenger a
+         * the first inbound message Meta attaches it to, and absent on the
+         * other messages of the same conversation. That is not always the
+         * first message after the click: on Instagram Click-to-Direct Meta
+         * usually delivers the ad post itself first, as an attachment-only
+         * `share` / `ig_post` message with no referral, and attaches the
+         * referral to the message right after it. The first referral of a
+         * conversation is also stored on the conversation as
+         * `metadata.meta_ad_*` (`GET /v1/inbox/conversations/{conversationId}`),
+         * so read it there instead of matching webhooks. On Instagram and Messenger a
          * RETURNING click also attaches it to the first message that
          * follows, so read it on every `message.received` for per-click
          * attribution; a click that opens an existing thread WITHOUT a
@@ -21885,6 +21892,10 @@ type ListFacebookPagesResponse = ({
          */
         tasks?: Array<(string)>;
     }>;
+    /**
+     * True when Meta still had more Pages after the listing hit its time budget or the 10,000 Page cap, so `pages` is incomplete. Do not ask the user to reconnect with fewer Pages ticked: Meta replaces the Page grant on every authorization, so unticked Pages lose access.
+     */
+    truncated?: boolean;
 });
 type ListFacebookPagesError = (unknown | ErrorResponse | {
     error?: string;
@@ -27714,10 +27725,12 @@ type GetInboxConversationResponse = ({
          * Ad-click attribution for a conversation that started from a Meta ad.
          * Absent when the conversation did not originate from an ad click.
          *
-         * Captured once, on the first inbound message after the click, and never
-         * overwritten. If the same person later clicks a different ad, the
-         * original values are kept. Meta only sends the referral on that first
-         * message.
+         * Captured once, from the first inbound message Meta attaches the referral
+         * to, and never overwritten. If the same person later clicks a different
+         * ad, the original values are kept. On Instagram Click-to-Direct that is
+         * usually not the first message: Meta first delivers the ad post as an
+         * attachment-only `share` / `ig_post` message with no referral, then
+         * attaches the referral to the next message.
          *
          * This operation currently returns only the `meta_ad_*` family, which
          * covers Instagram Click-to-Direct and Facebook Messenger

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -10654,6 +10654,11 @@ export const getAdReview = <ThrowOnError extends boolean = false>(options: Optio
  * creative (`asset_feed_spec`). Video items include Meta's poster thumbnail and the
  * video's Meta id when available.
  *
+ * Boosted Instagram posts (creatives with no image of their own) return the original
+ * post's media: the image, the video with its cover as `thumbnailUrl`, or every child of a
+ * carousel post with `index`. When the connection cannot read the Instagram post, the item
+ * is a 1080px rendering of the creative instead.
+ *
  * Reads Meta live rather than the stored creative blob because Meta's signed fbcdn
  * URLs carry an `oe=<hex>` expiration (image_url ~24 h, video source ~12 d). Treat
  * URLs as short-lived: re-fetch this endpoint before serving or downloading assets

package/src/generated/types.gen.ts

@@ -13619,8 +13619,15 @@ export type WebhookPayloadMessage = {
         isStoryMention?: boolean;
         /**
          * Click attribution forwarded verbatim from Meta. Populated only on
-         * the FIRST inbound message after the click; absent on subsequent
-         * messages of the same conversation. On Instagram and Messenger a
+         * the first inbound message Meta attaches it to, and absent on the
+         * other messages of the same conversation. That is not always the
+         * first message after the click: on Instagram Click-to-Direct Meta
+         * usually delivers the ad post itself first, as an attachment-only
+         * `share` / `ig_post` message with no referral, and attaches the
+         * referral to the message right after it. The first referral of a
+         * conversation is also stored on the conversation as
+         * `metadata.meta_ad_*` (`GET /v1/inbox/conversations/{conversationId}`),
+         * so read it there instead of matching webhooks. On Instagram and Messenger a
          * RETURNING click also attaches it to the first message that
          * follows, so read it on every `message.received` for per-click
          * attribution; a click that opens an existing thread WITHOUT a
@@ -20861,6 +20868,10 @@ export type ListFacebookPagesResponse = ({
          */
         tasks?: Array<(string)>;
     }>;
+    /**
+     * True when Meta still had more Pages after the listing hit its time budget or the 10,000 Page cap, so `pages` is incomplete. Do not ask the user to reconnect with fewer Pages ticked: Meta replaces the Page grant on every authorization, so unticked Pages lose access.
+     */
+    truncated?: boolean;
 });
 
 export type ListFacebookPagesError = (unknown | ErrorResponse | {
@@ -27091,10 +27102,12 @@ export type GetInboxConversationResponse = ({
          * Ad-click attribution for a conversation that started from a Meta ad.
          * Absent when the conversation did not originate from an ad click.
          *
-         * Captured once, on the first inbound message after the click, and never
-         * overwritten. If the same person later clicks a different ad, the
-         * original values are kept. Meta only sends the referral on that first
-         * message.
+         * Captured once, from the first inbound message Meta attaches the referral
+         * to, and never overwritten. If the same person later clicks a different
+         * ad, the original values are kept. On Instagram Click-to-Direct that is
+         * usually not the first message: Meta first delivers the ad post as an
+         * attachment-only `share` / `ig_post` message with no referral, then
+         * attaches the referral to the next message.
          *
          * This operation currently returns only the `meta_ad_*` family, which
          * covers Instagram Click-to-Direct and Facebook Messenger