@zernio/node 0.2.681 → 0.2.683

package/dist/index.d.mts

@@ -6702,6 +6702,27 @@ type TargetingSpec = {
         id: string;
         name?: string;
     }>;
+    /**
+     * Meta only. Job title entities from /v1/ads/targeting/search?dimension=workPosition. Not interchangeable with the LinkedIn `jobTitles` URN fragments.
+     */
+    workPositions?: Array<{
+        id: string;
+        name?: string;
+    }>;
+    /**
+     * Meta only. Employer entities from /v1/ads/targeting/search?dimension=workEmployer.
+     */
+    workEmployers?: Array<{
+        id: string;
+        name?: string;
+    }>;
+    /**
+     * Meta only. Work-industry entities from /v1/ads/targeting/search?dimension=workIndustry. Not interchangeable with the LinkedIn `industries` URN fragments.
+     */
+    workIndustries?: Array<{
+        id: string;
+        name?: string;
+    }>;
     /**
      * LinkedIn B2B only. Industry URN id fragments.
      */
@@ -6719,11 +6740,11 @@ type TargetingSpec = {
      */
     jobFunctions?: Array<(string)>;
     /**
-     * Platform audience IDs to include. Not supported on any platform (no builder maps it): rejected with a 400 on ad create, boost, and reach estimate.
+     * Platform audience IDs to include, as returned by GET /v1/ads/audiences (Meta custom audience ids, TikTok audience ids, Pinterest customer list ids, LinkedIn segment ids (bare, urn:li:adSegment or urn:li:dmpSegment forms accepted), Google user list ids, X custom audience ids). Not supported on OpenAI (400).
      */
     audienceInclude?: Array<(string)>;
     /**
-     * Platform audience IDs to exclude. Not supported on any platform (no builder maps it): rejected with a 400 on ad create, boost, and reach estimate.
+     * Platform audience IDs to exclude; same ID formats as audienceInclude. Not supported on OpenAI (400).
      */
     audienceExclude?: Array<(string)>;
 };
@@ -8585,8 +8606,9 @@ type WebhookPayloadMessage = {
         /**
          * platformMessageId of the message this one is a quote-reply to.
          * WhatsApp (`context.id`), Instagram and Facebook Messenger
-         * (`reply_to.mid`). Outgoing quote-replies carry the same field on
-         * `message.sent`; see WebhookPayloadMessageSent.metadata.
+         * (`reply_to.mid`). On outgoing messages the same field appears on
+         * `message.sent`, but only on some surfaces: see
+         * WebhookPayloadMessageSent.metadata.quotedMessageId.
          *
          */
         quotedMessageId?: string;
@@ -9134,13 +9156,27 @@ type WebhookPayloadMessageSent = {
      */
     metadata?: {
         /**
-         * platformMessageId of the message this send is a quote-reply to.
-         * Set when the reply was sent through Zernio with `replyTo` on the
-         * inbox send API (WhatsApp and Telegram), and when the operator
-         * replied from the native WhatsApp Business, Instagram or Messenger
-         * app. WhatsApp API sends carry it on the event fired from the
-         * delivery status, so it arrives on the same `message.sent` as any
-         * other WhatsApp send.
+         * `platformMessageId` of the message this send is a quote-reply to.
+         *
+         * Present when the reply was sent through Zernio with `replyTo` on
+         * the inbox send API (WhatsApp and Telegram). A WhatsApp API send
+         * fires its `message.sent` off the delivery status, and the quote
+         * reference is forwarded from the stored send there, so it arrives
+         * on the same `message.sent` as any other WhatsApp send.
+         *
+         * Not delivered on Instagram echoes. Zernio forwards
+         * `reply_to.mid` whenever Meta puts it on an echo, but on
+         * Instagram Meta does not send it, so a reply the operator quoted
+         * in the Instagram app arrives with no `quotedMessageId`.
+         * Facebook Messenger rides a separate subscription
+         * (`message_echoes`) and has not been measured, so treat it as
+         * unverified rather than supported.
+         *
+         * Absent on WhatsApp Coexistence echoes. Meta omits the quote
+         * context from `smb_message_echoes`, so a reply the operator sent
+         * from the WhatsApp Business app arrives with no `quotedMessageId`
+         * even though WhatsApp shows it as a quote-reply. Do not read the
+         * absence of this field as "not a reply".
          *
          */
         quotedMessageId?: string;
@@ -19425,6 +19461,16 @@ type GetInboxConversationMessagesResponse = ({
      */
     sortOrderApplied?: 'asc' | 'desc';
     messages?: Array<{
+        /**
+         * The platform's own message id: the `wamid` on WhatsApp, the
+         * `mid` on Instagram and Facebook Messenger. This is what
+         * `metadata.quotedMessageId` points at, the value to pass as
+         * `replyTo` on the platforms that support quote-replies, and the
+         * `{messageId}` segment of the attachment-resolve URL. Webhooks
+         * deliver the same value as `message.platformMessageId`; this
+         * response has no field by that name.
+         *
+         */
         id?: string;
         conversationId?: string;
         accountId?: string;
@@ -19520,7 +19566,8 @@ type GetInboxConversationMessagesResponse = ({
         }>;
         /**
          * Platform-specific extras. Free-form, but commonly includes:
-         * `quotedMessageId` (platformMessageId this message replies to),
+         * `quotedMessageId` (the `id` of the message this one replies to,
+         * delivered as `message.platformMessageId` on webhooks),
          * `waInteractive` (a compact descriptor of WhatsApp interactive
          * content sent: buttons / list / cta_url / flow / location_request),
          * and for inbound interactive taps `interactiveType` / `interactiveId`.
@@ -20075,7 +20122,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 (both 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 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. 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).
          */
         replyTo?: string;
         /**
@@ -29130,6 +29177,10 @@ type ListAdsData = {
          * Platform ad account ID (e.g. act_123 for Meta). Mirrors the same filter on /v1/ads/campaigns and /v1/ads/tree.
          */
         adAccountId?: string;
+        /**
+         * Platform ad set ID (filter ads within an ad set, the /{adset_id}/ads read of an adset-centric dashboard).
+         */
+        adSetId?: string;
         /**
          * Platform campaign ID (filter ads within a campaign)
          */
@@ -30281,29 +30332,51 @@ type UpdateAdData = {
             advantage_audience?: 0 | 1;
         };
         /**
-         * Replace the ad's creative. Meta, TikTok, and LinkedIn.
-         *
-         * - **Meta**: requires `headline`, `body`, `callToAction`, `linkUrl`, `imageUrl`. The
-         * ad's existing creative is replaced via a new `/act_X/adcreatives` upload + ad
-         * update. The old creative is retained on the ad account for historical reporting.
+         * Replace or patch the ad's creative. Meta, TikTok, and LinkedIn.
+         *
+         * - **Meta**: patch-style. Pass any subset — fields you omit are preserved from the
+         * live creative, including media (`image_hash`/`video_id` are reused, no re-upload)
+         * and `url_tags`. Sending the full set (`headline`, `body`, `callToAction`,
+         * `linkUrl`, `imageUrl`) rebuilds the creative from scratch instead. Partial
+         * patching reads the live `object_story_spec`, which Meta strips on SHARE /
+         * page-post / dark / asset_feed creatives — those return 422 asking for the full
+         * set. A `videoUrl`/`videoId` on an image creative is a type change and also
+         * needs the full set. `existingCreativeId` repoints the ad at a creative from
+         * GET /v1/ads/creatives and ignores every other field. Meta creatives are
+         * immutable, so any change creates a new creative and repoints the ad; the old
+         * creative is retained on the ad account for historical reporting.
          * - **TikTok**: patch-style. Pass any subset; `headline` is ignored (TikTok creatives
          * have no headline slot). `body` becomes the in-feed `ad_text`; `linkUrl` becomes
-         * `landing_page_url`; `videoUrl` triggers a fresh upload.
+         * `landing_page_url`; `videoUrl` triggers a fresh upload. `description`, `videoId`
+         * and `existingCreativeId` are Meta-only and return 400.
          * - **LinkedIn**: uploads new media (image via `imageUrl` or video via `videoUrl`),
          * creates a new inline media creative on the same campaign, and pauses the old
          * creative (best-effort). The old creative is retained for historical reporting.
+         * `videoId` and `existingCreativeId` are Meta-only and return 400.
          *
          */
         creative?: {
             /**
-             * Meta only
+             * Meta and LinkedIn (TikTok has no headline slot)
              */
             headline?: string;
             body?: string;
+            /**
+             * Link description slot (Meta `link_data.description` / `video_data.link_description`, LinkedIn creative description).
+             */
+            description?: string;
             callToAction?: string;
             linkUrl?: string;
             imageUrl?: string;
             videoUrl?: string;
+            /**
+             * Meta only. Reuse an already-uploaded ad video (from POST /v1/ads/videos or GET /v1/ads/videos) instead of re-uploading via videoUrl.
+             */
+            videoId?: string;
+            /**
+             * Meta only. Repoint the ad at an existing library creative (from GET /v1/ads/creatives); all other creative fields are ignored.
+             */
+            existingCreativeId?: string;
         };
         /**
          * Rename the ad. Now propagated to Meta (POST /{ad-id}); non-Meta platforms return 501.
@@ -32606,6 +32679,27 @@ type CreateStandaloneAdData = {
             id: string;
             name?: string;
         }>;
+        /**
+         * Meta only. Job title entities from /v1/ads/targeting/search?dimension=workPosition. Each must include id. Rejected on other platforms (use LinkedIn's `jobTitles` there).
+         */
+        workPositions?: Array<{
+            id: string;
+            name?: string;
+        }>;
+        /**
+         * Meta only. Employer entities from /v1/ads/targeting/search?dimension=workEmployer. Each must include id.
+         */
+        workEmployers?: Array<{
+            id: string;
+            name?: string;
+        }>;
+        /**
+         * Meta only. Work-industry entities from /v1/ads/targeting/search?dimension=workIndustry. Each must include id. Rejected on other platforms (use LinkedIn's `industries` there).
+         */
+        workIndustries?: Array<{
+            id: string;
+            name?: string;
+        }>;
         /**
          * Normalized household-income tier. Meta and TikTok express all four; Google maps only
          * `top_10`; rejected on LinkedIn, X, and Pinterest. On Meta, income targeting is incompatible
@@ -33923,9 +34017,9 @@ type SearchAdTargetingData = {
          */
         countryCode?: string;
         /**
-         * What to search. `geo` resolves locations (scope further with `geoType`), `interest`/`behavior` resolve audience entities, `income` resolves income-tier options. Defaults to `interest` for backward compatibility with the deprecated /v1/ads/interests alias.
+         * What to search. `geo` resolves locations (scope further with `geoType`), `interest`/`behavior` resolve audience entities, `income` resolves income-tier options, `workPosition`/`workEmployer`/`workIndustry` resolve Meta work demographics. Defaults to `interest` for backward compatibility with the deprecated /v1/ads/interests alias.
          */
-        dimension?: 'geo' | 'interest' | 'behavior' | 'income';
+        dimension?: 'geo' | 'interest' | 'behavior' | 'income' | 'workPosition' | 'workEmployer' | 'workIndustry';
         /**
          * Only used when `dimension=geo`. The kind of location to resolve. `all` searches every type in one relevance-ranked call. Defaults to `city`.
          */

package/dist/index.d.ts

@@ -6702,6 +6702,27 @@ type TargetingSpec = {
         id: string;
         name?: string;
     }>;
+    /**
+     * Meta only. Job title entities from /v1/ads/targeting/search?dimension=workPosition. Not interchangeable with the LinkedIn `jobTitles` URN fragments.
+     */
+    workPositions?: Array<{
+        id: string;
+        name?: string;
+    }>;
+    /**
+     * Meta only. Employer entities from /v1/ads/targeting/search?dimension=workEmployer.
+     */
+    workEmployers?: Array<{
+        id: string;
+        name?: string;
+    }>;
+    /**
+     * Meta only. Work-industry entities from /v1/ads/targeting/search?dimension=workIndustry. Not interchangeable with the LinkedIn `industries` URN fragments.
+     */
+    workIndustries?: Array<{
+        id: string;
+        name?: string;
+    }>;
     /**
      * LinkedIn B2B only. Industry URN id fragments.
      */
@@ -6719,11 +6740,11 @@ type TargetingSpec = {
      */
     jobFunctions?: Array<(string)>;
     /**
-     * Platform audience IDs to include. Not supported on any platform (no builder maps it): rejected with a 400 on ad create, boost, and reach estimate.
+     * Platform audience IDs to include, as returned by GET /v1/ads/audiences (Meta custom audience ids, TikTok audience ids, Pinterest customer list ids, LinkedIn segment ids (bare, urn:li:adSegment or urn:li:dmpSegment forms accepted), Google user list ids, X custom audience ids). Not supported on OpenAI (400).
      */
     audienceInclude?: Array<(string)>;
     /**
-     * Platform audience IDs to exclude. Not supported on any platform (no builder maps it): rejected with a 400 on ad create, boost, and reach estimate.
+     * Platform audience IDs to exclude; same ID formats as audienceInclude. Not supported on OpenAI (400).
      */
     audienceExclude?: Array<(string)>;
 };
@@ -8585,8 +8606,9 @@ type WebhookPayloadMessage = {
         /**
          * platformMessageId of the message this one is a quote-reply to.
          * WhatsApp (`context.id`), Instagram and Facebook Messenger
-         * (`reply_to.mid`). Outgoing quote-replies carry the same field on
-         * `message.sent`; see WebhookPayloadMessageSent.metadata.
+         * (`reply_to.mid`). On outgoing messages the same field appears on
+         * `message.sent`, but only on some surfaces: see
+         * WebhookPayloadMessageSent.metadata.quotedMessageId.
          *
          */
         quotedMessageId?: string;
@@ -9134,13 +9156,27 @@ type WebhookPayloadMessageSent = {
      */
     metadata?: {
         /**
-         * platformMessageId of the message this send is a quote-reply to.
-         * Set when the reply was sent through Zernio with `replyTo` on the
-         * inbox send API (WhatsApp and Telegram), and when the operator
-         * replied from the native WhatsApp Business, Instagram or Messenger
-         * app. WhatsApp API sends carry it on the event fired from the
-         * delivery status, so it arrives on the same `message.sent` as any
-         * other WhatsApp send.
+         * `platformMessageId` of the message this send is a quote-reply to.
+         *
+         * Present when the reply was sent through Zernio with `replyTo` on
+         * the inbox send API (WhatsApp and Telegram). A WhatsApp API send
+         * fires its `message.sent` off the delivery status, and the quote
+         * reference is forwarded from the stored send there, so it arrives
+         * on the same `message.sent` as any other WhatsApp send.
+         *
+         * Not delivered on Instagram echoes. Zernio forwards
+         * `reply_to.mid` whenever Meta puts it on an echo, but on
+         * Instagram Meta does not send it, so a reply the operator quoted
+         * in the Instagram app arrives with no `quotedMessageId`.
+         * Facebook Messenger rides a separate subscription
+         * (`message_echoes`) and has not been measured, so treat it as
+         * unverified rather than supported.
+         *
+         * Absent on WhatsApp Coexistence echoes. Meta omits the quote
+         * context from `smb_message_echoes`, so a reply the operator sent
+         * from the WhatsApp Business app arrives with no `quotedMessageId`
+         * even though WhatsApp shows it as a quote-reply. Do not read the
+         * absence of this field as "not a reply".
          *
          */
         quotedMessageId?: string;
@@ -19425,6 +19461,16 @@ type GetInboxConversationMessagesResponse = ({
      */
     sortOrderApplied?: 'asc' | 'desc';
     messages?: Array<{
+        /**
+         * The platform's own message id: the `wamid` on WhatsApp, the
+         * `mid` on Instagram and Facebook Messenger. This is what
+         * `metadata.quotedMessageId` points at, the value to pass as
+         * `replyTo` on the platforms that support quote-replies, and the
+         * `{messageId}` segment of the attachment-resolve URL. Webhooks
+         * deliver the same value as `message.platformMessageId`; this
+         * response has no field by that name.
+         *
+         */
         id?: string;
         conversationId?: string;
         accountId?: string;
@@ -19520,7 +19566,8 @@ type GetInboxConversationMessagesResponse = ({
         }>;
         /**
          * Platform-specific extras. Free-form, but commonly includes:
-         * `quotedMessageId` (platformMessageId this message replies to),
+         * `quotedMessageId` (the `id` of the message this one replies to,
+         * delivered as `message.platformMessageId` on webhooks),
          * `waInteractive` (a compact descriptor of WhatsApp interactive
          * content sent: buttons / list / cta_url / flow / location_request),
          * and for inbound interactive taps `interactiveType` / `interactiveId`.
@@ -20075,7 +20122,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 (both 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 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. 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).
          */
         replyTo?: string;
         /**
@@ -29130,6 +29177,10 @@ type ListAdsData = {
          * Platform ad account ID (e.g. act_123 for Meta). Mirrors the same filter on /v1/ads/campaigns and /v1/ads/tree.
          */
         adAccountId?: string;
+        /**
+         * Platform ad set ID (filter ads within an ad set, the /{adset_id}/ads read of an adset-centric dashboard).
+         */
+        adSetId?: string;
         /**
          * Platform campaign ID (filter ads within a campaign)
          */
@@ -30281,29 +30332,51 @@ type UpdateAdData = {
             advantage_audience?: 0 | 1;
         };
         /**
-         * Replace the ad's creative. Meta, TikTok, and LinkedIn.
-         *
-         * - **Meta**: requires `headline`, `body`, `callToAction`, `linkUrl`, `imageUrl`. The
-         * ad's existing creative is replaced via a new `/act_X/adcreatives` upload + ad
-         * update. The old creative is retained on the ad account for historical reporting.
+         * Replace or patch the ad's creative. Meta, TikTok, and LinkedIn.
+         *
+         * - **Meta**: patch-style. Pass any subset — fields you omit are preserved from the
+         * live creative, including media (`image_hash`/`video_id` are reused, no re-upload)
+         * and `url_tags`. Sending the full set (`headline`, `body`, `callToAction`,
+         * `linkUrl`, `imageUrl`) rebuilds the creative from scratch instead. Partial
+         * patching reads the live `object_story_spec`, which Meta strips on SHARE /
+         * page-post / dark / asset_feed creatives — those return 422 asking for the full
+         * set. A `videoUrl`/`videoId` on an image creative is a type change and also
+         * needs the full set. `existingCreativeId` repoints the ad at a creative from
+         * GET /v1/ads/creatives and ignores every other field. Meta creatives are
+         * immutable, so any change creates a new creative and repoints the ad; the old
+         * creative is retained on the ad account for historical reporting.
          * - **TikTok**: patch-style. Pass any subset; `headline` is ignored (TikTok creatives
          * have no headline slot). `body` becomes the in-feed `ad_text`; `linkUrl` becomes
-         * `landing_page_url`; `videoUrl` triggers a fresh upload.
+         * `landing_page_url`; `videoUrl` triggers a fresh upload. `description`, `videoId`
+         * and `existingCreativeId` are Meta-only and return 400.
          * - **LinkedIn**: uploads new media (image via `imageUrl` or video via `videoUrl`),
          * creates a new inline media creative on the same campaign, and pauses the old
          * creative (best-effort). The old creative is retained for historical reporting.
+         * `videoId` and `existingCreativeId` are Meta-only and return 400.
          *
          */
         creative?: {
             /**
-             * Meta only
+             * Meta and LinkedIn (TikTok has no headline slot)
              */
             headline?: string;
             body?: string;
+            /**
+             * Link description slot (Meta `link_data.description` / `video_data.link_description`, LinkedIn creative description).
+             */
+            description?: string;
             callToAction?: string;
             linkUrl?: string;
             imageUrl?: string;
             videoUrl?: string;
+            /**
+             * Meta only. Reuse an already-uploaded ad video (from POST /v1/ads/videos or GET /v1/ads/videos) instead of re-uploading via videoUrl.
+             */
+            videoId?: string;
+            /**
+             * Meta only. Repoint the ad at an existing library creative (from GET /v1/ads/creatives); all other creative fields are ignored.
+             */
+            existingCreativeId?: string;
         };
         /**
          * Rename the ad. Now propagated to Meta (POST /{ad-id}); non-Meta platforms return 501.
@@ -32606,6 +32679,27 @@ type CreateStandaloneAdData = {
             id: string;
             name?: string;
         }>;
+        /**
+         * Meta only. Job title entities from /v1/ads/targeting/search?dimension=workPosition. Each must include id. Rejected on other platforms (use LinkedIn's `jobTitles` there).
+         */
+        workPositions?: Array<{
+            id: string;
+            name?: string;
+        }>;
+        /**
+         * Meta only. Employer entities from /v1/ads/targeting/search?dimension=workEmployer. Each must include id.
+         */
+        workEmployers?: Array<{
+            id: string;
+            name?: string;
+        }>;
+        /**
+         * Meta only. Work-industry entities from /v1/ads/targeting/search?dimension=workIndustry. Each must include id. Rejected on other platforms (use LinkedIn's `industries` there).
+         */
+        workIndustries?: Array<{
+            id: string;
+            name?: string;
+        }>;
         /**
          * Normalized household-income tier. Meta and TikTok express all four; Google maps only
          * `top_10`; rejected on LinkedIn, X, and Pinterest. On Meta, income targeting is incompatible
@@ -33923,9 +34017,9 @@ type SearchAdTargetingData = {
          */
         countryCode?: string;
         /**
-         * What to search. `geo` resolves locations (scope further with `geoType`), `interest`/`behavior` resolve audience entities, `income` resolves income-tier options. Defaults to `interest` for backward compatibility with the deprecated /v1/ads/interests alias.
+         * What to search. `geo` resolves locations (scope further with `geoType`), `interest`/`behavior` resolve audience entities, `income` resolves income-tier options, `workPosition`/`workEmployer`/`workIndustry` resolve Meta work demographics. Defaults to `interest` for backward compatibility with the deprecated /v1/ads/interests alias.
          */
-        dimension?: 'geo' | 'interest' | 'behavior' | 'income';
+        dimension?: 'geo' | 'interest' | 'behavior' | 'income' | 'workPosition' | 'workEmployer' | 'workIndustry';
         /**
          * Only used when `dimension=geo`. The kind of location to resolve. `all` searches every type in one relevance-ranked call. Defaults to `city`.
          */

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -9072,8 +9072,13 @@ export const searchAdInterests = <ThrowOnError extends boolean = false>(options:
  * `POST /v1/ads/targeting/reach-estimate`, and `saved_targeting` audiences.
  *
  * The `dimension` param selects what is searched, `geo` (locations, further scoped
- * by `geoType`), `interest`, `behavior`, or `income`. Availability of each dimension
- * varies by platform (e.g. behaviours are Meta/TikTok only). Results are normalized
+ * by `geoType`), `interest`, `behavior`, `income`, or the Meta-only work
+ * demographics `workPosition`, `workEmployer` and `workIndustry` (their ids feed
+ * `TargetingSpec.workPositions`/`workEmployers`/`workIndustries`). Availability of
+ * each dimension varies by platform (e.g. behaviours are Meta/TikTok only).
+ * Work industries are a fixed ~30-entry Meta catalog with no server-side query,
+ * so `workIndustry` matching, ranking and `limit` happen in Zernio.
+ * Results are normalized
  * across platforms into a single shape, so the same client code consumes Meta,
  * TikTok, LinkedIn, X, Pinterest, and Google results.
  *

package/src/generated/types.gen.ts

@@ -5566,6 +5566,27 @@ export type TargetingSpec = {
         id: string;
         name?: string;
     }>;
+    /**
+     * Meta only. Job title entities from /v1/ads/targeting/search?dimension=workPosition. Not interchangeable with the LinkedIn `jobTitles` URN fragments.
+     */
+    workPositions?: Array<{
+        id: string;
+        name?: string;
+    }>;
+    /**
+     * Meta only. Employer entities from /v1/ads/targeting/search?dimension=workEmployer.
+     */
+    workEmployers?: Array<{
+        id: string;
+        name?: string;
+    }>;
+    /**
+     * Meta only. Work-industry entities from /v1/ads/targeting/search?dimension=workIndustry. Not interchangeable with the LinkedIn `industries` URN fragments.
+     */
+    workIndustries?: Array<{
+        id: string;
+        name?: string;
+    }>;
     /**
      * LinkedIn B2B only. Industry URN id fragments.
      */
@@ -5583,11 +5604,11 @@ export type TargetingSpec = {
      */
     jobFunctions?: Array<(string)>;
     /**
-     * Platform audience IDs to include. Not supported on any platform (no builder maps it): rejected with a 400 on ad create, boost, and reach estimate.
+     * Platform audience IDs to include, as returned by GET /v1/ads/audiences (Meta custom audience ids, TikTok audience ids, Pinterest customer list ids, LinkedIn segment ids (bare, urn:li:adSegment or urn:li:dmpSegment forms accepted), Google user list ids, X custom audience ids). Not supported on OpenAI (400).
      */
     audienceInclude?: Array<(string)>;
     /**
-     * Platform audience IDs to exclude. Not supported on any platform (no builder maps it): rejected with a 400 on ad create, boost, and reach estimate.
+     * Platform audience IDs to exclude; same ID formats as audienceInclude. Not supported on OpenAI (400).
      */
     audienceExclude?: Array<(string)>;
 };
@@ -7524,8 +7545,9 @@ export type WebhookPayloadMessage = {
         /**
          * platformMessageId of the message this one is a quote-reply to.
          * WhatsApp (`context.id`), Instagram and Facebook Messenger
-         * (`reply_to.mid`). Outgoing quote-replies carry the same field on
-         * `message.sent`; see WebhookPayloadMessageSent.metadata.
+         * (`reply_to.mid`). On outgoing messages the same field appears on
+         * `message.sent`, but only on some surfaces: see
+         * WebhookPayloadMessageSent.metadata.quotedMessageId.
          *
          */
         quotedMessageId?: string;
@@ -8084,13 +8106,27 @@ export type WebhookPayloadMessageSent = {
      */
     metadata?: {
         /**
-         * platformMessageId of the message this send is a quote-reply to.
-         * Set when the reply was sent through Zernio with `replyTo` on the
-         * inbox send API (WhatsApp and Telegram), and when the operator
-         * replied from the native WhatsApp Business, Instagram or Messenger
-         * app. WhatsApp API sends carry it on the event fired from the
-         * delivery status, so it arrives on the same `message.sent` as any
-         * other WhatsApp send.
+         * `platformMessageId` of the message this send is a quote-reply to.
+         *
+         * Present when the reply was sent through Zernio with `replyTo` on
+         * the inbox send API (WhatsApp and Telegram). A WhatsApp API send
+         * fires its `message.sent` off the delivery status, and the quote
+         * reference is forwarded from the stored send there, so it arrives
+         * on the same `message.sent` as any other WhatsApp send.
+         *
+         * Not delivered on Instagram echoes. Zernio forwards
+         * `reply_to.mid` whenever Meta puts it on an echo, but on
+         * Instagram Meta does not send it, so a reply the operator quoted
+         * in the Instagram app arrives with no `quotedMessageId`.
+         * Facebook Messenger rides a separate subscription
+         * (`message_echoes`) and has not been measured, so treat it as
+         * unverified rather than supported.
+         *
+         * Absent on WhatsApp Coexistence echoes. Meta omits the quote
+         * context from `smb_message_echoes`, so a reply the operator sent
+         * from the WhatsApp Business app arrives with no `quotedMessageId`
+         * even though WhatsApp shows it as a quote-reply. Do not read the
+         * absence of this field as "not a reply".
          *
          */
         quotedMessageId?: string;
@@ -19076,6 +19112,16 @@ export type GetInboxConversationMessagesResponse = ({
      */
     sortOrderApplied?: 'asc' | 'desc';
     messages?: Array<{
+        /**
+         * The platform's own message id: the `wamid` on WhatsApp, the
+         * `mid` on Instagram and Facebook Messenger. This is what
+         * `metadata.quotedMessageId` points at, the value to pass as
+         * `replyTo` on the platforms that support quote-replies, and the
+         * `{messageId}` segment of the attachment-resolve URL. Webhooks
+         * deliver the same value as `message.platformMessageId`; this
+         * response has no field by that name.
+         *
+         */
         id?: string;
         conversationId?: string;
         accountId?: string;
@@ -19171,7 +19217,8 @@ export type GetInboxConversationMessagesResponse = ({
         }>;
         /**
          * Platform-specific extras. Free-form, but commonly includes:
-         * `quotedMessageId` (platformMessageId this message replies to),
+         * `quotedMessageId` (the `id` of the message this one replies to,
+         * delivered as `message.platformMessageId` on webhooks),
          * `waInteractive` (a compact descriptor of WhatsApp interactive
          * content sent: buttons / list / cta_url / flow / location_request),
          * and for inbound interactive taps `interactiveType` / `interactiveId`.
@@ -19728,7 +19775,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 (both 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 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. 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).
          */
         replyTo?: string;
         /**
@@ -29534,6 +29581,10 @@ export type ListAdsData = {
          * Platform ad account ID (e.g. act_123 for Meta). Mirrors the same filter on /v1/ads/campaigns and /v1/ads/tree.
          */
         adAccountId?: string;
+        /**
+         * Platform ad set ID (filter ads within an ad set, the /{adset_id}/ads read of an adset-centric dashboard).
+         */
+        adSetId?: string;
         /**
          * Platform campaign ID (filter ads within a campaign)
          */
@@ -30748,29 +30799,51 @@ export type UpdateAdData = {
             advantage_audience?: 0 | 1;
         };
         /**
-         * Replace the ad's creative. Meta, TikTok, and LinkedIn.
-         *
-         * - **Meta**: requires `headline`, `body`, `callToAction`, `linkUrl`, `imageUrl`. The
-         * ad's existing creative is replaced via a new `/act_X/adcreatives` upload + ad
-         * update. The old creative is retained on the ad account for historical reporting.
+         * Replace or patch the ad's creative. Meta, TikTok, and LinkedIn.
+         *
+         * - **Meta**: patch-style. Pass any subset — fields you omit are preserved from the
+         * live creative, including media (`image_hash`/`video_id` are reused, no re-upload)
+         * and `url_tags`. Sending the full set (`headline`, `body`, `callToAction`,
+         * `linkUrl`, `imageUrl`) rebuilds the creative from scratch instead. Partial
+         * patching reads the live `object_story_spec`, which Meta strips on SHARE /
+         * page-post / dark / asset_feed creatives — those return 422 asking for the full
+         * set. A `videoUrl`/`videoId` on an image creative is a type change and also
+         * needs the full set. `existingCreativeId` repoints the ad at a creative from
+         * GET /v1/ads/creatives and ignores every other field. Meta creatives are
+         * immutable, so any change creates a new creative and repoints the ad; the old
+         * creative is retained on the ad account for historical reporting.
          * - **TikTok**: patch-style. Pass any subset; `headline` is ignored (TikTok creatives
          * have no headline slot). `body` becomes the in-feed `ad_text`; `linkUrl` becomes
-         * `landing_page_url`; `videoUrl` triggers a fresh upload.
+         * `landing_page_url`; `videoUrl` triggers a fresh upload. `description`, `videoId`
+         * and `existingCreativeId` are Meta-only and return 400.
          * - **LinkedIn**: uploads new media (image via `imageUrl` or video via `videoUrl`),
          * creates a new inline media creative on the same campaign, and pauses the old
          * creative (best-effort). The old creative is retained for historical reporting.
+         * `videoId` and `existingCreativeId` are Meta-only and return 400.
          *
          */
         creative?: {
             /**
-             * Meta only
+             * Meta and LinkedIn (TikTok has no headline slot)
              */
             headline?: string;
             body?: string;
+            /**
+             * Link description slot (Meta `link_data.description` / `video_data.link_description`, LinkedIn creative description).
+             */
+            description?: string;
             callToAction?: string;
             linkUrl?: string;
             imageUrl?: string;
             videoUrl?: string;
+            /**
+             * Meta only. Reuse an already-uploaded ad video (from POST /v1/ads/videos or GET /v1/ads/videos) instead of re-uploading via videoUrl.
+             */
+            videoId?: string;
+            /**
+             * Meta only. Repoint the ad at an existing library creative (from GET /v1/ads/creatives); all other creative fields are ignored.
+             */
+            existingCreativeId?: string;
         };
         /**
          * Rename the ad. Now propagated to Meta (POST /{ad-id}); non-Meta platforms return 501.
@@ -33205,6 +33278,27 @@ export type CreateStandaloneAdData = {
             id: string;
             name?: string;
         }>;
+        /**
+         * Meta only. Job title entities from /v1/ads/targeting/search?dimension=workPosition. Each must include id. Rejected on other platforms (use LinkedIn's `jobTitles` there).
+         */
+        workPositions?: Array<{
+            id: string;
+            name?: string;
+        }>;
+        /**
+         * Meta only. Employer entities from /v1/ads/targeting/search?dimension=workEmployer. Each must include id.
+         */
+        workEmployers?: Array<{
+            id: string;
+            name?: string;
+        }>;
+        /**
+         * Meta only. Work-industry entities from /v1/ads/targeting/search?dimension=workIndustry. Each must include id. Rejected on other platforms (use LinkedIn's `industries` there).
+         */
+        workIndustries?: Array<{
+            id: string;
+            name?: string;
+        }>;
         /**
          * Normalized household-income tier. Meta and TikTok express all four; Google maps only
          * `top_10`; rejected on LinkedIn, X, and Pinterest. On Meta, income targeting is incompatible
@@ -34564,9 +34658,9 @@ export type SearchAdTargetingData = {
          */
         countryCode?: string;
         /**
-         * What to search. `geo` resolves locations (scope further with `geoType`), `interest`/`behavior` resolve audience entities, `income` resolves income-tier options. Defaults to `interest` for backward compatibility with the deprecated /v1/ads/interests alias.
+         * What to search. `geo` resolves locations (scope further with `geoType`), `interest`/`behavior` resolve audience entities, `income` resolves income-tier options, `workPosition`/`workEmployer`/`workIndustry` resolve Meta work demographics. Defaults to `interest` for backward compatibility with the deprecated /v1/ads/interests alias.
          */
-        dimension?: 'geo' | 'interest' | 'behavior' | 'income';
+        dimension?: 'geo' | 'interest' | 'behavior' | 'income' | 'workPosition' | 'workEmployer' | 'workIndustry';
         /**
          * Only used when `dimension=geo`. The kind of location to resolve. `all` searches every type in one relevance-ranked call. Defaults to `city`.
          */