@zernio/node 0.2.733 → 0.2.735

package/dist/index.d.mts

@@ -10262,6 +10262,30 @@ type WebhookPayloadMessage = {
              */
             product_retailer_id?: string;
         };
+        /**
+         * WhatsApp only. The location pin the user shared, forwarded
+         * verbatim from Meta. The message `text` is only the emoji preview
+         * (`📍 <name>`); the coordinates live here.
+         *
+         */
+        location?: {
+            /**
+             * Latitude in decimal degrees.
+             */
+            latitude?: number;
+            /**
+             * Longitude in decimal degrees.
+             */
+            longitude?: number;
+            /**
+             * Location name, when the user shared a named place.
+             */
+            name?: string;
+            /**
+             * Street address, when Meta sends one.
+             */
+            address?: string;
+        };
         /**
          * WhatsApp only. Contact cards the user shared, forwarded verbatim
          * from Meta. Read `contactsOrigin` before treating any number here
@@ -10688,9 +10712,48 @@ type WebhookPayloadMessageSent = {
     conversation: InboxWebhookConversation;
     account: InboxWebhookAccount;
     /**
-     * Platform-specific context for the sent message. The key is present only when the send carried some context, and absent otherwise: it is never null and never an empty object.
+     * Platform-specific context for the sent message: a quote-reply reference, a WhatsApp location pin or WhatsApp contact cards. 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?: {
+        /**
+         * WhatsApp only. The location pin this message carries, in the same
+         * shape the inbox send API accepts. Present on API sends that passed
+         * `location`, and on Coexistence echoes of a pin shared from the
+         * WhatsApp Business app. The message `text` is only the emoji
+         * preview (`📍 <name>`); the pin itself lives here.
+         *
+         */
+        location?: {
+            /**
+             * Latitude in decimal degrees.
+             */
+            latitude?: number;
+            /**
+             * Longitude in decimal degrees.
+             */
+            longitude?: number;
+            /**
+             * Location name, when one was given.
+             */
+            name?: string;
+            /**
+             * Street address, when one was given.
+             */
+            address?: string;
+        };
+        /**
+         * WhatsApp only. The contact cards this message carries. On API
+         * sends this is the `contacts` array exactly as given to the inbox
+         * send API (`name`, `phones[].phone` / `type`, `emails[]`); on
+         * Coexistence echoes of a card shared from the WhatsApp Business
+         * app it is Meta's shape (`phones[].wa_id`, `vcard`). The message
+         * `text` is only the emoji preview (`👤 <name>`); the cards live
+         * here.
+         *
+         */
+        contacts?: Array<{
+            [key: string]: unknown;
+        }>;
         /**
          * `platformMessageId` of the message this send is a quote-reply to.
          *
@@ -10819,8 +10882,11 @@ type event21 = 'post.scheduled' | 'post.published' | 'post.failed' | 'post.parti
  * and for `post.tiktok.url_resolved` (same shape, fired when a
  * published TikTok post's public URL is backfilled). Terminal events
  * fire once per platform target inside a post as that platform
- * reaches a terminal state (published or permanent failure). The
- * `post` envelope mirrors the shape of `WebhookPayloadPost` so
+ * reaches a terminal state (published or permanent failure), except
+ * that a target which later fails background reconciliation emits
+ * `post.platform.failed` a second time, after its own
+ * `post.platform.published`. The `post` envelope mirrors the shape
+ * of `WebhookPayloadPost` so
  * consumers can reuse rendering logic; the `platform` block
  * identifies which specific platform transitioned; the `account`
  * block identifies the connected account behind that

package/dist/index.d.ts

@@ -10262,6 +10262,30 @@ type WebhookPayloadMessage = {
              */
             product_retailer_id?: string;
         };
+        /**
+         * WhatsApp only. The location pin the user shared, forwarded
+         * verbatim from Meta. The message `text` is only the emoji preview
+         * (`📍 <name>`); the coordinates live here.
+         *
+         */
+        location?: {
+            /**
+             * Latitude in decimal degrees.
+             */
+            latitude?: number;
+            /**
+             * Longitude in decimal degrees.
+             */
+            longitude?: number;
+            /**
+             * Location name, when the user shared a named place.
+             */
+            name?: string;
+            /**
+             * Street address, when Meta sends one.
+             */
+            address?: string;
+        };
         /**
          * WhatsApp only. Contact cards the user shared, forwarded verbatim
          * from Meta. Read `contactsOrigin` before treating any number here
@@ -10688,9 +10712,48 @@ type WebhookPayloadMessageSent = {
     conversation: InboxWebhookConversation;
     account: InboxWebhookAccount;
     /**
-     * Platform-specific context for the sent message. The key is present only when the send carried some context, and absent otherwise: it is never null and never an empty object.
+     * Platform-specific context for the sent message: a quote-reply reference, a WhatsApp location pin or WhatsApp contact cards. 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?: {
+        /**
+         * WhatsApp only. The location pin this message carries, in the same
+         * shape the inbox send API accepts. Present on API sends that passed
+         * `location`, and on Coexistence echoes of a pin shared from the
+         * WhatsApp Business app. The message `text` is only the emoji
+         * preview (`📍 <name>`); the pin itself lives here.
+         *
+         */
+        location?: {
+            /**
+             * Latitude in decimal degrees.
+             */
+            latitude?: number;
+            /**
+             * Longitude in decimal degrees.
+             */
+            longitude?: number;
+            /**
+             * Location name, when one was given.
+             */
+            name?: string;
+            /**
+             * Street address, when one was given.
+             */
+            address?: string;
+        };
+        /**
+         * WhatsApp only. The contact cards this message carries. On API
+         * sends this is the `contacts` array exactly as given to the inbox
+         * send API (`name`, `phones[].phone` / `type`, `emails[]`); on
+         * Coexistence echoes of a card shared from the WhatsApp Business
+         * app it is Meta's shape (`phones[].wa_id`, `vcard`). The message
+         * `text` is only the emoji preview (`👤 <name>`); the cards live
+         * here.
+         *
+         */
+        contacts?: Array<{
+            [key: string]: unknown;
+        }>;
         /**
          * `platformMessageId` of the message this send is a quote-reply to.
          *
@@ -10819,8 +10882,11 @@ type event21 = 'post.scheduled' | 'post.published' | 'post.failed' | 'post.parti
  * and for `post.tiktok.url_resolved` (same shape, fired when a
  * published TikTok post's public URL is backfilled). Terminal events
  * fire once per platform target inside a post as that platform
- * reaches a terminal state (published or permanent failure). The
- * `post` envelope mirrors the shape of `WebhookPayloadPost` so
+ * reaches a terminal state (published or permanent failure), except
+ * that a target which later fails background reconciliation emits
+ * `post.platform.failed` a second time, after its own
+ * `post.platform.published`. The `post` envelope mirrors the shape
+ * of `WebhookPayloadPost` so
  * consumers can reuse rendering logic; the `platform` block
  * identifies which specific platform transitioned; the `account`
  * block identifies the connected account behind that

package/dist/index.js

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

package/src/generated/types.gen.ts

@@ -9061,6 +9061,30 @@ export type WebhookPayloadMessage = {
              */
             product_retailer_id?: string;
         };
+        /**
+         * WhatsApp only. The location pin the user shared, forwarded
+         * verbatim from Meta. The message `text` is only the emoji preview
+         * (`📍 <name>`); the coordinates live here.
+         *
+         */
+        location?: {
+            /**
+             * Latitude in decimal degrees.
+             */
+            latitude?: number;
+            /**
+             * Longitude in decimal degrees.
+             */
+            longitude?: number;
+            /**
+             * Location name, when the user shared a named place.
+             */
+            name?: string;
+            /**
+             * Street address, when Meta sends one.
+             */
+            address?: string;
+        };
         /**
          * WhatsApp only. Contact cards the user shared, forwarded verbatim
          * from Meta. Read `contactsOrigin` before treating any number here
@@ -9498,9 +9522,48 @@ export type WebhookPayloadMessageSent = {
     conversation: InboxWebhookConversation;
     account: InboxWebhookAccount;
     /**
-     * Platform-specific context for the sent message. The key is present only when the send carried some context, and absent otherwise: it is never null and never an empty object.
+     * Platform-specific context for the sent message: a quote-reply reference, a WhatsApp location pin or WhatsApp contact cards. 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?: {
+        /**
+         * WhatsApp only. The location pin this message carries, in the same
+         * shape the inbox send API accepts. Present on API sends that passed
+         * `location`, and on Coexistence echoes of a pin shared from the
+         * WhatsApp Business app. The message `text` is only the emoji
+         * preview (`📍 <name>`); the pin itself lives here.
+         *
+         */
+        location?: {
+            /**
+             * Latitude in decimal degrees.
+             */
+            latitude?: number;
+            /**
+             * Longitude in decimal degrees.
+             */
+            longitude?: number;
+            /**
+             * Location name, when one was given.
+             */
+            name?: string;
+            /**
+             * Street address, when one was given.
+             */
+            address?: string;
+        };
+        /**
+         * WhatsApp only. The contact cards this message carries. On API
+         * sends this is the `contacts` array exactly as given to the inbox
+         * send API (`name`, `phones[].phone` / `type`, `emails[]`); on
+         * Coexistence echoes of a card shared from the WhatsApp Business
+         * app it is Meta's shape (`phones[].wa_id`, `vcard`). The message
+         * `text` is only the emoji preview (`👤 <name>`); the cards live
+         * here.
+         *
+         */
+        contacts?: Array<{
+            [key: string]: unknown;
+        }>;
         /**
          * `platformMessageId` of the message this send is a quote-reply to.
          *
@@ -9637,8 +9700,11 @@ export type event21 = 'post.scheduled' | 'post.published' | 'post.failed' | 'pos
  * and for `post.tiktok.url_resolved` (same shape, fired when a
  * published TikTok post's public URL is backfilled). Terminal events
  * fire once per platform target inside a post as that platform
- * reaches a terminal state (published or permanent failure). The
- * `post` envelope mirrors the shape of `WebhookPayloadPost` so
+ * reaches a terminal state (published or permanent failure), except
+ * that a target which later fails background reconciliation emits
+ * `post.platform.failed` a second time, after its own
+ * `post.platform.published`. The `post` envelope mirrors the shape
+ * of `WebhookPayloadPost` so
  * consumers can reuse rendering logic; the `platform` block
  * identifies which specific platform transitioned; the `account`
  * block identifies the connected account behind that