sentdm 0.31.0 → 0.32.0

data/rbi/sentdm/models/template.rbi

@@ -18,6 +18,21 @@ module Sentdm
       sig { params(id: String).void }
       attr_writer :id
 
+      # Which consent keyword this template answers, when it is one of Sent's
+      # auto-replies: OPT_IN, OPT_OUT, HELP, or OTHER for a customer-defined keyword.
+      # Null for an ordinary template, and omitted from the response, so its presence is
+      # the answer to "is this an auto-reply".
+      #
+      # Deliberately not required, unlike CustomerId, even though the same "no single
+      # mapper" argument applies: NJsonSchema publishes a C# required member in the
+      # schema's required array, so the contract would have advertised a field this
+      # response omits for every ordinary template, and a generated client could refuse
+      # the common case. A compile-time guard is not worth a wrong published contract.
+      # Every mapping site sets it explicitly, and TemplateResponseSchemaTests pins the
+      # field as optional so it cannot be reintroduced.
+      sig { returns(T.nilable(String)) }
+      attr_accessor :auto_reply_action
+
       # Template category: MARKETING, UTILITY, AUTHENTICATION
       sig { returns(T.nilable(String)) }
       attr_reader :category
@@ -25,7 +40,18 @@ module Sentdm
       sig { params(category: String).void }
       attr_writer :category
 
-      # Supported channels: sms, whatsapp
+      # The channels this template's definition can render on, in canonical order: sms,
+      # whatsapp, rcs.
+      #
+      # Derived from the definition's body, mirroring each channel's send-time fallback
+      # chain, so a channel is listed only when a real body would be produced for it:
+      # SMS reads sms ?? multiChannel, WhatsApp reads whatsapp ?? multiChannel, and RCS
+      # reads rcs ?? multiChannel ?? sms. A multiChannel body therefore reports all
+      # three, and the extra SMS fallback on RCS is why an sms/whatsapp pair reports RCS
+      # too.
+      #
+      # This says what the content can render on, not what may be sent: sending also
+      # needs the template approved for that channel.
       sig { returns(T.nilable(T::Array[String])) }
       attr_accessor :channels
 
@@ -57,7 +83,8 @@ module Sentdm
       sig { params(name: String).void }
       attr_writer :name
 
-      # Template status: APPROVED, PENDING, REJECTED
+      # Template status: DRAFT, PENDING, APPROVED, REJECTED. A template created with
+      # submit_for_review: false starts as DRAFT and stays there until it is submitted.
       sig { returns(T.nilable(String)) }
       attr_reader :status
 
@@ -77,6 +104,7 @@ module Sentdm
         params(
           customer_id: String,
           id: String,
+          auto_reply_action: T.nilable(String),
           category: String,
           channels: T.nilable(T::Array[String]),
           created_at: Time,
@@ -94,9 +122,33 @@ module Sentdm
         customer_id:,
         # Unique template identifier
         id: nil,
+        # Which consent keyword this template answers, when it is one of Sent's
+        # auto-replies: OPT_IN, OPT_OUT, HELP, or OTHER for a customer-defined keyword.
+        # Null for an ordinary template, and omitted from the response, so its presence is
+        # the answer to "is this an auto-reply".
+        #
+        # Deliberately not required, unlike CustomerId, even though the same "no single
+        # mapper" argument applies: NJsonSchema publishes a C# required member in the
+        # schema's required array, so the contract would have advertised a field this
+        # response omits for every ordinary template, and a generated client could refuse
+        # the common case. A compile-time guard is not worth a wrong published contract.
+        # Every mapping site sets it explicitly, and TemplateResponseSchemaTests pins the
+        # field as optional so it cannot be reintroduced.
+        auto_reply_action: nil,
         # Template category: MARKETING, UTILITY, AUTHENTICATION
         category: nil,
-        # Supported channels: sms, whatsapp
+        # The channels this template's definition can render on, in canonical order: sms,
+        # whatsapp, rcs.
+        #
+        # Derived from the definition's body, mirroring each channel's send-time fallback
+        # chain, so a channel is listed only when a real body would be produced for it:
+        # SMS reads sms ?? multiChannel, WhatsApp reads whatsapp ?? multiChannel, and RCS
+        # reads rcs ?? multiChannel ?? sms. A multiChannel body therefore reports all
+        # three, and the extra SMS fallback on RCS is why an sms/whatsapp pair reports RCS
+        # too.
+        #
+        # This says what the content can render on, not what may be sent: sending also
+        # needs the template approved for that channel.
         channels: nil,
         # When the template was created
         created_at: nil,
@@ -106,7 +158,8 @@ module Sentdm
         language: nil,
         # Template display name
         name: nil,
-        # Template status: APPROVED, PENDING, REJECTED
+        # Template status: DRAFT, PENDING, APPROVED, REJECTED. A template created with
+        # submit_for_review: false starts as DRAFT and stays there until it is submitted.
         status: nil,
         # When the template was last updated
         updated_at: nil,
@@ -120,6 +173,7 @@ module Sentdm
           {
             customer_id: String,
             id: String,
+            auto_reply_action: T.nilable(String),
             category: String,
             channels: T.nilable(T::Array[String]),
             created_at: Time,

data/rbi/sentdm/models/template_body.rbi

@@ -6,8 +6,7 @@ module Sentdm
       OrHash =
         T.type_alias { T.any(Sentdm::TemplateBody, Sentdm::Internal::AnyHash) }
 
-      # Content that will be used for all channels (SMS and WhatsApp) unless
-      # channel-specific content is provided
+      # The shared body, used for every channel. One half of the choice described above.
       sig { returns(T.nilable(Sentdm::TemplateBodyContent)) }
       attr_reader :multi_channel
 
@@ -18,22 +17,23 @@ module Sentdm
       end
       attr_writer :multi_channel
 
-      # RCS-specific content that overrides multi-channel content for RCS messages
+      # RCS-specific copy that overrides the chosen strategy for RCS only. The one true
+      # override: optional on top of either strategy, but it cannot be the only body
+      # present. Its length cap is the higher one described on Template.
       sig { returns(T.nilable(Sentdm::TemplateBodyContent)) }
       attr_reader :rcs
 
       sig { params(rcs: T.nilable(Sentdm::TemplateBodyContent::OrHash)).void }
       attr_writer :rcs
 
-      # SMS-specific content that overrides multi-channel content for SMS messages
+      # The SMS body. It does not override multiChannel, it replaces it.
       sig { returns(T.nilable(Sentdm::TemplateBodyContent)) }
       attr_reader :sms
 
       sig { params(sms: T.nilable(Sentdm::TemplateBodyContent::OrHash)).void }
       attr_writer :sms
 
-      # WhatsApp-specific content that overrides multi-channel content for WhatsApp
-      # messages
+      # The WhatsApp body. It does not override multiChannel, it replaces it.
       sig { returns(T.nilable(Sentdm::TemplateBodyContent)) }
       attr_reader :whatsapp
 
@@ -42,7 +42,16 @@ module Sentdm
       end
       attr_writer :whatsapp
 
-      # Body section of a message template with channel-specific content
+      # Body section of a message template.
+      #
+      # A body picks one of two authoring strategies, and mixing them is refused
+      # (TemplateDefinitionValidator.HaveValidChannelConfiguration): a shared
+      # multiChannel body on its own, or an explicit sms + whatsapp pair, both present.
+      #
+      # multiChannel together with sms or whatsapp is rejected, and so is sms or
+      # whatsapp on its own — every template is expected to be deliverable on every
+      # channel. rcs is the one true override: it may accompany either strategy to vary
+      # the copy, but cannot stand alone.
       sig do
         params(
           multi_channel: T.nilable(Sentdm::TemplateBodyContent::OrHash),
@@ -52,15 +61,15 @@ module Sentdm
         ).returns(T.attached_class)
       end
       def self.new(
-        # Content that will be used for all channels (SMS and WhatsApp) unless
-        # channel-specific content is provided
+        # The shared body, used for every channel. One half of the choice described above.
         multi_channel: nil,
-        # RCS-specific content that overrides multi-channel content for RCS messages
+        # RCS-specific copy that overrides the chosen strategy for RCS only. The one true
+        # override: optional on top of either strategy, but it cannot be the only body
+        # present. Its length cap is the higher one described on Template.
         rcs: nil,
-        # SMS-specific content that overrides multi-channel content for SMS messages
+        # The SMS body. It does not override multiChannel, it replaces it.
         sms: nil,
-        # WhatsApp-specific content that overrides multi-channel content for WhatsApp
-        # messages
+        # The WhatsApp body. It does not override multiChannel, it replaces it.
         whatsapp: nil
       )
       end

data/rbi/sentdm/models/template_body_content.rbi

@@ -8,12 +8,39 @@ module Sentdm
           T.any(Sentdm::TemplateBodyContent, Sentdm::Internal::AnyHash)
         end
 
+      # The body copy, with variables written as {{index:variable}}.
+      #
+      # Length cap depends on which channel this body belongs to:
+      # TemplateContentLimits.MaxBodyLength (1024) for multiChannel, sms and whatsapp —
+      # Meta's BODY limit, which a multiChannel body may be delivered under — and
+      # TemplateContentLimits.MaxRcsBodyLength (3072) for an rcs body, which never
+      # reaches Meta. The maxLength advertised on this schema is the 1024 one, because
+      # all four channel bodies share this single schema — an rcs body between the two
+      # is accepted.
+      #
+      # Meta requires every variable to carry surrounding context, so a body is refused
+      # unless it also satisfies all of the following (enforced by
+      # TemplateDefinitionValidator): At least one letter before the first variable and
+      # after the last — trailing punctuation such as "... {{1:variable}}." does not
+      # count. At least (2 × variable count) + 1 words once the placeholders are
+      # removed. No two variables adjacent with only whitespace between them. No leading
+      # or trailing newline, no more than two consecutive line breaks, and no more than
+      # four consecutive spaces.
+      #
+      # Example: "Hello {{0:variable}}! Welcome to {{1:variable}}. We are glad to have
+      # you on board." — two variables, so at least five words are required, and the
+      # copy after the final variable contains letters.
       sig { returns(String) }
       attr_accessor :template
 
+      # The type of body content — send "text". It is dropped from the stored definition
+      # when null, so a body posted without it is saved with no type key at all and the
+      # template editor has nothing to render the block from.
       sig { returns(T.nilable(String)) }
       attr_accessor :type
 
+      # The variables referenced by the body copy, one entry per {{index:variable}}
+      # placeholder.
       sig { returns(T.nilable(T::Array[Sentdm::TemplateVariable])) }
       attr_accessor :variables
 
@@ -24,7 +51,38 @@ module Sentdm
           variables: T.nilable(T::Array[Sentdm::TemplateVariable::OrHash])
         ).returns(T.attached_class)
       end
-      def self.new(template:, type: nil, variables: nil)
+      def self.new(
+        # The body copy, with variables written as {{index:variable}}.
+        #
+        # Length cap depends on which channel this body belongs to:
+        # TemplateContentLimits.MaxBodyLength (1024) for multiChannel, sms and whatsapp —
+        # Meta's BODY limit, which a multiChannel body may be delivered under — and
+        # TemplateContentLimits.MaxRcsBodyLength (3072) for an rcs body, which never
+        # reaches Meta. The maxLength advertised on this schema is the 1024 one, because
+        # all four channel bodies share this single schema — an rcs body between the two
+        # is accepted.
+        #
+        # Meta requires every variable to carry surrounding context, so a body is refused
+        # unless it also satisfies all of the following (enforced by
+        # TemplateDefinitionValidator): At least one letter before the first variable and
+        # after the last — trailing punctuation such as "... {{1:variable}}." does not
+        # count. At least (2 × variable count) + 1 words once the placeholders are
+        # removed. No two variables adjacent with only whitespace between them. No leading
+        # or trailing newline, no more than two consecutive line breaks, and no more than
+        # four consecutive spaces.
+        #
+        # Example: "Hello {{0:variable}}! Welcome to {{1:variable}}. We are glad to have
+        # you on board." — two variables, so at least five words are required, and the
+        # copy after the final variable contains letters.
+        template:,
+        # The type of body content — send "text". It is dropped from the stored definition
+        # when null, so a body posted without it is saved with no type key at all and the
+        # template editor has nothing to render the block from.
+        type: nil,
+        # The variables referenced by the body copy, one entry per {{index:variable}}
+        # placeholder.
+        variables: nil
+      )
       end
 
       sig do

data/rbi/sentdm/models/template_button.rbi

@@ -19,7 +19,13 @@ module Sentdm
       sig { returns(String) }
       attr_accessor :type
 
-      # The unique identifier of the button (1-based index)
+      # The button's identifier (1-based index), unique within the template.
+      #
+      # Omitting it is only safe for a template holding a single button. The field is a
+      # non-nullable int, so every button that leaves it out defaults to 0, and two such
+      # buttons are refused by the unique-id rule ("Button IDs must be unique"). Number
+      # them from 1 in the order they should appear — order matters on RCS, where only
+      # the first four buttons render.
       sig { returns(T.nilable(Integer)) }
       attr_reader :id
 
@@ -39,7 +45,13 @@ module Sentdm
         props:,
         # The type of button (e.g., QUICK_REPLY, URL, PHONE_NUMBER, VOICE_CALL, COPY_CODE)
         type:,
-        # The unique identifier of the button (1-based index)
+        # The button's identifier (1-based index), unique within the template.
+        #
+        # Omitting it is only safe for a template holding a single button. The field is a
+        # non-nullable int, so every button that leaves it out defaults to 0, and two such
+        # buttons are refused by the unique-id rule ("Button IDs must be unique"). Number
+        # them from 1 in the order they should appear — order matters on RCS, where only
+        # the first four buttons render.
         id: nil
       )
       end

data/rbi/sentdm/models/template_button_props.rbi

@@ -23,6 +23,17 @@ module Sentdm
       sig { returns(String) }
       attr_accessor :quick_reply_type
 
+      # The button's label. Required for every button type, and capped at
+      # TemplateContentLimits.MaxButtonTextLength (25) characters.
+      #
+      # Meta accepts only static text here, so a label is refused when it contains a
+      # {{...}} variable placeholder, a newline, an emoji, or WhatsApp formatting markup
+      # (\*, \_, ~) — enforced by ApplyButtonLabelContentRules in
+      # TemplateButtonValidator. Meta reports all four as one error: "Buttons can't have
+      # any variables, newlines, emojis, or formatting characters."
+      #
+      # AUTHENTICATION OTP buttons are the exception: Meta auto-localizes their label
+      # from the template language, and the converter drops whatever text was sent.
       sig { returns(String) }
       attr_accessor :text
 
@@ -73,6 +84,17 @@ module Sentdm
         offer_code:,
         phone_number:,
         quick_reply_type:,
+        # The button's label. Required for every button type, and capped at
+        # TemplateContentLimits.MaxButtonTextLength (25) characters.
+        #
+        # Meta accepts only static text here, so a label is refused when it contains a
+        # {{...}} variable placeholder, a newline, an emoji, or WhatsApp formatting markup
+        # (\*, \_, ~) — enforced by ApplyButtonLabelContentRules in
+        # TemplateButtonValidator. Meta reports all four as one error: "Buttons can't have
+        # any variables, newlines, emojis, or formatting characters."
+        #
+        # AUTHENTICATION OTP buttons are the exception: Meta auto-localizes their label
+        # from the template language, and the converter drops whatever text was sent.
         text:,
         url:,
         url_type:,

data/rbi/sentdm/models/template_definition.rbi

@@ -8,7 +8,16 @@ module Sentdm
           T.any(Sentdm::TemplateDefinition, Sentdm::Internal::AnyHash)
         end
 
-      # Body section of a message template with channel-specific content
+      # Body section of a message template.
+      #
+      # A body picks one of two authoring strategies, and mixing them is refused
+      # (TemplateDefinitionValidator.HaveValidChannelConfiguration): a shared
+      # multiChannel body on its own, or an explicit sms + whatsapp pair, both present.
+      #
+      # multiChannel together with sms or whatsapp is rejected, and so is sms or
+      # whatsapp on its own — every template is expected to be deliverable on every
+      # channel. rcs is the one true override: it may accompany either strategy to vary
+      # the copy, but cannot stand alone.
       sig { returns(Sentdm::TemplateBody) }
       attr_reader :body
 
@@ -62,7 +71,16 @@ module Sentdm
         ).returns(T.attached_class)
       end
       def self.new(
-        # Body section of a message template with channel-specific content
+        # Body section of a message template.
+        #
+        # A body picks one of two authoring strategies, and mixing them is refused
+        # (TemplateDefinitionValidator.HaveValidChannelConfiguration): a shared
+        # multiChannel body on its own, or an explicit sms + whatsapp pair, both present.
+        #
+        # multiChannel together with sms or whatsapp is rejected, and so is sms or
+        # whatsapp on its own — every template is expected to be deliverable on every
+        # channel. rcs is the one true override: it may accompany either strategy to vary
+        # the copy, but cannot stand alone.
         body:,
         # Configuration for AUTHENTICATION category templates
         authentication_config: nil,

data/rbi/sentdm/models/template_event.rbi

@@ -6,14 +6,14 @@ module Sentdm
       OrHash =
         T.type_alias { T.any(Sentdm::TemplateEvent, Sentdm::Internal::AnyHash) }
 
-      # The specific event within the family, for example message.delivered or
-      # message.received. Absent on events that have no subtype, so treat it as
-      # optional.
+      # The specific event within the family, for example message.delivered,
+      # message.received or contact.opt_out. Absent on events that have no subtype, so
+      # treat it as optional.
       sig { returns(T.nilable(String)) }
       attr_accessor :event
 
-      # The event family, for example message or templates. Route on this first, then on
-      # event for the specific change.
+      # The event family, for example message, templates or contact. Route on this
+      # first, then on event for the specific change.
       sig { returns(T.nilable(String)) }
       attr_reader :field
 
@@ -30,6 +30,10 @@ module Sentdm
       end
       attr_writer :payload
 
+      # The event-specific body.
+      sig { returns(T.nilable(String)) }
+      attr_accessor :request_id
+
       # When Sent emitted the event, in UTC (yyyy-MM-ddTHH:mm:ssZ). This is the emission
       # time, not the time the underlying change happened. Use the timestamp inside the
       # payload for the latter.
@@ -46,20 +50,23 @@ module Sentdm
           event: T.nilable(String),
           field: String,
           payload: T.nilable(Sentdm::TemplateEventPayload::OrHash),
+          request_id: T.nilable(String),
           timestamp: String
         ).returns(T.attached_class)
       end
       def self.new(
-        # The specific event within the family, for example message.delivered or
-        # message.received. Absent on events that have no subtype, so treat it as
-        # optional.
+        # The specific event within the family, for example message.delivered,
+        # message.received or contact.opt_out. Absent on events that have no subtype, so
+        # treat it as optional.
         event: nil,
-        # The event family, for example message or templates. Route on this first, then on
-        # event for the specific change.
+        # The event family, for example message, templates or contact. Route on this
+        # first, then on event for the specific change.
         field: nil,
         # Body of a template status event. Delivered when a template's review outcome
         # changes, so you can react without polling.
         payload: nil,
+        # The event-specific body.
+        request_id: nil,
         # When Sent emitted the event, in UTC (yyyy-MM-ddTHH:mm:ssZ). This is the emission
         # time, not the time the underlying change happened. Use the timestamp inside the
         # payload for the latter.
@@ -73,6 +80,7 @@ module Sentdm
             event: T.nilable(String),
             field: String,
             payload: T.nilable(Sentdm::TemplateEventPayload),
+            request_id: T.nilable(String),
             timestamp: String
           }
         )

data/rbi/sentdm/models/template_event_payload.rbi

@@ -24,6 +24,23 @@ module Sentdm
       sig { params(account_id: String).void }
       attr_writer :account_id
 
+      # Which consent keyword this template answers, when it is one of Sent's
+      # auto-replies: OPT_IN, OPT_OUT, HELP, or OTHER for a customer-defined keyword.
+      #
+      # Omitted for an ordinary template, so its presence is the answer to "is this an
+      # auto-reply". Sent creates the three compliance auto-replies at signup and they
+      # go through review like any other template, so their events arrive mixed in with
+      # the customer's own with nothing else to tell them apart.
+      #
+      # Named for the reader rather than after Template.OptAction, which it is mapped
+      # from. The MCP tool result deliberately keeps OptAction, OptKeywords and IsOpt:
+      # it mirrors the internal shape on purpose and publishes the keywords too, so
+      # renaming one of the three there would leave a surface half in each vocabulary.
+      # Two names for one concept, each consistent within its own surface, chosen over a
+      # rename that breaks MCP clients silently.
+      sig { returns(T.nilable(String)) }
+      attr_accessor :auto_reply_action
+
       # The template's category, for example UTILITY, MARKETING, or AUTHENTICATION.
       sig { returns(T.nilable(String)) }
       attr_reader :category
@@ -31,12 +48,15 @@ module Sentdm
       sig { params(category: String).void }
       attr_writer :category
 
-      # The channel the template applies to.
+      # The channel leg this decision is about, for example whatsapp, sms, or rcs. A
+      # template is reviewed per channel and the legs come back independently, so each
+      # one reports separately.
+      #
+      # Omitted when the decision applies to the template as a whole rather than to one
+      # leg. That event is the broader news: a template-wide rejection blocks every
+      # channel, whatever the individual legs say.
       sig { returns(T.nilable(String)) }
-      attr_reader :channel
-
-      sig { params(channel: String).void }
-      attr_writer :channel
+      attr_accessor :channel
 
       # The template's language code, for example en_US.
       sig { returns(T.nilable(String)) }
@@ -71,8 +91,9 @@ module Sentdm
           status: String,
           whatsapp_template_id: String,
           account_id: String,
+          auto_reply_action: T.nilable(String),
           category: String,
-          channel: String,
+          channel: T.nilable(String),
           language: String,
           reason: T.nilable(String),
           template_id: String,
@@ -87,9 +108,30 @@ module Sentdm
         whatsapp_template_id:,
         # The account the template belongs to.
         account_id: nil,
+        # Which consent keyword this template answers, when it is one of Sent's
+        # auto-replies: OPT_IN, OPT_OUT, HELP, or OTHER for a customer-defined keyword.
+        #
+        # Omitted for an ordinary template, so its presence is the answer to "is this an
+        # auto-reply". Sent creates the three compliance auto-replies at signup and they
+        # go through review like any other template, so their events arrive mixed in with
+        # the customer's own with nothing else to tell them apart.
+        #
+        # Named for the reader rather than after Template.OptAction, which it is mapped
+        # from. The MCP tool result deliberately keeps OptAction, OptKeywords and IsOpt:
+        # it mirrors the internal shape on purpose and publishes the keywords too, so
+        # renaming one of the three there would leave a surface half in each vocabulary.
+        # Two names for one concept, each consistent within its own surface, chosen over a
+        # rename that breaks MCP clients silently.
+        auto_reply_action: nil,
         # The template's category, for example UTILITY, MARKETING, or AUTHENTICATION.
         category: nil,
-        # The channel the template applies to.
+        # The channel leg this decision is about, for example whatsapp, sms, or rcs. A
+        # template is reviewed per channel and the legs come back independently, so each
+        # one reports separately.
+        #
+        # Omitted when the decision applies to the template as a whole rather than to one
+        # leg. That event is the broader news: a template-wide rejection blocks every
+        # channel, whatever the individual legs say.
         channel: nil,
         # The template's language code, for example en_US.
         language: nil,
@@ -109,8 +151,9 @@ module Sentdm
             status: String,
             whatsapp_template_id: String,
             account_id: String,
+            auto_reply_action: T.nilable(String),
             category: String,
-            channel: String,
+            channel: T.nilable(String),
             language: String,
             reason: T.nilable(String),
             template_id: String,

data/rbi/sentdm/models/template_variable.rbi

@@ -8,6 +8,9 @@ module Sentdm
           T.any(Sentdm::TemplateVariable, Sentdm::Internal::AnyHash)
         end
 
+      # The variable's name, and the key callers use for it in a send request's
+      # parameters object. Must start with a letter and hold only letters, digits and
+      # underscores.
       sig { returns(String) }
       attr_accessor :name
 
@@ -17,9 +20,17 @@ module Sentdm
       sig { params(props: Sentdm::TemplateVariable::Props::OrHash).void }
       attr_writer :props
 
+      # One of variable, link or media. Decides which Props fields are required.
       sig { returns(String) }
       attr_accessor :type
 
+      # The variable's index, and the number its {{index:variable}} placeholder refers
+      # to.
+      #
+      # Omitting it is only safe for a section holding a single variable. The field is a
+      # non-nullable int, so every variable that leaves it out defaults to 0, and a
+      # section with two such variables is refused by the unique-id rule ("variables
+      # must have unique IDs"). Number them from 0 in the order they appear.
       sig { returns(T.nilable(Integer)) }
       attr_reader :id
 
@@ -34,7 +45,23 @@ module Sentdm
           id: Integer
         ).returns(T.attached_class)
       end
-      def self.new(name:, props:, type:, id: nil)
+      def self.new(
+        # The variable's name, and the key callers use for it in a send request's
+        # parameters object. Must start with a letter and hold only letters, digits and
+        # underscores.
+        name:,
+        props:,
+        # One of variable, link or media. Decides which Props fields are required.
+        type:,
+        # The variable's index, and the number its {{index:variable}} placeholder refers
+        # to.
+        #
+        # Omitting it is only safe for a section holding a single variable. The field is a
+        # non-nullable int, so every variable that leaves it out defaults to 0, and a
+        # section with two such variables is refused by the unique-id rule ("variables
+        # must have unique IDs"). Number them from 0 in the order they appear.
+        id: nil
+      )
       end
 
       sig do

data/rbi/sentdm/models/webhook_list_events_response.rbi

@@ -39,9 +39,9 @@ module Sentdm
       attr_accessor :error_message
 
       # The exact event body that was delivered, or attempted, for this record. One of
-      # the three webhook envelopes: a message status change, an inbound message, or a
-      # template status change. Read field and event to tell which, the same way your
-      # endpoint does.
+      # the four webhook envelopes: a message status change, an inbound message, a
+      # template status change, or a contact consent signal. Read field and event to
+      # tell which, the same way your endpoint does.
       sig do
         returns(
           T.nilable(
@@ -57,7 +57,9 @@ module Sentdm
             T.any(
               Sentdm::MessageEvent::OrHash,
               Sentdm::InboundMessageEvent::OrHash,
-              Sentdm::TemplateEvent::OrHash
+              Sentdm::TemplateEvent::OrHash,
+              Sentdm::ChannelEvent::OrHash,
+              Sentdm::ContactEvent::OrHash
             )
         ).void
       end
@@ -92,7 +94,9 @@ module Sentdm
             T.any(
               Sentdm::MessageEvent::OrHash,
               Sentdm::InboundMessageEvent::OrHash,
-              Sentdm::TemplateEvent::OrHash
+              Sentdm::TemplateEvent::OrHash,
+              Sentdm::ChannelEvent::OrHash,
+              Sentdm::ContactEvent::OrHash
             ),
           event_type: String,
           http_status_code: T.nilable(Integer),
@@ -108,9 +112,9 @@ module Sentdm
         delivery_status: nil,
         error_message: nil,
         # The exact event body that was delivered, or attempted, for this record. One of
-        # the three webhook envelopes: a message status change, an inbound message, or a
-        # template status change. Read field and event to tell which, the same way your
-        # endpoint does.
+        # the four webhook envelopes: a message status change, an inbound message, a
+        # template status change, or a contact consent signal. Read field and event to
+        # tell which, the same way your endpoint does.
         event_data: nil,
         event_type: nil,
         http_status_code: nil,
@@ -142,9 +146,9 @@ module Sentdm
       end
 
       # The exact event body that was delivered, or attempted, for this record. One of
-      # the three webhook envelopes: a message status change, an inbound message, or a
-      # template status change. Read field and event to tell which, the same way your
-      # endpoint does.
+      # the four webhook envelopes: a message status change, an inbound message, a
+      # template status change, or a contact consent signal. Read field and event to
+      # tell which, the same way your endpoint does.
       module EventData
         extend Sentdm::Internal::Type::Union
 
@@ -153,7 +157,9 @@ module Sentdm
             T.any(
               Sentdm::MessageEvent,
               Sentdm::InboundMessageEvent,
-              Sentdm::TemplateEvent
+              Sentdm::TemplateEvent,
+              Sentdm::ChannelEvent,
+              Sentdm::ContactEvent
             )
           end