@zernio/node 0.2.510 → 0.2.512

package/dist/index.d.mts

@@ -7341,9 +7341,17 @@ type WebhookPayloadMessage = {
     conversation: InboxWebhookConversation;
     account: InboxWebhookAccount;
     /**
-     * Interactive message metadata (present when message is a quick reply tap, postback button tap, or inline keyboard callback)
+     * Platform-specific message context (present when the message is a quick reply tap, postback button tap, inline keyboard callback, or a quote-reply to an earlier message)
      */
     metadata?: {
+        /**
+         * platformMessageId of the message this one is a quote-reply to.
+         * WhatsApp (`context.id`), Instagram and Facebook Messenger
+         * (`reply_to.mid`). On `message.sent` echoes (operator replied
+         * from the native app) this is the only metadata field populated.
+         *
+         */
+        quotedMessageId?: string;
         /**
          * Payload from a quick reply tap (Facebook/Instagram Messenger).
          */
@@ -17069,7 +17077,7 @@ type SendInboxMessageData = {
          */
         messageTag?: 'CONFIRMED_EVENT_UPDATE' | 'POST_PURCHASE_UPDATE' | 'ACCOUNT_UPDATE' | 'HUMAN_AGENT';
         /**
-         * Platform message ID to quote-reply to. For WhatsApp, pass the wamid (available in message.platformMessageId from webhooks). For Telegram, pass the Telegram message ID.
+         * Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID; for Instagram, the Meta mid (all available in message.platformMessageId from webhooks or the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without reply support, including Facebook Messenger (Meta's Messenger Send API has no reply_to).
          */
         replyTo?: string;
         /**
@@ -25829,6 +25837,10 @@ type UpdateAdSetData = {
             promotedObject?: {
                 pixelId?: string;
                 customEventType?: string;
+                /**
+                 * Pixel custom-event name (custom_event_str); requires customEventType OTHER. Same pairing rules as /v1/ads/create.
+                 */
+                customEventStr?: string;
                 pageId?: string;
                 applicationId?: string;
                 objectStoreUrl?: string;
@@ -27931,7 +27943,7 @@ type CreateStandaloneAdData = {
          * Required on legacy and multi-creative shapes; the attach shape inherits it from the ad set. Available goals vary by platform.
          *
          * **Meta**
-         * - `conversions`: OUTCOME_SALES. Requires `promotedObject.pixelId` and `promotedObject.customEventType` with a commerce event such as PURCHASE or START_TRIAL, or `promotedObject.customConversionId` to optimise against a Custom Conversion instead.
+         * - `conversions`: OUTCOME_SALES. Requires `promotedObject.pixelId` and `promotedObject.customEventType` with a commerce event such as PURCHASE or START_TRIAL, or `promotedObject.customConversionId` to optimise against a Custom Conversion, or `customEventType: OTHER` + `customEventStr` to optimise against a pixel custom event.
          * - `lead_conversion`: OUTCOME_LEADS optimizing website pixel leads. Same pixel and event fields, but with a leads-class event such as LEAD, SUBMIT_APPLICATION, SCHEDULE or CONTACT (or `promotedObject.customConversionId` to optimise against a Custom Conversion instead). Meta gates conversion events by objective, so leads-class events are rejected under `conversions`.
          * - `lead_generation`: OUTCOME_LEADS with instant forms. Requires `leadGenFormId`. `promotedObject.pageId` is optional and auto-filled from the connected Page.
          * - `app_promotion`: requires `promotedObject.applicationId` and `promotedObject.objectStoreUrl`.
@@ -28731,7 +28743,7 @@ type CreateStandaloneAdData = {
          * Required for goals whose ad-set optimization_goal points at a specific
          * event/page/app (without it Meta rejects the ad-set create with
          * `error_subcode: 1815430` "Please select a promoted object for your ad set"):
-         * - `goal: conversions` / `lead_conversion` (OFFSITE_CONVERSIONS): requires `pixelId` + `customEventType`, or `customConversionId` when optimising against a Custom Conversion (the conversion carries its own event definition)
+         * - `goal: conversions` / `lead_conversion` (OFFSITE_CONVERSIONS): requires `pixelId` + `customEventType`, or `customConversionId` when optimising against a Custom Conversion (the conversion carries its own event definition). For a pixel CUSTOM event (one you named yourself in CAPI/Events Manager), send `customEventType: OTHER` + `customEventStr` with the event name.
          * - `goal: app_promotion` (APP_INSTALLS): requires `applicationId` + `objectStoreUrl`
          * - `goal: lead_generation` (LEAD_GENERATION): `pageId` is auto-filled from the connected Page when omitted
          *
@@ -28780,6 +28792,17 @@ type CreateStandaloneAdData = {
              *
              */
             customEventType?: string;
+            /**
+             * Meta only. Pixel custom-event name to optimise against (Meta's
+             * `custom_event_str`), exactly as it appears in Events Manager and in your
+             * CAPI payloads (case-sensitive, not uppercased). Requires
+             * `customEventType: OTHER`, and `OTHER` requires this field (400 either way).
+             * The same as picking a custom event in Ads Manager's conversion-event
+             * dropdown. For rule-based Custom Conversions use `customConversionId`
+             * instead.
+             *
+             */
+            customEventStr?: string;
             /**
              * Facebook Page ID. Used by `goal: lead_generation`. Auto-filled from the
              * connected Page when omitted.

package/dist/index.d.ts

@@ -7341,9 +7341,17 @@ type WebhookPayloadMessage = {
     conversation: InboxWebhookConversation;
     account: InboxWebhookAccount;
     /**
-     * Interactive message metadata (present when message is a quick reply tap, postback button tap, or inline keyboard callback)
+     * Platform-specific message context (present when the message is a quick reply tap, postback button tap, inline keyboard callback, or a quote-reply to an earlier message)
      */
     metadata?: {
+        /**
+         * platformMessageId of the message this one is a quote-reply to.
+         * WhatsApp (`context.id`), Instagram and Facebook Messenger
+         * (`reply_to.mid`). On `message.sent` echoes (operator replied
+         * from the native app) this is the only metadata field populated.
+         *
+         */
+        quotedMessageId?: string;
         /**
          * Payload from a quick reply tap (Facebook/Instagram Messenger).
          */
@@ -17069,7 +17077,7 @@ type SendInboxMessageData = {
          */
         messageTag?: 'CONFIRMED_EVENT_UPDATE' | 'POST_PURCHASE_UPDATE' | 'ACCOUNT_UPDATE' | 'HUMAN_AGENT';
         /**
-         * Platform message ID to quote-reply to. For WhatsApp, pass the wamid (available in message.platformMessageId from webhooks). For Telegram, pass the Telegram message ID.
+         * Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID; for Instagram, the Meta mid (all available in message.platformMessageId from webhooks or the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without reply support, including Facebook Messenger (Meta's Messenger Send API has no reply_to).
          */
         replyTo?: string;
         /**
@@ -25829,6 +25837,10 @@ type UpdateAdSetData = {
             promotedObject?: {
                 pixelId?: string;
                 customEventType?: string;
+                /**
+                 * Pixel custom-event name (custom_event_str); requires customEventType OTHER. Same pairing rules as /v1/ads/create.
+                 */
+                customEventStr?: string;
                 pageId?: string;
                 applicationId?: string;
                 objectStoreUrl?: string;
@@ -27931,7 +27943,7 @@ type CreateStandaloneAdData = {
          * Required on legacy and multi-creative shapes; the attach shape inherits it from the ad set. Available goals vary by platform.
          *
          * **Meta**
-         * - `conversions`: OUTCOME_SALES. Requires `promotedObject.pixelId` and `promotedObject.customEventType` with a commerce event such as PURCHASE or START_TRIAL, or `promotedObject.customConversionId` to optimise against a Custom Conversion instead.
+         * - `conversions`: OUTCOME_SALES. Requires `promotedObject.pixelId` and `promotedObject.customEventType` with a commerce event such as PURCHASE or START_TRIAL, or `promotedObject.customConversionId` to optimise against a Custom Conversion, or `customEventType: OTHER` + `customEventStr` to optimise against a pixel custom event.
          * - `lead_conversion`: OUTCOME_LEADS optimizing website pixel leads. Same pixel and event fields, but with a leads-class event such as LEAD, SUBMIT_APPLICATION, SCHEDULE or CONTACT (or `promotedObject.customConversionId` to optimise against a Custom Conversion instead). Meta gates conversion events by objective, so leads-class events are rejected under `conversions`.
          * - `lead_generation`: OUTCOME_LEADS with instant forms. Requires `leadGenFormId`. `promotedObject.pageId` is optional and auto-filled from the connected Page.
          * - `app_promotion`: requires `promotedObject.applicationId` and `promotedObject.objectStoreUrl`.
@@ -28731,7 +28743,7 @@ type CreateStandaloneAdData = {
          * Required for goals whose ad-set optimization_goal points at a specific
          * event/page/app (without it Meta rejects the ad-set create with
          * `error_subcode: 1815430` "Please select a promoted object for your ad set"):
-         * - `goal: conversions` / `lead_conversion` (OFFSITE_CONVERSIONS): requires `pixelId` + `customEventType`, or `customConversionId` when optimising against a Custom Conversion (the conversion carries its own event definition)
+         * - `goal: conversions` / `lead_conversion` (OFFSITE_CONVERSIONS): requires `pixelId` + `customEventType`, or `customConversionId` when optimising against a Custom Conversion (the conversion carries its own event definition). For a pixel CUSTOM event (one you named yourself in CAPI/Events Manager), send `customEventType: OTHER` + `customEventStr` with the event name.
          * - `goal: app_promotion` (APP_INSTALLS): requires `applicationId` + `objectStoreUrl`
          * - `goal: lead_generation` (LEAD_GENERATION): `pageId` is auto-filled from the connected Page when omitted
          *
@@ -28780,6 +28792,17 @@ type CreateStandaloneAdData = {
              *
              */
             customEventType?: string;
+            /**
+             * Meta only. Pixel custom-event name to optimise against (Meta's
+             * `custom_event_str`), exactly as it appears in Events Manager and in your
+             * CAPI payloads (case-sensitive, not uppercased). Requires
+             * `customEventType: OTHER`, and `OTHER` requires this field (400 either way).
+             * The same as picking a custom event in Ads Manager's conversion-event
+             * dropdown. For rule-based Custom Conversions use `customConversionId`
+             * instead.
+             *
+             */
+            customEventStr?: string;
             /**
              * Facebook Page ID. Used by `goal: lead_generation`. Auto-filled from the
              * connected Page when omitted.

package/dist/index.js

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

package/src/generated/types.gen.ts

@@ -6367,9 +6367,17 @@ export type WebhookPayloadMessage = {
     conversation: InboxWebhookConversation;
     account: InboxWebhookAccount;
     /**
-     * Interactive message metadata (present when message is a quick reply tap, postback button tap, or inline keyboard callback)
+     * Platform-specific message context (present when the message is a quick reply tap, postback button tap, inline keyboard callback, or a quote-reply to an earlier message)
      */
     metadata?: {
+        /**
+         * platformMessageId of the message this one is a quote-reply to.
+         * WhatsApp (`context.id`), Instagram and Facebook Messenger
+         * (`reply_to.mid`). On `message.sent` echoes (operator replied
+         * from the native app) this is the only metadata field populated.
+         *
+         */
+        quotedMessageId?: string;
         /**
          * Payload from a quick reply tap (Facebook/Instagram Messenger).
          */
@@ -16734,7 +16742,7 @@ export type SendInboxMessageData = {
          */
         messageTag?: 'CONFIRMED_EVENT_UPDATE' | 'POST_PURCHASE_UPDATE' | 'ACCOUNT_UPDATE' | 'HUMAN_AGENT';
         /**
-         * Platform message ID to quote-reply to. For WhatsApp, pass the wamid (available in message.platformMessageId from webhooks). For Telegram, pass the Telegram message ID.
+         * Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID; for Instagram, the Meta mid (all available in message.platformMessageId from webhooks or the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without reply support, including Facebook Messenger (Meta's Messenger Send API has no reply_to).
          */
         replyTo?: string;
         /**
@@ -26229,6 +26237,10 @@ export type UpdateAdSetData = {
             promotedObject?: {
                 pixelId?: string;
                 customEventType?: string;
+                /**
+                 * Pixel custom-event name (custom_event_str); requires customEventType OTHER. Same pairing rules as /v1/ads/create.
+                 */
+                customEventStr?: string;
                 pageId?: string;
                 applicationId?: string;
                 objectStoreUrl?: string;
@@ -28469,7 +28481,7 @@ export type CreateStandaloneAdData = {
          * Required on legacy and multi-creative shapes; the attach shape inherits it from the ad set. Available goals vary by platform.
          *
          * **Meta**
-         * - `conversions`: OUTCOME_SALES. Requires `promotedObject.pixelId` and `promotedObject.customEventType` with a commerce event such as PURCHASE or START_TRIAL, or `promotedObject.customConversionId` to optimise against a Custom Conversion instead.
+         * - `conversions`: OUTCOME_SALES. Requires `promotedObject.pixelId` and `promotedObject.customEventType` with a commerce event such as PURCHASE or START_TRIAL, or `promotedObject.customConversionId` to optimise against a Custom Conversion, or `customEventType: OTHER` + `customEventStr` to optimise against a pixel custom event.
          * - `lead_conversion`: OUTCOME_LEADS optimizing website pixel leads. Same pixel and event fields, but with a leads-class event such as LEAD, SUBMIT_APPLICATION, SCHEDULE or CONTACT (or `promotedObject.customConversionId` to optimise against a Custom Conversion instead). Meta gates conversion events by objective, so leads-class events are rejected under `conversions`.
          * - `lead_generation`: OUTCOME_LEADS with instant forms. Requires `leadGenFormId`. `promotedObject.pageId` is optional and auto-filled from the connected Page.
          * - `app_promotion`: requires `promotedObject.applicationId` and `promotedObject.objectStoreUrl`.
@@ -29269,7 +29281,7 @@ export type CreateStandaloneAdData = {
          * Required for goals whose ad-set optimization_goal points at a specific
          * event/page/app (without it Meta rejects the ad-set create with
          * `error_subcode: 1815430` "Please select a promoted object for your ad set"):
-         * - `goal: conversions` / `lead_conversion` (OFFSITE_CONVERSIONS): requires `pixelId` + `customEventType`, or `customConversionId` when optimising against a Custom Conversion (the conversion carries its own event definition)
+         * - `goal: conversions` / `lead_conversion` (OFFSITE_CONVERSIONS): requires `pixelId` + `customEventType`, or `customConversionId` when optimising against a Custom Conversion (the conversion carries its own event definition). For a pixel CUSTOM event (one you named yourself in CAPI/Events Manager), send `customEventType: OTHER` + `customEventStr` with the event name.
          * - `goal: app_promotion` (APP_INSTALLS): requires `applicationId` + `objectStoreUrl`
          * - `goal: lead_generation` (LEAD_GENERATION): `pageId` is auto-filled from the connected Page when omitted
          *
@@ -29318,6 +29330,17 @@ export type CreateStandaloneAdData = {
              *
              */
             customEventType?: string;
+            /**
+             * Meta only. Pixel custom-event name to optimise against (Meta's
+             * `custom_event_str`), exactly as it appears in Events Manager and in your
+             * CAPI payloads (case-sensitive, not uppercased). Requires
+             * `customEventType: OTHER`, and `OTHER` requires this field (400 either way).
+             * The same as picking a custom event in Ads Manager's conversion-event
+             * dropdown. For rule-based Custom Conversions use `customConversionId`
+             * instead.
+             *
+             */
+            customEventStr?: string;
             /**
              * Facebook Page ID. Used by `goal: lead_generation`. Auto-filled from the
              * connected Page when omitted.