@zernio/node 0.2.661 → 0.2.663

package/dist/index.d.mts

@@ -18832,6 +18832,27 @@ type CreateInboxConversationData = {
              */
             filename?: string;
         };
+        /**
+         * WhatsApp only. Required to send a template whose approved header format is LOCATION: Meta only accepts the location's lat/long at send time, never at template creation, so there is nothing to fill in automatically. Cannot be combined with headerMedia (a template has exactly one header).
+         */
+        headerLocation?: {
+            /**
+             * Latitude in decimal degrees.
+             */
+            latitude: number;
+            /**
+             * Longitude in decimal degrees.
+             */
+            longitude: number;
+            /**
+             * Location name shown to the recipient (e.g. a business name).
+             */
+            name?: string;
+            /**
+             * Location address shown to the recipient.
+             */
+            address?: string;
+        };
     };
 };
 type CreateInboxConversationResponse = ({
@@ -19907,6 +19928,38 @@ type SendInboxMessageResponse = ({
             type?: string;
             url?: string;
         }>;
+        /**
+         * Facebook/Instagram only. Present when an attachment and text were both requested: Meta has no single body shape for both, so the send is two Meta messages under the hood. First element === messageId (the attachment); second is the follow-up text.
+         */
+        messageIds?: Array<(string)>;
+        /**
+         * Facebook/Instagram only. The attachment was delivered but the follow-up text message was rejected by Meta and was not stored; the response is still a 200 because the attachment send succeeded.
+         */
+        partialFailure?: {
+            part?: 'text';
+            error?: string;
+            /**
+             * Meta's own diagnostic fields for the rejected follow-up, same shape as the 400 response's platformError.
+             */
+            platformError?: {
+                /**
+                 * Meta error code
+                 */
+                code?: number;
+                /**
+                 * Meta error_subcode
+                 */
+                subcode?: number;
+                /**
+                 * Meta fbtrace_id, quote this in a Meta bug report
+                 */
+                fbtraceId?: string;
+                /**
+                 * Meta error type (e.g. OAuthException)
+                 */
+                type?: string;
+            };
+        };
     };
 });
 type SendInboxMessageError = ({

package/dist/index.d.ts

@@ -18832,6 +18832,27 @@ type CreateInboxConversationData = {
              */
             filename?: string;
         };
+        /**
+         * WhatsApp only. Required to send a template whose approved header format is LOCATION: Meta only accepts the location's lat/long at send time, never at template creation, so there is nothing to fill in automatically. Cannot be combined with headerMedia (a template has exactly one header).
+         */
+        headerLocation?: {
+            /**
+             * Latitude in decimal degrees.
+             */
+            latitude: number;
+            /**
+             * Longitude in decimal degrees.
+             */
+            longitude: number;
+            /**
+             * Location name shown to the recipient (e.g. a business name).
+             */
+            name?: string;
+            /**
+             * Location address shown to the recipient.
+             */
+            address?: string;
+        };
     };
 };
 type CreateInboxConversationResponse = ({
@@ -19907,6 +19928,38 @@ type SendInboxMessageResponse = ({
             type?: string;
             url?: string;
         }>;
+        /**
+         * Facebook/Instagram only. Present when an attachment and text were both requested: Meta has no single body shape for both, so the send is two Meta messages under the hood. First element === messageId (the attachment); second is the follow-up text.
+         */
+        messageIds?: Array<(string)>;
+        /**
+         * Facebook/Instagram only. The attachment was delivered but the follow-up text message was rejected by Meta and was not stored; the response is still a 200 because the attachment send succeeded.
+         */
+        partialFailure?: {
+            part?: 'text';
+            error?: string;
+            /**
+             * Meta's own diagnostic fields for the rejected follow-up, same shape as the 400 response's platformError.
+             */
+            platformError?: {
+                /**
+                 * Meta error code
+                 */
+                code?: number;
+                /**
+                 * Meta error_subcode
+                 */
+                subcode?: number;
+                /**
+                 * Meta fbtrace_id, quote this in a Meta bug report
+                 */
+                fbtraceId?: string;
+                /**
+                 * Meta error type (e.g. OAuthException)
+                 */
+                type?: string;
+            };
+        };
     };
 });
 type SendInboxMessageError = ({

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -3305,7 +3305,7 @@ export const listInboxConversations = <ThrowOnError extends boolean = false>(opt
  *
  * Slack: pass a workspace member id as participantId (list them with GET /v1/accounts/{accountId}/slack-members). Zernio opens the DM channel with that member and sends the message; the thread then behaves like any other Slack conversation in the inbox. The member must belong to the connected workspace.
  *
- * WhatsApp: this is the endpoint for sending an approved template message to a phone number. Provide templateName, templateLanguage, and templateParams (variable values for the text header, body and dynamic URL buttons, in that order), with the recipient phone in participantId. A template is required because WhatsApp does not permit freeform messages to open a conversation; a missing template returns TEMPLATE_REQUIRED. Templates with media headers (image, video, document) are handled automatically: Zernio reads the approved template definition and fills the header at send time with the template's approved sample asset. To send a DIFFERENT asset per message (e.g. a distinct invoice PDF for each recipient), pass the headerMedia field with a public link (or a Meta media id); it overrides the sample for that send. A button that carries its own value at send time (a copy-code button holding a Pix payment code or a coupon, a flow token) is sent with templateButtonParams, addressed by the button's index; templateParams covers text variables and dynamic URL buttons only. Calling this for a number you already have a thread with simply sends the template into that thread, which also makes it the way to re-engage a contact after the 24-hour customer-service window has closed. Once the recipient replies (opening the 24h window), send freeform messages with the send-message endpoint (POST /v1/inbox/conversations/{conversationId}/messages). Template fields are accepted on the JSON body only, not on multipart requests. Alternatively, WhatsApp Business Accounts eligible for Meta Direct Send can open a conversation with a business-initiated utility text message and no template: pass category: 'utility' together with message (and no templateName). See the category field below.
+ * WhatsApp: this is the endpoint for sending an approved template message to a phone number. Provide templateName, templateLanguage, and templateParams (variable values for the text header, body and dynamic URL buttons, in that order), with the recipient phone in participantId. A template is required because WhatsApp does not permit freeform messages to open a conversation; a missing template returns TEMPLATE_REQUIRED. Templates with media headers (image, video, document) are handled automatically: Zernio reads the approved template definition and fills the header at send time with the template's approved sample asset. To send a DIFFERENT asset per message (e.g. a distinct invoice PDF for each recipient), pass the headerMedia field with a public link (or a Meta media id); it overrides the sample for that send. A template whose approved header format is LOCATION has no header asset to reconstruct at all: Meta only accepts the location at send time, so pass headerLocation (latitude and longitude required) whenever such a template is sent; headerMedia and headerLocation cannot both be supplied. A button that carries its own value at send time (a copy-code button holding a Pix payment code or a coupon, a flow token) is sent with templateButtonParams, addressed by the button's index; templateParams covers text variables and dynamic URL buttons only. Calling this for a number you already have a thread with simply sends the template into that thread, which also makes it the way to re-engage a contact after the 24-hour customer-service window has closed. Once the recipient replies (opening the 24h window), send freeform messages with the send-message endpoint (POST /v1/inbox/conversations/{conversationId}/messages). Template fields are accepted on the JSON body only, not on multipart requests. Alternatively, WhatsApp Business Accounts eligible for Meta Direct Send can open a conversation with a business-initiated utility text message and no template: pass category: 'utility' together with message (and no templateName). See the category field below.
  *
  * DM eligibility (X/Twitter): Before sending, the endpoint checks if the recipient accepts DMs from your account (via the receives_your_dm field). If not, a 422 error with code DM_NOT_ALLOWED is returned. You can skip this check with skipDmCheck: true if you have already verified eligibility.
  *

package/src/generated/types.gen.ts

@@ -18471,6 +18471,27 @@ export type CreateInboxConversationData = {
              */
             filename?: string;
         };
+        /**
+         * WhatsApp only. Required to send a template whose approved header format is LOCATION: Meta only accepts the location's lat/long at send time, never at template creation, so there is nothing to fill in automatically. Cannot be combined with headerMedia (a template has exactly one header).
+         */
+        headerLocation?: {
+            /**
+             * Latitude in decimal degrees.
+             */
+            latitude: number;
+            /**
+             * Longitude in decimal degrees.
+             */
+            longitude: number;
+            /**
+             * Location name shown to the recipient (e.g. a business name).
+             */
+            name?: string;
+            /**
+             * Location address shown to the recipient.
+             */
+            address?: string;
+        };
     };
 };
 
@@ -19562,6 +19583,38 @@ export type SendInboxMessageResponse = ({
             type?: string;
             url?: string;
         }>;
+        /**
+         * Facebook/Instagram only. Present when an attachment and text were both requested: Meta has no single body shape for both, so the send is two Meta messages under the hood. First element === messageId (the attachment); second is the follow-up text.
+         */
+        messageIds?: Array<(string)>;
+        /**
+         * Facebook/Instagram only. The attachment was delivered but the follow-up text message was rejected by Meta and was not stored; the response is still a 200 because the attachment send succeeded.
+         */
+        partialFailure?: {
+            part?: 'text';
+            error?: string;
+            /**
+             * Meta's own diagnostic fields for the rejected follow-up, same shape as the 400 response's platformError.
+             */
+            platformError?: {
+                /**
+                 * Meta error code
+                 */
+                code?: number;
+                /**
+                 * Meta error_subcode
+                 */
+                subcode?: number;
+                /**
+                 * Meta fbtrace_id, quote this in a Meta bug report
+                 */
+                fbtraceId?: string;
+                /**
+                 * Meta error type (e.g. OAuthException)
+                 */
+                type?: string;
+            };
+        };
     };
 });