@getlatedev/node 0.2.1354 → 0.2.1356

package/dist/index.d.mts

@@ -20522,7 +20522,7 @@ type WorkflowNode = {
      * **Variables** available from the start of every run (absent values are `''`): `lastMessage`, `inboundText`, `triggerText`, `conversationId`, `contact.name`, `contact.phone`, `contact.handle`, `contact.tags` (array), `contact.fields` (the contact's custom fields object), `contact.lastInteractionAt` (ISO date), `contact.lastInteractionHoursAgo` (number), `contact.isFollower` (Instagram, from the stored profile: true, false or `''` when unknown), `referral.ref`, `referral.source`, `referral.type`, `referral.adId`, `referral.adTitle` (the ad title or headline Meta sent), `referral.adName` (the synced ad's name, else `referral.adTitle`), `referral.campaignName` (the synced ad's campaign), `postback.payload`, `postback.title`, `quickReply.payload`, `quickReply.title`, `story.id`, `story.url`, `comment.id`, `comment.text`, `comment.platformPostId`, `reaction.emoji`, `reaction.action` (added|removed). `api_call` runs also get the request's `variables`, merged over these. `lead_received` runs also get `lead.id`, `lead.leadgenId`, `lead.formId`, `lead.formName`, `lead.adId`, `lead.adsetId`, `lead.campaignId` and every form answer by its key (`lead.full_name`, `lead.email`, `lead.phone_number`). Template `variableMapping` entries with `field: custom` interpolate `{{...}}` in `customValue`. An array or object interpolated into text renders as JSON.
      *
      * **send_message**: `{ messageType: text|template|media|interactive|cards, text, template, media:{mediaType:image|video|audio|document, url,caption}, interactive, buttons, quickReplies, messageTag }`. `template` is `{name,language,variableMapping}` for `messageType: template` and `{ type: generic, elements:[{ title, subtitle, imageUrl, buttons }] }` (1 to 10 cards) for `messageType: cards`. `template` and `interactive` are WhatsApp-only. `interactive.type` is inferred from the payload shape when omitted; payloads with neither `type` nor an inferable shape are rejected.
-     * Facebook and Instagram only (rejected with a 400 on other platforms; WhatsApp keeps `interactive`): `cards`, plus `buttons` on `text` (cards carry their own buttons) and `quickReplies` / `messageTag` on `text`, `media` and `cards`. `media` takes no `buttons` (a 400 at save). `buttons:[{ type: url|postback|phone, title, url, payload, phone, workflowId }]` (1 to 3, text only and the text then 640 characters at most, sent as Meta's button_template, `phone` Facebook-only, not inside cards), `quickReplies:[{ title, payload, imageUrl, workflowId }]` (1 to 13, not combined with `buttons`) and `messageTag: HUMAN_AGENT|CONFIRMED_EVENT_UPDATE|POST_PURCHASE_UPDATE|ACCOUNT_UPDATE` (Instagram accepts only `HUMAN_AGENT`). Titles are capped at 20 characters (80 for card titles and subtitles). A postback button or quick reply with no `payload` gets `zernio:workflow:<this workflow id>`, so a tap answers this workflow's pending `wait_for_reply` or restarts it; with `workflowId` (a 24-hex workflow id, not combined with `payload`) the tap starts that workflow instead.
+     * Facebook and Instagram only (rejected with a 400 on other platforms; WhatsApp keeps `interactive`): `cards`, plus `buttons` on `text` (cards carry their own buttons) and `quickReplies` / `messageTag` on `text`, `media` and `cards`. `media` takes no `buttons` (a 400 at save). `buttons:[{ type: url|postback|phone, title, url, payload, phone, workflowId }]` (1 to 3, text only and the text then 640 characters at most, sent as Meta's button_template, `phone` Facebook-only, not inside cards), `quickReplies:[{ title, payload, imageUrl, workflowId }]` (1 to 13, not combined with `buttons`). `messageTag` is not available: a workflow only sends within the 24h window, and `HUMAN_AGENT` is rejected with a 400 because it is only for replies typed by a person. Titles are capped at 20 characters (80 for card titles and subtitles). A postback button or quick reply with no `payload` gets `zernio:workflow:<this workflow id>`, so a tap answers this workflow's pending `wait_for_reply` or restarts it; with `workflowId` (a 24-hex workflow id, not combined with `payload`) the tap starts that workflow instead.
      *
      * **wait_for_reply**: `{ timeoutMinutes:int (max 43200), saveAs:string }`. Resume via the `'reply'` edge on inbound, or `'timeout'` edge after `timeoutMinutes` of silence. On Facebook and Instagram a button tap sets `{{postback.payload}}` / `{{postback.title}}` and a quick reply tap sets `{{quickReply.payload}}` / `{{quickReply.title}}`; each reply clears the previous tap.
      *
@@ -33961,7 +33961,7 @@ type SendInboxMessageData = {
          */
         messagingType?: 'RESPONSE' | 'UPDATE' | 'MESSAGE_TAG';
         /**
-         * Facebook message tag for messaging outside 24h window. Requires messagingType MESSAGE_TAG. Instagram only supports HUMAN_AGENT.
+         * Facebook and Instagram. To reply after the 24h window, send HUMAN_AGENT with messagingType MESSAGE_TAG: it works up to 7 days after the person's last message, for replies typed by a person only (Meta does not allow it on automated messages). Meta retired the other tags, so they fail.
          */
         messageTag?: 'CONFIRMED_EVENT_UPDATE' | 'POST_PURCHASE_UPDATE' | 'ACCOUNT_UPDATE' | 'HUMAN_AGENT';
         /**
@@ -43134,7 +43134,7 @@ type CreateBroadcastData = {
                 filename?: string;
             }>;
             /**
-             * Instagram and Facebook only. Meta message tag sent with every recipient message (messaging_type MESSAGE_TAG) so the broadcast can reach people outside the 24h window. Instagram accepts HUMAN_AGENT only. Rejected with a 400 on any other platform.
+             * Not usable: a broadcast only reaches people within the 24h window. HUMAN_AGENT is rejected with a 400 because it is only for replies typed by a person, and Meta retired the other tags.
              */
             messageTag?: 'CONFIRMED_EVENT_UPDATE' | 'POST_PURCHASE_UPDATE' | 'ACCOUNT_UPDATE' | 'HUMAN_AGENT';
         };
@@ -46912,6 +46912,48 @@ type UpdateAdSetData = {
          *
          */
         bidStrategy?: (BidStrategy);
+        /**
+         * Meta only (400 elsewhere, before anything in the request is written). Writes the ad
+         * set's `dsa_beneficiary`, the legal entity that benefits from its ads, same field and
+         * limits as `dsaBeneficiary` on POST /v1/ads/create. Only the fields you send are
+         * written. It is the EU DSA field; for the regional regimes (Brazil, Malaysia,
+         * Thailand, Australia, Singapore, Taiwan, India) use `regionalRegulatedCategories` and
+         * `regionalRegulationIdentities` instead. Read it back with
+         * GET /v1/ads/ad-sets/{adSetId}?accountId={accountId}&fields=dsa_beneficiary,dsa_payor.
+         *
+         */
+        dsaBeneficiary?: string;
+        /**
+         * Meta only (400 elsewhere, before anything in the request is written). Writes the ad
+         * set's `dsa_payor`, the legal entity that pays for its ads, same field and limits as
+         * `dsaPayor` on POST /v1/ads/create. Can differ from `dsaBeneficiary`.
+         *
+         */
+        dsaPayor?: string;
+        /**
+         * Meta only (400 elsewhere, before anything in the request is written). Writes the ad
+         * set's `regional_regulated_categories`, same values as on POST /v1/ads/create
+         * (AUSTRALIA_FINSERV, AUSTRALIA_UNIVERSAL, BRAZIL_REGULATION, INDIA_FINSERV,
+         * MALAYSIA_UNIVERSAL, SINGAPORE_UNIVERSAL, TAIWAN_FINSERV, TAIWAN_UNIVERSAL,
+         * THAILAND_UNIVERSAL). Send it with `regionalRegulationIdentities`. An empty array is a 400.
+         *
+         */
+        regionalRegulatedCategories?: Array<(string)>;
+        /**
+         * Meta only (400 elsewhere, before anything in the request is written). Writes the ad
+         * set's `regional_regulation_identities`: the Verified identity IDs of the beneficiary
+         * and payer for each declared category, same keys and validation as on
+         * POST /v1/ads/create (for example `universal_beneficiary` / `universal_payer` for
+         * BRAZIL_REGULATION, MALAYSIA_UNIVERSAL and THAILAND_UNIVERSAL). Send each ID as a
+         * string of digits; an empty object is a 400. When Meta refuses the ad set for a missing
+         * verified advertiser, the 400 `platform_api_error` names the keys the declared categories
+         * expect in `details.expectedIdentityKeys`, as on create. Read both back with
+         * GET /v1/ads/ad-sets/{adSetId}?accountId={accountId}&fields=regional_regulated_categories,regional_regulation_identities.
+         *
+         */
+        regionalRegulationIdentities?: {
+            [key: string]: (string | number);
+        };
         /**
          * TikTok only (a 400 elsewhere). TikTok Smart Targeting on the ad group: `audience` is
          * TikTok's `smart_audience_enabled`, `interestsBehaviors` its `smart_interest_behavior_enabled`.

package/dist/index.d.ts

@@ -20522,7 +20522,7 @@ type WorkflowNode = {
      * **Variables** available from the start of every run (absent values are `''`): `lastMessage`, `inboundText`, `triggerText`, `conversationId`, `contact.name`, `contact.phone`, `contact.handle`, `contact.tags` (array), `contact.fields` (the contact's custom fields object), `contact.lastInteractionAt` (ISO date), `contact.lastInteractionHoursAgo` (number), `contact.isFollower` (Instagram, from the stored profile: true, false or `''` when unknown), `referral.ref`, `referral.source`, `referral.type`, `referral.adId`, `referral.adTitle` (the ad title or headline Meta sent), `referral.adName` (the synced ad's name, else `referral.adTitle`), `referral.campaignName` (the synced ad's campaign), `postback.payload`, `postback.title`, `quickReply.payload`, `quickReply.title`, `story.id`, `story.url`, `comment.id`, `comment.text`, `comment.platformPostId`, `reaction.emoji`, `reaction.action` (added|removed). `api_call` runs also get the request's `variables`, merged over these. `lead_received` runs also get `lead.id`, `lead.leadgenId`, `lead.formId`, `lead.formName`, `lead.adId`, `lead.adsetId`, `lead.campaignId` and every form answer by its key (`lead.full_name`, `lead.email`, `lead.phone_number`). Template `variableMapping` entries with `field: custom` interpolate `{{...}}` in `customValue`. An array or object interpolated into text renders as JSON.
      *
      * **send_message**: `{ messageType: text|template|media|interactive|cards, text, template, media:{mediaType:image|video|audio|document, url,caption}, interactive, buttons, quickReplies, messageTag }`. `template` is `{name,language,variableMapping}` for `messageType: template` and `{ type: generic, elements:[{ title, subtitle, imageUrl, buttons }] }` (1 to 10 cards) for `messageType: cards`. `template` and `interactive` are WhatsApp-only. `interactive.type` is inferred from the payload shape when omitted; payloads with neither `type` nor an inferable shape are rejected.
-     * Facebook and Instagram only (rejected with a 400 on other platforms; WhatsApp keeps `interactive`): `cards`, plus `buttons` on `text` (cards carry their own buttons) and `quickReplies` / `messageTag` on `text`, `media` and `cards`. `media` takes no `buttons` (a 400 at save). `buttons:[{ type: url|postback|phone, title, url, payload, phone, workflowId }]` (1 to 3, text only and the text then 640 characters at most, sent as Meta's button_template, `phone` Facebook-only, not inside cards), `quickReplies:[{ title, payload, imageUrl, workflowId }]` (1 to 13, not combined with `buttons`) and `messageTag: HUMAN_AGENT|CONFIRMED_EVENT_UPDATE|POST_PURCHASE_UPDATE|ACCOUNT_UPDATE` (Instagram accepts only `HUMAN_AGENT`). Titles are capped at 20 characters (80 for card titles and subtitles). A postback button or quick reply with no `payload` gets `zernio:workflow:<this workflow id>`, so a tap answers this workflow's pending `wait_for_reply` or restarts it; with `workflowId` (a 24-hex workflow id, not combined with `payload`) the tap starts that workflow instead.
+     * Facebook and Instagram only (rejected with a 400 on other platforms; WhatsApp keeps `interactive`): `cards`, plus `buttons` on `text` (cards carry their own buttons) and `quickReplies` / `messageTag` on `text`, `media` and `cards`. `media` takes no `buttons` (a 400 at save). `buttons:[{ type: url|postback|phone, title, url, payload, phone, workflowId }]` (1 to 3, text only and the text then 640 characters at most, sent as Meta's button_template, `phone` Facebook-only, not inside cards), `quickReplies:[{ title, payload, imageUrl, workflowId }]` (1 to 13, not combined with `buttons`). `messageTag` is not available: a workflow only sends within the 24h window, and `HUMAN_AGENT` is rejected with a 400 because it is only for replies typed by a person. Titles are capped at 20 characters (80 for card titles and subtitles). A postback button or quick reply with no `payload` gets `zernio:workflow:<this workflow id>`, so a tap answers this workflow's pending `wait_for_reply` or restarts it; with `workflowId` (a 24-hex workflow id, not combined with `payload`) the tap starts that workflow instead.
      *
      * **wait_for_reply**: `{ timeoutMinutes:int (max 43200), saveAs:string }`. Resume via the `'reply'` edge on inbound, or `'timeout'` edge after `timeoutMinutes` of silence. On Facebook and Instagram a button tap sets `{{postback.payload}}` / `{{postback.title}}` and a quick reply tap sets `{{quickReply.payload}}` / `{{quickReply.title}}`; each reply clears the previous tap.
      *
@@ -33961,7 +33961,7 @@ type SendInboxMessageData = {
          */
         messagingType?: 'RESPONSE' | 'UPDATE' | 'MESSAGE_TAG';
         /**
-         * Facebook message tag for messaging outside 24h window. Requires messagingType MESSAGE_TAG. Instagram only supports HUMAN_AGENT.
+         * Facebook and Instagram. To reply after the 24h window, send HUMAN_AGENT with messagingType MESSAGE_TAG: it works up to 7 days after the person's last message, for replies typed by a person only (Meta does not allow it on automated messages). Meta retired the other tags, so they fail.
          */
         messageTag?: 'CONFIRMED_EVENT_UPDATE' | 'POST_PURCHASE_UPDATE' | 'ACCOUNT_UPDATE' | 'HUMAN_AGENT';
         /**
@@ -43134,7 +43134,7 @@ type CreateBroadcastData = {
                 filename?: string;
             }>;
             /**
-             * Instagram and Facebook only. Meta message tag sent with every recipient message (messaging_type MESSAGE_TAG) so the broadcast can reach people outside the 24h window. Instagram accepts HUMAN_AGENT only. Rejected with a 400 on any other platform.
+             * Not usable: a broadcast only reaches people within the 24h window. HUMAN_AGENT is rejected with a 400 because it is only for replies typed by a person, and Meta retired the other tags.
              */
             messageTag?: 'CONFIRMED_EVENT_UPDATE' | 'POST_PURCHASE_UPDATE' | 'ACCOUNT_UPDATE' | 'HUMAN_AGENT';
         };
@@ -46912,6 +46912,48 @@ type UpdateAdSetData = {
          *
          */
         bidStrategy?: (BidStrategy);
+        /**
+         * Meta only (400 elsewhere, before anything in the request is written). Writes the ad
+         * set's `dsa_beneficiary`, the legal entity that benefits from its ads, same field and
+         * limits as `dsaBeneficiary` on POST /v1/ads/create. Only the fields you send are
+         * written. It is the EU DSA field; for the regional regimes (Brazil, Malaysia,
+         * Thailand, Australia, Singapore, Taiwan, India) use `regionalRegulatedCategories` and
+         * `regionalRegulationIdentities` instead. Read it back with
+         * GET /v1/ads/ad-sets/{adSetId}?accountId={accountId}&fields=dsa_beneficiary,dsa_payor.
+         *
+         */
+        dsaBeneficiary?: string;
+        /**
+         * Meta only (400 elsewhere, before anything in the request is written). Writes the ad
+         * set's `dsa_payor`, the legal entity that pays for its ads, same field and limits as
+         * `dsaPayor` on POST /v1/ads/create. Can differ from `dsaBeneficiary`.
+         *
+         */
+        dsaPayor?: string;
+        /**
+         * Meta only (400 elsewhere, before anything in the request is written). Writes the ad
+         * set's `regional_regulated_categories`, same values as on POST /v1/ads/create
+         * (AUSTRALIA_FINSERV, AUSTRALIA_UNIVERSAL, BRAZIL_REGULATION, INDIA_FINSERV,
+         * MALAYSIA_UNIVERSAL, SINGAPORE_UNIVERSAL, TAIWAN_FINSERV, TAIWAN_UNIVERSAL,
+         * THAILAND_UNIVERSAL). Send it with `regionalRegulationIdentities`. An empty array is a 400.
+         *
+         */
+        regionalRegulatedCategories?: Array<(string)>;
+        /**
+         * Meta only (400 elsewhere, before anything in the request is written). Writes the ad
+         * set's `regional_regulation_identities`: the Verified identity IDs of the beneficiary
+         * and payer for each declared category, same keys and validation as on
+         * POST /v1/ads/create (for example `universal_beneficiary` / `universal_payer` for
+         * BRAZIL_REGULATION, MALAYSIA_UNIVERSAL and THAILAND_UNIVERSAL). Send each ID as a
+         * string of digits; an empty object is a 400. When Meta refuses the ad set for a missing
+         * verified advertiser, the 400 `platform_api_error` names the keys the declared categories
+         * expect in `details.expectedIdentityKeys`, as on create. Read both back with
+         * GET /v1/ads/ad-sets/{adSetId}?accountId={accountId}&fields=regional_regulated_categories,regional_regulation_identities.
+         *
+         */
+        regionalRegulationIdentities?: {
+            [key: string]: (string | number);
+        };
         /**
          * TikTok only (a 400 elsewhere). TikTok Smart Targeting on the ad group: `audience` is
          * TikTok's `smart_audience_enabled`, `interestsBehaviors` its `smart_interest_behavior_enabled`.

package/dist/index.js

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

package/src/generated/sdk.gen.ts

@@ -11575,7 +11575,10 @@ export const getAdSetDetails = <ThrowOnError extends boolean = false>(options: O
  * Changes an ad set's settings, such as its budget, bid strategy, status or delivery options.
  *
  * Use this for ABO budget updates, ad-set-scoped
- * pause/resume, bid-strategy edits, Meta value-rule-set attach/detach, and
+ * pause/resume, bid-strategy edits, Meta value-rule-set attach/detach, Meta
+ * beneficiary and payer (`dsaBeneficiary` / `dsaPayor` for the EU,
+ * `regionalRegulatedCategories` / `regionalRegulationIdentities` for the
+ * regional regimes), and
  * Meta-only post-launch delivery settings via `platformSpecificData`. At
  * least one updatable field is required.
  *

package/src/generated/types.gen.ts

@@ -19181,7 +19181,7 @@ export type WorkflowNode = {
      * **Variables** available from the start of every run (absent values are `''`): `lastMessage`, `inboundText`, `triggerText`, `conversationId`, `contact.name`, `contact.phone`, `contact.handle`, `contact.tags` (array), `contact.fields` (the contact's custom fields object), `contact.lastInteractionAt` (ISO date), `contact.lastInteractionHoursAgo` (number), `contact.isFollower` (Instagram, from the stored profile: true, false or `''` when unknown), `referral.ref`, `referral.source`, `referral.type`, `referral.adId`, `referral.adTitle` (the ad title or headline Meta sent), `referral.adName` (the synced ad's name, else `referral.adTitle`), `referral.campaignName` (the synced ad's campaign), `postback.payload`, `postback.title`, `quickReply.payload`, `quickReply.title`, `story.id`, `story.url`, `comment.id`, `comment.text`, `comment.platformPostId`, `reaction.emoji`, `reaction.action` (added|removed). `api_call` runs also get the request's `variables`, merged over these. `lead_received` runs also get `lead.id`, `lead.leadgenId`, `lead.formId`, `lead.formName`, `lead.adId`, `lead.adsetId`, `lead.campaignId` and every form answer by its key (`lead.full_name`, `lead.email`, `lead.phone_number`). Template `variableMapping` entries with `field: custom` interpolate `{{...}}` in `customValue`. An array or object interpolated into text renders as JSON.
      *
      * **send_message**: `{ messageType: text|template|media|interactive|cards, text, template, media:{mediaType:image|video|audio|document, url,caption}, interactive, buttons, quickReplies, messageTag }`. `template` is `{name,language,variableMapping}` for `messageType: template` and `{ type: generic, elements:[{ title, subtitle, imageUrl, buttons }] }` (1 to 10 cards) for `messageType: cards`. `template` and `interactive` are WhatsApp-only. `interactive.type` is inferred from the payload shape when omitted; payloads with neither `type` nor an inferable shape are rejected.
-     * Facebook and Instagram only (rejected with a 400 on other platforms; WhatsApp keeps `interactive`): `cards`, plus `buttons` on `text` (cards carry their own buttons) and `quickReplies` / `messageTag` on `text`, `media` and `cards`. `media` takes no `buttons` (a 400 at save). `buttons:[{ type: url|postback|phone, title, url, payload, phone, workflowId }]` (1 to 3, text only and the text then 640 characters at most, sent as Meta's button_template, `phone` Facebook-only, not inside cards), `quickReplies:[{ title, payload, imageUrl, workflowId }]` (1 to 13, not combined with `buttons`) and `messageTag: HUMAN_AGENT|CONFIRMED_EVENT_UPDATE|POST_PURCHASE_UPDATE|ACCOUNT_UPDATE` (Instagram accepts only `HUMAN_AGENT`). Titles are capped at 20 characters (80 for card titles and subtitles). A postback button or quick reply with no `payload` gets `zernio:workflow:<this workflow id>`, so a tap answers this workflow's pending `wait_for_reply` or restarts it; with `workflowId` (a 24-hex workflow id, not combined with `payload`) the tap starts that workflow instead.
+     * Facebook and Instagram only (rejected with a 400 on other platforms; WhatsApp keeps `interactive`): `cards`, plus `buttons` on `text` (cards carry their own buttons) and `quickReplies` / `messageTag` on `text`, `media` and `cards`. `media` takes no `buttons` (a 400 at save). `buttons:[{ type: url|postback|phone, title, url, payload, phone, workflowId }]` (1 to 3, text only and the text then 640 characters at most, sent as Meta's button_template, `phone` Facebook-only, not inside cards), `quickReplies:[{ title, payload, imageUrl, workflowId }]` (1 to 13, not combined with `buttons`). `messageTag` is not available: a workflow only sends within the 24h window, and `HUMAN_AGENT` is rejected with a 400 because it is only for replies typed by a person. Titles are capped at 20 characters (80 for card titles and subtitles). A postback button or quick reply with no `payload` gets `zernio:workflow:<this workflow id>`, so a tap answers this workflow's pending `wait_for_reply` or restarts it; with `workflowId` (a 24-hex workflow id, not combined with `payload`) the tap starts that workflow instead.
      *
      * **wait_for_reply**: `{ timeoutMinutes:int (max 43200), saveAs:string }`. Resume via the `'reply'` edge on inbound, or `'timeout'` edge after `timeoutMinutes` of silence. On Facebook and Instagram a button tap sets `{{postback.payload}}` / `{{postback.title}}` and a quick reply tap sets `{{quickReply.payload}}` / `{{quickReply.title}}`; each reply clears the previous tap.
      *
@@ -33512,7 +33512,7 @@ export type SendInboxMessageData = {
          */
         messagingType?: 'RESPONSE' | 'UPDATE' | 'MESSAGE_TAG';
         /**
-         * Facebook message tag for messaging outside 24h window. Requires messagingType MESSAGE_TAG. Instagram only supports HUMAN_AGENT.
+         * Facebook and Instagram. To reply after the 24h window, send HUMAN_AGENT with messagingType MESSAGE_TAG: it works up to 7 days after the person's last message, for replies typed by a person only (Meta does not allow it on automated messages). Meta retired the other tags, so they fail.
          */
         messageTag?: 'CONFIRMED_EVENT_UPDATE' | 'POST_PURCHASE_UPDATE' | 'ACCOUNT_UPDATE' | 'HUMAN_AGENT';
         /**
@@ -43562,7 +43562,7 @@ export type CreateBroadcastData = {
                 filename?: string;
             }>;
             /**
-             * Instagram and Facebook only. Meta message tag sent with every recipient message (messaging_type MESSAGE_TAG) so the broadcast can reach people outside the 24h window. Instagram accepts HUMAN_AGENT only. Rejected with a 400 on any other platform.
+             * Not usable: a broadcast only reaches people within the 24h window. HUMAN_AGENT is rejected with a 400 because it is only for replies typed by a person, and Meta retired the other tags.
              */
             messageTag?: 'CONFIRMED_EVENT_UPDATE' | 'POST_PURCHASE_UPDATE' | 'ACCOUNT_UPDATE' | 'HUMAN_AGENT';
         };
@@ -47598,6 +47598,48 @@ export type UpdateAdSetData = {
          *
          */
         bidStrategy?: (BidStrategy);
+        /**
+         * Meta only (400 elsewhere, before anything in the request is written). Writes the ad
+         * set's `dsa_beneficiary`, the legal entity that benefits from its ads, same field and
+         * limits as `dsaBeneficiary` on POST /v1/ads/create. Only the fields you send are
+         * written. It is the EU DSA field; for the regional regimes (Brazil, Malaysia,
+         * Thailand, Australia, Singapore, Taiwan, India) use `regionalRegulatedCategories` and
+         * `regionalRegulationIdentities` instead. Read it back with
+         * GET /v1/ads/ad-sets/{adSetId}?accountId={accountId}&fields=dsa_beneficiary,dsa_payor.
+         *
+         */
+        dsaBeneficiary?: string;
+        /**
+         * Meta only (400 elsewhere, before anything in the request is written). Writes the ad
+         * set's `dsa_payor`, the legal entity that pays for its ads, same field and limits as
+         * `dsaPayor` on POST /v1/ads/create. Can differ from `dsaBeneficiary`.
+         *
+         */
+        dsaPayor?: string;
+        /**
+         * Meta only (400 elsewhere, before anything in the request is written). Writes the ad
+         * set's `regional_regulated_categories`, same values as on POST /v1/ads/create
+         * (AUSTRALIA_FINSERV, AUSTRALIA_UNIVERSAL, BRAZIL_REGULATION, INDIA_FINSERV,
+         * MALAYSIA_UNIVERSAL, SINGAPORE_UNIVERSAL, TAIWAN_FINSERV, TAIWAN_UNIVERSAL,
+         * THAILAND_UNIVERSAL). Send it with `regionalRegulationIdentities`. An empty array is a 400.
+         *
+         */
+        regionalRegulatedCategories?: Array<(string)>;
+        /**
+         * Meta only (400 elsewhere, before anything in the request is written). Writes the ad
+         * set's `regional_regulation_identities`: the Verified identity IDs of the beneficiary
+         * and payer for each declared category, same keys and validation as on
+         * POST /v1/ads/create (for example `universal_beneficiary` / `universal_payer` for
+         * BRAZIL_REGULATION, MALAYSIA_UNIVERSAL and THAILAND_UNIVERSAL). Send each ID as a
+         * string of digits; an empty object is a 400. When Meta refuses the ad set for a missing
+         * verified advertiser, the 400 `platform_api_error` names the keys the declared categories
+         * expect in `details.expectedIdentityKeys`, as on create. Read both back with
+         * GET /v1/ads/ad-sets/{adSetId}?accountId={accountId}&fields=regional_regulated_categories,regional_regulation_identities.
+         *
+         */
+        regionalRegulationIdentities?: {
+            [key: string]: (string | number);
+        };
         /**
          * TikTok only (a 400 elsewhere). TikTok Smart Targeting on the ad group: `audience` is
          * TikTok's `smart_audience_enabled`, `interestsBehaviors` its `smart_interest_behavior_enabled`.