@zernio/node 0.2.723 → 0.2.725

package/dist/index.d.mts

@@ -20917,7 +20917,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; for Telegram, the Telegram message ID (delivered as message.platformMessageId on webhooks, and as `id` on each entry of the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without send-side reply support, including Instagram and Facebook Messenger (Meta's Send API rejects reply_to on Instagram and does not expose it on Messenger).
+         * Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID (delivered as message.platformMessageId on webhooks, and as `id` on each entry of the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Instagram and Facebook Messenger do not support send-side quote replies: the message is sent without a quote and the successful response includes a warnings entry with code ignored_field and param replyTo. Other platforms without send-side reply support ignore this field.
          */
         replyTo?: string;
         /**
@@ -20981,6 +20981,17 @@ type SendInboxMessageData = {
 };
 type SendInboxMessageResponse = ({
     success?: boolean;
+    /**
+     * Present when a successful send ignored replyTo on Instagram or Facebook Messenger. The message was sent without a quote; do not retry it to apply the reply.
+     */
+    warnings?: Array<{
+        code: 'ignored_field';
+        param: 'replyTo';
+        /**
+         * Human-readable explanation of the ignored field.
+         */
+        message: string;
+    }>;
     data?: {
         /**
          * Platform id of the sent message (not returned for Reddit). For WhatsApp this is the raw Meta wamid, the same id delivered as message.platformMessageId on webhooks and delivery-status updates, and the value to pass as replyTo to quote-reply.
@@ -22735,7 +22746,7 @@ type CreateWhatsAppTemplateData = {
             phone_number?: string;
         }>;
         /**
-         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 restores the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
+         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 (create only) keeps the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
          */
         message_send_ttl_seconds?: number;
     };
@@ -22837,7 +22848,7 @@ type UpdateWhatsAppTemplateData = {
          */
         components?: Array<WhatsAppTemplateComponent>;
         /**
-         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 restores the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
+         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 is not accepted here (Meta treats it as an empty edit); send a value in range. A TTL-only edit keeps an APPROVED template approved, no re-review. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
          */
         message_send_ttl_seconds?: number;
     };
@@ -22979,7 +22990,7 @@ type UpdateWhatsAppTemplateByIdData = {
          */
         components?: Array<WhatsAppTemplateComponent>;
         /**
-         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 restores the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
+         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 is not accepted here (Meta treats it as an empty edit); send a value in range. A TTL-only edit keeps an APPROVED template approved, no re-review. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
          */
         message_send_ttl_seconds?: number;
     };
@@ -28064,7 +28075,7 @@ type ListContactsData = {
         accountId?: string;
         isSubscribed?: 'true' | 'false';
         limit?: number;
-        platform?: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack';
+        platform?: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack' | 'sms';
         /**
          * Filter by profile. Omit to list across all profiles. Matches the profile recorded on the contact itself, which is set when the contact is created and is independent of the profile its account currently belongs to. Filter by accountId to list a contact through its channel instead.
          */
@@ -28134,7 +28145,7 @@ type CreateContactData = {
         /**
          * Channel platform. Only the enum values support contact channels; any other platform is rejected with code platform_not_supported.
          */
-        platform?: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack';
+        platform?: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack' | 'sms';
         platformIdentifier?: string;
         displayIdentifier?: string;
     };
@@ -28491,7 +28502,7 @@ type CreateBroadcastData = {
     body: {
         profileId: string;
         accountId: string;
-        platform: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp';
+        platform: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'sms' | 'slack';
         name: string;
         description?: string;
         message?: {
@@ -29221,7 +29232,7 @@ type CreateSequenceData = {
     body: {
         profileId: string;
         accountId: string;
-        platform: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp';
+        platform: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack';
         name: string;
         description?: string;
         steps?: Array<{
@@ -31681,14 +31692,28 @@ type UpdateAdData = {
          */
         targeting?: {
             /**
-             * Google only. The FULL new set of positive keywords for the ad group; live keywords not listed are removed. Entries are strings (BROAD) or { text, matchType } with matchType exact | phrase | broad. Mirrored to GET /v1/ads/keywords immediately.
+             * Google only. The FULL desired set of positive keywords for the entire ad group.
+             * Omit to leave positives unchanged; [] removes all positives. Negatives are independent.
+             * Entries are strings (BROAD) or { text, matchType } with matchType exact | phrase | broad;
+             * an omitted matchType also defaults to BROAD. Matching case-insensitive text AND match type
+             * retains the existing criterion ID, status, bid overrides, labels and history without a mutation.
+             * A changed text or match type uses remove/create, without transferring the old criterion's
+             * attributes or history. See Google keyword replacement above for an EXACT-to-BROAD example.
+             * Mirrored to GET /v1/ads/keywords immediately.
+             *
              */
             keywords?: Array<(string | {
                 text: string;
                 matchType?: 'exact' | 'phrase' | 'broad';
             })>;
             /**
-             * Google only. Same declarative contract as keywords, for the ad group's negative keywords.
+             * Google only. The FULL desired set of negative keywords for the entire ad group,
+             * independent of positives. Omit to leave negatives unchanged; [] removes all negatives.
+             * Uses the same text/match-type identity and preservation contract as keywords above.
+             * Strings and objects without matchType default to BROAD, so resending an EXACT or PHRASE
+             * negative as a bare string requests a different criterion. Campaign negatives are separate:
+             * use /v1/ads/campaigns/{campaignId}/negative-keywords to manage those.
+             *
              */
             negativeKeywords?: Array<(string | {
                 text: string;
@@ -33943,14 +33968,16 @@ type CreateStandaloneAdData = {
          * multiple ads per ad set are allowed (unlike `dynamicCreative` which is limited to one).
          * Requires `imageUrl` or `video`, `linkUrl`, and `callToAction`. When set, the top-level
          * `body` field is used as the `object_story_spec.link_data.message` (the preview text) and
-         * `headlines` must also be present. Mutually exclusive with `dynamicCreative`,
-         * `placementAssets`, `carouselCards`, and `creatives[]`.
+         * `headlines` must also be present. On a video creative the copy lands in
+         * `video_data.message` / `video_data.title` instead of `link_data`. Mutually exclusive
+         * with `dynamicCreative`, `placementAssets`, `carouselCards`, and `creatives[]`.
          *
          */
         bodies?: Array<(string)>;
         /**
          * Meta only. Headline variations for Multiple Text Options. Must be sent alongside `bodies`.
-         * The top-level `headline` field is used as the `object_story_spec.link_data.name`.
+         * The top-level `headline` field is used as the `object_story_spec.link_data.name`
+         * (`video_data.title` on a video creative).
          *
          */
         headlines?: Array<(string)>;
@@ -35187,6 +35214,9 @@ type CreateLeadFormData = {
                 content?: Array<(string)>;
                 style?: 'LIST_STYLE' | 'PARAGRAPH_STYLE';
                 buttonText?: string;
+                /**
+                 * Direct public JPEG or PNG image URL, up to 5 MB. Redirects, Ad Image hashes and IDs are not supported.
+                 */
                 coverPhoto?: string;
             };
         } | {

package/dist/index.d.ts

@@ -20917,7 +20917,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; for Telegram, the Telegram message ID (delivered as message.platformMessageId on webhooks, and as `id` on each entry of the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without send-side reply support, including Instagram and Facebook Messenger (Meta's Send API rejects reply_to on Instagram and does not expose it on Messenger).
+         * Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID (delivered as message.platformMessageId on webhooks, and as `id` on each entry of the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Instagram and Facebook Messenger do not support send-side quote replies: the message is sent without a quote and the successful response includes a warnings entry with code ignored_field and param replyTo. Other platforms without send-side reply support ignore this field.
          */
         replyTo?: string;
         /**
@@ -20981,6 +20981,17 @@ type SendInboxMessageData = {
 };
 type SendInboxMessageResponse = ({
     success?: boolean;
+    /**
+     * Present when a successful send ignored replyTo on Instagram or Facebook Messenger. The message was sent without a quote; do not retry it to apply the reply.
+     */
+    warnings?: Array<{
+        code: 'ignored_field';
+        param: 'replyTo';
+        /**
+         * Human-readable explanation of the ignored field.
+         */
+        message: string;
+    }>;
     data?: {
         /**
          * Platform id of the sent message (not returned for Reddit). For WhatsApp this is the raw Meta wamid, the same id delivered as message.platformMessageId on webhooks and delivery-status updates, and the value to pass as replyTo to quote-reply.
@@ -22735,7 +22746,7 @@ type CreateWhatsAppTemplateData = {
             phone_number?: string;
         }>;
         /**
-         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 restores the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
+         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 (create only) keeps the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
          */
         message_send_ttl_seconds?: number;
     };
@@ -22837,7 +22848,7 @@ type UpdateWhatsAppTemplateData = {
          */
         components?: Array<WhatsAppTemplateComponent>;
         /**
-         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 restores the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
+         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 is not accepted here (Meta treats it as an empty edit); send a value in range. A TTL-only edit keeps an APPROVED template approved, no re-review. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
          */
         message_send_ttl_seconds?: number;
     };
@@ -22979,7 +22990,7 @@ type UpdateWhatsAppTemplateByIdData = {
          */
         components?: Array<WhatsAppTemplateComponent>;
         /**
-         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 restores the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
+         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 is not accepted here (Meta treats it as an empty edit); send a value in range. A TTL-only edit keeps an APPROVED template approved, no re-review. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
          */
         message_send_ttl_seconds?: number;
     };
@@ -28064,7 +28075,7 @@ type ListContactsData = {
         accountId?: string;
         isSubscribed?: 'true' | 'false';
         limit?: number;
-        platform?: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack';
+        platform?: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack' | 'sms';
         /**
          * Filter by profile. Omit to list across all profiles. Matches the profile recorded on the contact itself, which is set when the contact is created and is independent of the profile its account currently belongs to. Filter by accountId to list a contact through its channel instead.
          */
@@ -28134,7 +28145,7 @@ type CreateContactData = {
         /**
          * Channel platform. Only the enum values support contact channels; any other platform is rejected with code platform_not_supported.
          */
-        platform?: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack';
+        platform?: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack' | 'sms';
         platformIdentifier?: string;
         displayIdentifier?: string;
     };
@@ -28491,7 +28502,7 @@ type CreateBroadcastData = {
     body: {
         profileId: string;
         accountId: string;
-        platform: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp';
+        platform: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'sms' | 'slack';
         name: string;
         description?: string;
         message?: {
@@ -29221,7 +29232,7 @@ type CreateSequenceData = {
     body: {
         profileId: string;
         accountId: string;
-        platform: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp';
+        platform: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack';
         name: string;
         description?: string;
         steps?: Array<{
@@ -31681,14 +31692,28 @@ type UpdateAdData = {
          */
         targeting?: {
             /**
-             * Google only. The FULL new set of positive keywords for the ad group; live keywords not listed are removed. Entries are strings (BROAD) or { text, matchType } with matchType exact | phrase | broad. Mirrored to GET /v1/ads/keywords immediately.
+             * Google only. The FULL desired set of positive keywords for the entire ad group.
+             * Omit to leave positives unchanged; [] removes all positives. Negatives are independent.
+             * Entries are strings (BROAD) or { text, matchType } with matchType exact | phrase | broad;
+             * an omitted matchType also defaults to BROAD. Matching case-insensitive text AND match type
+             * retains the existing criterion ID, status, bid overrides, labels and history without a mutation.
+             * A changed text or match type uses remove/create, without transferring the old criterion's
+             * attributes or history. See Google keyword replacement above for an EXACT-to-BROAD example.
+             * Mirrored to GET /v1/ads/keywords immediately.
+             *
              */
             keywords?: Array<(string | {
                 text: string;
                 matchType?: 'exact' | 'phrase' | 'broad';
             })>;
             /**
-             * Google only. Same declarative contract as keywords, for the ad group's negative keywords.
+             * Google only. The FULL desired set of negative keywords for the entire ad group,
+             * independent of positives. Omit to leave negatives unchanged; [] removes all negatives.
+             * Uses the same text/match-type identity and preservation contract as keywords above.
+             * Strings and objects without matchType default to BROAD, so resending an EXACT or PHRASE
+             * negative as a bare string requests a different criterion. Campaign negatives are separate:
+             * use /v1/ads/campaigns/{campaignId}/negative-keywords to manage those.
+             *
              */
             negativeKeywords?: Array<(string | {
                 text: string;
@@ -33943,14 +33968,16 @@ type CreateStandaloneAdData = {
          * multiple ads per ad set are allowed (unlike `dynamicCreative` which is limited to one).
          * Requires `imageUrl` or `video`, `linkUrl`, and `callToAction`. When set, the top-level
          * `body` field is used as the `object_story_spec.link_data.message` (the preview text) and
-         * `headlines` must also be present. Mutually exclusive with `dynamicCreative`,
-         * `placementAssets`, `carouselCards`, and `creatives[]`.
+         * `headlines` must also be present. On a video creative the copy lands in
+         * `video_data.message` / `video_data.title` instead of `link_data`. Mutually exclusive
+         * with `dynamicCreative`, `placementAssets`, `carouselCards`, and `creatives[]`.
          *
          */
         bodies?: Array<(string)>;
         /**
          * Meta only. Headline variations for Multiple Text Options. Must be sent alongside `bodies`.
-         * The top-level `headline` field is used as the `object_story_spec.link_data.name`.
+         * The top-level `headline` field is used as the `object_story_spec.link_data.name`
+         * (`video_data.title` on a video creative).
          *
          */
         headlines?: Array<(string)>;
@@ -35187,6 +35214,9 @@ type CreateLeadFormData = {
                 content?: Array<(string)>;
                 style?: 'LIST_STYLE' | 'PARAGRAPH_STYLE';
                 buttonText?: string;
+                /**
+                 * Direct public JPEG or PNG image URL, up to 5 MB. Redirects, Ad Image hashes and IDs are not supported.
+                 */
                 coverPhoto?: string;
             };
         } | {

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -4482,8 +4482,9 @@ export const getWhatsAppTemplate = <ThrowOnError extends boolean = false>(option
  * must match exactly. Variants in `PENDING_DELETION` are not part of the family.
  *
  * Meta only allows editing templates in `APPROVED`, `REJECTED` or `PAUSED` state; an approved
- * template can be edited once per 24 hours and up to 10 times per 30 days. A successful update
- * sends the variant back to Meta for review, so the `status` returned here is normally `PENDING`.
+ * template can be edited once per 24 hours and up to 10 times per 30 days. A component update
+ * sends the variant back to Meta for review, so the `status` returned here is normally `PENDING`;
+ * a TTL-only update keeps an APPROVED variant approved.
  * The final outcome arrives on the `whatsapp.template.status_updated` webhook (which carries the
  * variant's `templateId` and `language`). A variant already in `PENDING` cannot be edited again
  * until Meta finishes reviewing it.
@@ -4531,8 +4532,9 @@ export const getWhatsAppTemplateById = <ThrowOnError extends boolean = false>(op
  * Update one variant's components and/or its message_send_ttl_seconds by its Meta id. Name, language and category cannot change.
  *
  * Meta only allows editing templates in `APPROVED`, `REJECTED` or `PAUSED` state; an approved
- * template can be edited once per 24 hours and up to 10 times per 30 days. A successful update
- * sends the variant back to Meta for review, so the `status` returned here is normally `PENDING`.
+ * template can be edited once per 24 hours and up to 10 times per 30 days. A component update
+ * sends the variant back to Meta for review, so the `status` returned here is normally `PENDING`;
+ * a TTL-only update keeps an APPROVED variant approved.
  * The final outcome arrives on the `whatsapp.template.status_updated` webhook (which carries the
  * variant's `templateId` and `language`). A variant already in `PENDING` cannot be edited again
  * until Meta finishes reviewing it.
@@ -8465,6 +8467,32 @@ export const getAd = <ThrowOnError extends boolean = false>(options: OptionsLega
  * `targeting` or `creative` returns 501 with code `unsupported_platform_operation`.
  * OpenAI Ads budget is lifetime-only (see `budget.type` below).
  *
+ * **Google keyword replacement:** These edits affect the ad's entire ad group,
+ * including sibling ads. Positive (`targeting.keywords`) and negative
+ * (`targeting.negativeKeywords`) sets are independent: omit a field to leave
+ * that set unchanged, or send `[]` to remove every keyword of that kind.
+ *
+ * Zernio compares each supplied set with Google's live criteria by
+ * case-insensitive keyword text and match type. A matching criterion is left
+ * untouched, retaining its criterion ID, enabled/paused status, keyword-level
+ * bid overrides, labels, and criterion-associated history/statistics. Zernio
+ * does not reset its quality score; Google continues to calculate scores and
+ * statistics normally. Text comparison does not trim whitespace.
+ *
+ * A bare string or an object without `matchType` means `broad`, not the
+ * existing criterion's match type. For example, resending an existing
+ * `{ "text": "plumber", "matchType": "exact" }` preserves it; sending
+ * `"plumber"` instead removes that EXACT criterion and requests a BROAD one.
+ * Changing text or match type removes criteria no longer requested and
+ * creates any missing criteria. New criteria get new IDs and do not inherit
+ * removed criteria's bid overrides, labels, or history. Historical reporting
+ * for a removed criterion is not transferred to its replacement.
+ *
+ * To add keywords without replacing a set, use
+ * [POST /v1/ads/keywords](https://docs.zernio.com/ad-campaigns/add-ad-keywords).
+ * Use `PATCH /v1/ads/keywords/{keywordId}` to pause/enable one keyword, or
+ * `DELETE /v1/ads/keywords/{keywordId}` to remove it.
+ *
  */
 export const updateAd = <ThrowOnError extends boolean = false>(options: OptionsLegacyParser<UpdateAdData, ThrowOnError>) => {
     return (options?.client ?? client).put<UpdateAdResponse, UpdateAdError, ThrowOnError>({

package/src/generated/types.gen.ts

@@ -20530,7 +20530,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; for Telegram, the Telegram message ID (delivered as message.platformMessageId on webhooks, and as `id` on each entry of the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Silently ignored on platforms without send-side reply support, including Instagram and Facebook Messenger (Meta's Send API rejects reply_to on Instagram and does not expose it on Messenger).
+         * Platform message ID to quote-reply to. For WhatsApp, pass the wamid; for Telegram, the Telegram message ID (delivered as message.platformMessageId on webhooks, and as `id` on each entry of the list-messages endpoint). On Slack it threads the reply (thread_ts) instead of quoting. Instagram and Facebook Messenger do not support send-side quote replies: the message is sent without a quote and the successful response includes a warnings entry with code ignored_field and param replyTo. Other platforms without send-side reply support ignore this field.
          */
         replyTo?: string;
         /**
@@ -20595,6 +20595,17 @@ export type SendInboxMessageData = {
 
 export type SendInboxMessageResponse = ({
     success?: boolean;
+    /**
+     * Present when a successful send ignored replyTo on Instagram or Facebook Messenger. The message was sent without a quote; do not retry it to apply the reply.
+     */
+    warnings?: Array<{
+        code: 'ignored_field';
+        param: 'replyTo';
+        /**
+         * Human-readable explanation of the ignored field.
+         */
+        message: string;
+    }>;
     data?: {
         /**
          * Platform id of the sent message (not returned for Reddit). For WhatsApp this is the raw Meta wamid, the same id delivered as message.platformMessageId on webhooks and delivery-status updates, and the value to pass as replyTo to quote-reply.
@@ -22486,7 +22497,7 @@ export type CreateWhatsAppTemplateData = {
             phone_number?: string;
         }>;
         /**
-         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 restores the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
+         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 (create only) keeps the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
          */
         message_send_ttl_seconds?: number;
     };
@@ -22594,7 +22605,7 @@ export type UpdateWhatsAppTemplateData = {
          */
         components?: Array<WhatsAppTemplateComponent>;
         /**
-         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 restores the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
+         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 is not accepted here (Meta treats it as an empty edit); send a value in range. A TTL-only edit keeps an APPROVED template approved, no re-review. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
          */
         message_send_ttl_seconds?: number;
     };
@@ -22745,7 +22756,7 @@ export type UpdateWhatsAppTemplateByIdData = {
          */
         components?: Array<WhatsAppTemplateComponent>;
         /**
-         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 restores the 30-day default on AUTHENTICATION and UTILITY. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
+         * Delivery validity window in seconds: a message not delivered within it is dropped. Range depends on category: AUTHENTICATION 30 to 900, UTILITY 30 to 43200 (12h), MARKETING 43200 to 2592000 (30 days); -1 is not accepted here (Meta treats it as an empty edit); send a value in range. A TTL-only edit keeps an APPROVED template approved, no re-review. Meta defaults to 600 for AUTHENTICATION and 30 days otherwise. If Meta later recategorises the template, it clears the TTL (read it back to check).
          */
         message_send_ttl_seconds?: number;
     };
@@ -28275,7 +28286,7 @@ export type ListContactsData = {
         accountId?: string;
         isSubscribed?: 'true' | 'false';
         limit?: number;
-        platform?: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack';
+        platform?: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack' | 'sms';
         /**
          * Filter by profile. Omit to list across all profiles. Matches the profile recorded on the contact itself, which is set when the contact is created and is independent of the profile its account currently belongs to. Filter by accountId to list a contact through its channel instead.
          */
@@ -28348,7 +28359,7 @@ export type CreateContactData = {
         /**
          * Channel platform. Only the enum values support contact channels; any other platform is rejected with code platform_not_supported.
          */
-        platform?: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack';
+        platform?: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack' | 'sms';
         platformIdentifier?: string;
         displayIdentifier?: string;
     };
@@ -28744,7 +28755,7 @@ export type CreateBroadcastData = {
     body: {
         profileId: string;
         accountId: string;
-        platform: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp';
+        platform: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'sms' | 'slack';
         name: string;
         description?: string;
         message?: {
@@ -29546,7 +29557,7 @@ export type CreateSequenceData = {
     body: {
         profileId: string;
         accountId: string;
-        platform: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp';
+        platform: 'instagram' | 'facebook' | 'telegram' | 'twitter' | 'bluesky' | 'reddit' | 'whatsapp' | 'slack';
         name: string;
         description?: string;
         steps?: Array<{
@@ -32153,14 +32164,28 @@ export type UpdateAdData = {
          */
         targeting?: {
             /**
-             * Google only. The FULL new set of positive keywords for the ad group; live keywords not listed are removed. Entries are strings (BROAD) or { text, matchType } with matchType exact | phrase | broad. Mirrored to GET /v1/ads/keywords immediately.
+             * Google only. The FULL desired set of positive keywords for the entire ad group.
+             * Omit to leave positives unchanged; [] removes all positives. Negatives are independent.
+             * Entries are strings (BROAD) or { text, matchType } with matchType exact | phrase | broad;
+             * an omitted matchType also defaults to BROAD. Matching case-insensitive text AND match type
+             * retains the existing criterion ID, status, bid overrides, labels and history without a mutation.
+             * A changed text or match type uses remove/create, without transferring the old criterion's
+             * attributes or history. See Google keyword replacement above for an EXACT-to-BROAD example.
+             * Mirrored to GET /v1/ads/keywords immediately.
+             *
              */
             keywords?: Array<(string | {
     text: string;
     matchType?: 'exact' | 'phrase' | 'broad';
 })>;
             /**
-             * Google only. Same declarative contract as keywords, for the ad group's negative keywords.
+             * Google only. The FULL desired set of negative keywords for the entire ad group,
+             * independent of positives. Omit to leave negatives unchanged; [] removes all negatives.
+             * Uses the same text/match-type identity and preservation contract as keywords above.
+             * Strings and objects without matchType default to BROAD, so resending an EXACT or PHRASE
+             * negative as a bare string requests a different criterion. Campaign negatives are separate:
+             * use /v1/ads/campaigns/{campaignId}/negative-keywords to manage those.
+             *
              */
             negativeKeywords?: Array<(string | {
     text: string;
@@ -34556,14 +34581,16 @@ export type CreateStandaloneAdData = {
          * multiple ads per ad set are allowed (unlike `dynamicCreative` which is limited to one).
          * Requires `imageUrl` or `video`, `linkUrl`, and `callToAction`. When set, the top-level
          * `body` field is used as the `object_story_spec.link_data.message` (the preview text) and
-         * `headlines` must also be present. Mutually exclusive with `dynamicCreative`,
-         * `placementAssets`, `carouselCards`, and `creatives[]`.
+         * `headlines` must also be present. On a video creative the copy lands in
+         * `video_data.message` / `video_data.title` instead of `link_data`. Mutually exclusive
+         * with `dynamicCreative`, `placementAssets`, `carouselCards`, and `creatives[]`.
          *
          */
         bodies?: Array<(string)>;
         /**
          * Meta only. Headline variations for Multiple Text Options. Must be sent alongside `bodies`.
-         * The top-level `headline` field is used as the `object_story_spec.link_data.name`.
+         * The top-level `headline` field is used as the `object_story_spec.link_data.name`
+         * (`video_data.title` on a video creative).
          *
          */
         headlines?: Array<(string)>;
@@ -35809,6 +35836,9 @@ export type CreateLeadFormData = {
         content?: Array<(string)>;
         style?: 'LIST_STYLE' | 'PARAGRAPH_STYLE';
         buttonText?: string;
+        /**
+         * Direct public JPEG or PNG image URL, up to 5 MB. Redirects, Ad Image hashes and IDs are not supported.
+         */
         coverPhoto?: string;
     };
 } | {