trycourier 6.6.0 → 6.8.0

data/rbi/courier/models/topic_digest_request.rbi

@@ -8,12 +8,6 @@ module Courier
           T.any(Courier::TopicDigestRequest, Courier::Internal::AnyHash)
         end
 
-      # The cadences this digest delivers on. At least one is required: a digest with no
-      # schedule collects events into an instance that can never fire. Omitting the key
-      # on a replace leaves stored schedules untouched; sending `[]` is a `400`.
-      sig { returns(T::Array[Courier::TopicDigestScheduleRequest]) }
-      attr_accessor :schedules
-
       # The notification template that renders the digest. A digest with no template
       # collects nothing, so this is required.
       sig { returns(String) }
@@ -36,6 +30,31 @@ module Courier
       end
       attr_writer :categories
 
+      # The cadences this digest delivers on.
+      #
+      # The array replaces the stored schedules wholesale, so a schedule you leave out
+      # of it is deleted along with its delivery rule. Omit the key entirely to leave
+      # the stored schedules untouched — useful for changing `template_id` or
+      # `categories` without restating every schedule.
+      #
+      # A digest must end up with at least one schedule, because one with none collects
+      # events into an instance that can never fire. So sending `[]` is always a `400`,
+      # and so is omitting the key on a topic that has no schedules stored yet.
+      #
+      # On **create** the key is required outright: a topic being created has nothing
+      # stored to leave alone, and the topic row is written before its digest, so
+      # rejecting it any later would leave the topic behind and let a retry duplicate
+      # it.
+      sig { returns(T.nilable(T::Array[Courier::TopicDigestScheduleRequest])) }
+      attr_reader :schedules
+
+      sig do
+        params(
+          schedules: T::Array[Courier::TopicDigestScheduleRequest::OrHash]
+        ).void
+      end
+      attr_writer :schedules
+
       # Whether to deliver the digest even when nothing was collected.
       sig { returns(T.nilable(T::Boolean)) }
       attr_reader :trigger_empty
@@ -52,18 +71,14 @@ module Courier
       # merely off.
       sig do
         params(
-          schedules: T::Array[Courier::TopicDigestScheduleRequest::OrHash],
           template_id: String,
           audience_id: String,
           categories: T::Array[Courier::TopicDigestCategory::OrHash],
+          schedules: T::Array[Courier::TopicDigestScheduleRequest::OrHash],
           trigger_empty: T::Boolean
         ).returns(T.attached_class)
       end
       def self.new(
-        # The cadences this digest delivers on. At least one is required: a digest with no
-        # schedule collects events into an instance that can never fire. Omitting the key
-        # on a replace leaves stored schedules untouched; sending `[]` is a `400`.
-        schedules:,
         # The notification template that renders the digest. A digest with no template
         # collects nothing, so this is required.
         template_id:,
@@ -72,6 +87,22 @@ module Courier
         # Retention rules per category key. Defaults to a single `digest` category
         # retaining `FIRST`.
         categories: nil,
+        # The cadences this digest delivers on.
+        #
+        # The array replaces the stored schedules wholesale, so a schedule you leave out
+        # of it is deleted along with its delivery rule. Omit the key entirely to leave
+        # the stored schedules untouched — useful for changing `template_id` or
+        # `categories` without restating every schedule.
+        #
+        # A digest must end up with at least one schedule, because one with none collects
+        # events into an instance that can never fire. So sending `[]` is always a `400`,
+        # and so is omitting the key on a topic that has no schedules stored yet.
+        #
+        # On **create** the key is required outright: a topic being created has nothing
+        # stored to leave alone, and the topic row is written before its digest, so
+        # rejecting it any later would leave the topic behind and let a retry duplicate
+        # it.
+        schedules: nil,
         # Whether to deliver the digest even when nothing was collected.
         trigger_empty: nil
       )
@@ -80,10 +111,10 @@ module Courier
       sig do
         override.returns(
           {
-            schedules: T::Array[Courier::TopicDigestScheduleRequest],
             template_id: String,
             audience_id: String,
             categories: T::Array[Courier::TopicDigestCategory],
+            schedules: T::Array[Courier::TopicDigestScheduleRequest],
             trigger_empty: T::Boolean
           }
         )

data/rbi/courier/models/topic_digest_schedule_request.rbi

@@ -79,6 +79,12 @@ module Courier
       # existing schedule in place; omit it and one is assigned and returned. The
       # `schedules` array is a full replacement, so a stored schedule absent from it is
       # deleted along with its delivery rule.
+      #
+      # Updating by `schedule_id` replaces that schedule rather than merging into it:
+      # any field you leave out is cleared. Two of those change delivery silently — an
+      # omitted `timezone` reverts the schedule to UTC, and an omitted `is_default` can
+      # leave the topic with no default schedule, which is what recipients who have not
+      # chosen one fall back to. Restate every field you want to keep.
       sig do
         params(
           frequency: Courier::DigestFrequency::OrSymbol,

data/rbi/courier/models/topic_digest_schedule_response.rbi

@@ -13,6 +13,14 @@ module Courier
 
       # The schedule's identifier, assigned by the server. This is the value the
       # `/digests/schedules/{schedule_id}` endpoints are keyed by.
+      #
+      # Two formats are in circulation and only one is safe to drop into a URL.
+      # Schedules created through the API are `sch_01m26xfcn3endt3nxy4e2kx2rh` and need
+      # no encoding. Schedules created in the Preferences Editor before that format are
+      # `sch/{uuid}` and contain a literal `/`, so they must be URL-encoded as
+      # `sch%2F{uuid}` — unencoded, the path does not match the route and the response
+      # is a bare `404` that reads like a broken endpoint. Existing ids are never
+      # migrated.
       sig { returns(String) }
       attr_accessor :schedule_id
 
@@ -110,6 +118,14 @@ module Courier
       def self.new(
         # The schedule's identifier, assigned by the server. This is the value the
         # `/digests/schedules/{schedule_id}` endpoints are keyed by.
+        #
+        # Two formats are in circulation and only one is safe to drop into a URL.
+        # Schedules created through the API are `sch_01m26xfcn3endt3nxy4e2kx2rh` and need
+        # no encoding. Schedules created in the Preferences Editor before that format are
+        # `sch/{uuid}` and contain a literal `/`, so they must be URL-encoded as
+        # `sch%2F{uuid}` — unencoded, the path does not match the route and the response
+        # is a bare `404` that reads like a broken endpoint. Existing ids are never
+        # migrated.
         schedule_id:,
         # ISO-8601 timestamp of when the schedule was created.
         created: nil,

data/rbi/courier/models/users/topic_preference.rbi

@@ -40,8 +40,13 @@ module Courier
 
         # The digest schedule this recipient is on for the topic. Omitted rather than null
         # when they have not chosen one, in which case the topic's default schedule
-        # applies. Ids come from the topic's digest configuration or from
-        # `GET /digests/schedules`.
+        # applies. Ids come from the topic's digest configuration, returned on any read of
+        # the topic.
+        #
+        # Also omitted when the schedule they chose has since been deleted or disabled:
+        # the recipient is on the topic's default from that point on, which is how a send
+        # already resolves it, so the field reports what would actually be used rather
+        # than a dead id.
         sig { returns(T.nilable(String)) }
         attr_reader :digest_schedule_id
 
@@ -103,8 +108,13 @@ module Courier
           custom_routing: nil,
           # The digest schedule this recipient is on for the topic. Omitted rather than null
           # when they have not chosen one, in which case the topic's default schedule
-          # applies. Ids come from the topic's digest configuration or from
-          # `GET /digests/schedules`.
+          # applies. Ids come from the topic's digest configuration, returned on any read of
+          # the topic.
+          #
+          # Also omitted when the schedule they chose has since been deleted or disabled:
+          # the recipient is on the topic's default from that point on, which is how a send
+          # already resolves it, so the field reports what would actually be used rather
+          # than a dead id.
           digest_schedule_id: nil,
           # Whether the user has chosen specific delivery channels for this topic (listed in
           # custom_routing) rather than the topic's default routing.

data/rbi/courier/models/workspace_preference_topic_create_request.rbi

@@ -40,18 +40,32 @@ module Courier
       sig { returns(T.nilable(String)) }
       attr_accessor :description
 
-      # A topic's digest configuration: the template that renders it, the cadences it
-      # delivers on, and how collected events are retained.
+      # A topic's digest, as supplied when the topic itself is created: the template
+      # that renders it, the cadences it delivers on, and how collected events are
+      # retained.
+      #
+      # Identical to `TopicDigestRequest`, which a replace uses, except that `schedules`
+      # is required — a topic being created has no stored schedules for an absent key to
+      # leave alone.
       #
       # Send `null` for the whole object to turn a digest off, which unlinks the
       # template and removes its schedules. There is no `enabled` flag, and
       # `schedules: []` is rejected, because both states are un-deliverable rather than
       # merely off.
-      sig { returns(T.nilable(Courier::TopicDigestRequest)) }
+      sig do
+        returns(
+          T.nilable(Courier::WorkspacePreferenceTopicCreateRequest::Digest)
+        )
+      end
       attr_reader :digest
 
       sig do
-        params(digest: T.nilable(Courier::TopicDigestRequest::OrHash)).void
+        params(
+          digest:
+            T.nilable(
+              Courier::WorkspacePreferenceTopicCreateRequest::Digest::OrHash
+            )
+        ).void
       end
       attr_writer :digest
 
@@ -82,7 +96,10 @@ module Courier
               ]
             ),
           description: T.nilable(String),
-          digest: T.nilable(Courier::TopicDigestRequest::OrHash),
+          digest:
+            T.nilable(
+              Courier::WorkspacePreferenceTopicCreateRequest::Digest::OrHash
+            ),
           include_unsubscribe_header: T.nilable(T::Boolean),
           routing_options:
             T.nilable(T::Array[Courier::ChannelClassification::OrSymbol]),
@@ -99,8 +116,13 @@ module Courier
         allowed_preferences: nil,
         # Optional description shown under the topic on the hosted preferences page.
         description: nil,
-        # A topic's digest configuration: the template that renders it, the cadences it
-        # delivers on, and how collected events are retained.
+        # A topic's digest, as supplied when the topic itself is created: the template
+        # that renders it, the cadences it delivers on, and how collected events are
+        # retained.
+        #
+        # Identical to `TopicDigestRequest`, which a replace uses, except that `schedules`
+        # is required — a topic being created has no stored schedules for an absent key to
+        # leave alone.
         #
         # Send `null` for the whole object to turn a digest off, which unlinks the
         # template and removes its schedules. There is no `enabled` flag, and
@@ -129,7 +151,8 @@ module Courier
                 ]
               ),
             description: T.nilable(String),
-            digest: T.nilable(Courier::TopicDigestRequest),
+            digest:
+              T.nilable(Courier::WorkspacePreferenceTopicCreateRequest::Digest),
             include_unsubscribe_header: T.nilable(T::Boolean),
             routing_options:
               T.nilable(T::Array[Courier::ChannelClassification::OrSymbol]),
@@ -214,6 +237,130 @@ module Courier
         def self.values
         end
       end
+
+      class Digest < Courier::Internal::Type::BaseModel
+        OrHash =
+          T.type_alias do
+            T.any(
+              Courier::WorkspacePreferenceTopicCreateRequest::Digest,
+              Courier::Internal::AnyHash
+            )
+          end
+
+        # The cadences this digest delivers on.
+        #
+        # The array replaces the stored schedules wholesale, so a schedule you leave out
+        # of it is deleted along with its delivery rule. Omit the key entirely to leave
+        # the stored schedules untouched — useful for changing `template_id` or
+        # `categories` without restating every schedule.
+        #
+        # A digest must end up with at least one schedule, because one with none collects
+        # events into an instance that can never fire. So sending `[]` is always a `400`,
+        # and so is omitting the key on a topic that has no schedules stored yet.
+        #
+        # On **create** the key is required outright: a topic being created has nothing
+        # stored to leave alone, and the topic row is written before its digest, so
+        # rejecting it any later would leave the topic behind and let a retry duplicate
+        # it.
+        sig { returns(T::Array[Courier::TopicDigestScheduleRequest]) }
+        attr_accessor :schedules
+
+        # The notification template that renders the digest. A digest with no template
+        # collects nothing, so this is required.
+        sig { returns(String) }
+        attr_accessor :template_id
+
+        # Optional audience the digest is scoped to.
+        sig { returns(T.nilable(String)) }
+        attr_reader :audience_id
+
+        sig { params(audience_id: String).void }
+        attr_writer :audience_id
+
+        # Retention rules per category key. Defaults to a single `digest` category
+        # retaining `FIRST`.
+        sig { returns(T.nilable(T::Array[Courier::TopicDigestCategory])) }
+        attr_reader :categories
+
+        sig do
+          params(
+            categories: T::Array[Courier::TopicDigestCategory::OrHash]
+          ).void
+        end
+        attr_writer :categories
+
+        # Whether to deliver the digest even when nothing was collected.
+        sig { returns(T.nilable(T::Boolean)) }
+        attr_reader :trigger_empty
+
+        sig { params(trigger_empty: T::Boolean).void }
+        attr_writer :trigger_empty
+
+        # A topic's digest, as supplied when the topic itself is created: the template
+        # that renders it, the cadences it delivers on, and how collected events are
+        # retained.
+        #
+        # Identical to `TopicDigestRequest`, which a replace uses, except that `schedules`
+        # is required — a topic being created has no stored schedules for an absent key to
+        # leave alone.
+        #
+        # Send `null` for the whole object to turn a digest off, which unlinks the
+        # template and removes its schedules. There is no `enabled` flag, and
+        # `schedules: []` is rejected, because both states are un-deliverable rather than
+        # merely off.
+        sig do
+          params(
+            schedules: T::Array[Courier::TopicDigestScheduleRequest::OrHash],
+            template_id: String,
+            audience_id: String,
+            categories: T::Array[Courier::TopicDigestCategory::OrHash],
+            trigger_empty: T::Boolean
+          ).returns(T.attached_class)
+        end
+        def self.new(
+          # The cadences this digest delivers on.
+          #
+          # The array replaces the stored schedules wholesale, so a schedule you leave out
+          # of it is deleted along with its delivery rule. Omit the key entirely to leave
+          # the stored schedules untouched — useful for changing `template_id` or
+          # `categories` without restating every schedule.
+          #
+          # A digest must end up with at least one schedule, because one with none collects
+          # events into an instance that can never fire. So sending `[]` is always a `400`,
+          # and so is omitting the key on a topic that has no schedules stored yet.
+          #
+          # On **create** the key is required outright: a topic being created has nothing
+          # stored to leave alone, and the topic row is written before its digest, so
+          # rejecting it any later would leave the topic behind and let a retry duplicate
+          # it.
+          schedules:,
+          # The notification template that renders the digest. A digest with no template
+          # collects nothing, so this is required.
+          template_id:,
+          # Optional audience the digest is scoped to.
+          audience_id: nil,
+          # Retention rules per category key. Defaults to a single `digest` category
+          # retaining `FIRST`.
+          categories: nil,
+          # Whether to deliver the digest even when nothing was collected.
+          trigger_empty: nil
+        )
+        end
+
+        sig do
+          override.returns(
+            {
+              schedules: T::Array[Courier::TopicDigestScheduleRequest],
+              template_id: String,
+              audience_id: String,
+              categories: T::Array[Courier::TopicDigestCategory],
+              trigger_empty: T::Boolean
+            }
+          )
+        end
+        def to_hash
+        end
+      end
     end
   end
 end

data/rbi/courier/resources/journeys.rbi

@@ -41,6 +41,7 @@ module Courier
                 Courier::JourneyNode::JourneyBranchNode::OrHash
               )
             ],
+          cancelation_token: String,
           enabled: T::Boolean,
           state: Courier::JourneyState::OrSymbol,
           idempotency_key: String,
@@ -53,6 +54,12 @@ module Courier
         name:,
         # Body param
         nodes:,
+        # Body param: Cancelation token stored on the journey definition. It tags every
+        # run the journey creates so that `POST /journeys/cancel` can later cancel those
+        # runs by token. Accepts a templated string such as `order-{{data.order_id}}`,
+        # which is resolved per run when the journey is invoked. On a replace, omitting
+        # this field preserves any existing token and sending a value replaces it.
+        cancelation_token: nil,
         # Body param
         enabled: nil,
         # Body param: Lifecycle state of a journey.
@@ -283,6 +290,7 @@ module Courier
                 Courier::JourneyNode::JourneyBranchNode::OrHash
               )
             ],
+          cancelation_token: String,
           enabled: T::Boolean,
           state: Courier::JourneyState::OrSymbol,
           request_options: Courier::RequestOptions::OrHash
@@ -293,6 +301,12 @@ module Courier
         template_id,
         name:,
         nodes:,
+        # Cancelation token stored on the journey definition. It tags every run the
+        # journey creates so that `POST /journeys/cancel` can later cancel those runs by
+        # token. Accepts a templated string such as `order-{{data.order_id}}`, which is
+        # resolved per run when the journey is invoked. On a replace, omitting this field
+        # preserves any existing token and sending a value replaces it.
+        cancelation_token: nil,
         enabled: nil,
         # Lifecycle state of a journey.
         state: nil,

data/rbi/courier/resources/workspace_preferences/topics.rbi

@@ -19,7 +19,10 @@ module Courier
                 ]
               ),
             description: T.nilable(String),
-            digest: T.nilable(Courier::TopicDigestRequest::OrHash),
+            digest:
+              T.nilable(
+                Courier::WorkspacePreferenceTopicCreateRequest::Digest::OrHash
+              ),
             include_unsubscribe_header: T.nilable(T::Boolean),
             routing_options:
               T.nilable(T::Array[Courier::ChannelClassification::OrSymbol]),
@@ -43,8 +46,13 @@ module Courier
           # Body param: Optional description shown under the topic on the hosted preferences
           # page.
           description: nil,
-          # Body param: A topic's digest configuration: the template that renders it, the
-          # cadences it delivers on, and how collected events are retained.
+          # Body param: A topic's digest, as supplied when the topic itself is created: the
+          # template that renders it, the cadences it delivers on, and how collected events
+          # are retained.
+          #
+          # Identical to `TopicDigestRequest`, which a replace uses, except that `schedules`
+          # is required — a topic being created has no stored schedules for an absent key to
+          # leave alone.
           #
           # Send `null` for the whole object to turn a digest off, which unlinks the
           # template and removes its schedules. There is no `enabled` flag, and

data/sig/courier/models/create_journey_request.rbs

@@ -4,6 +4,7 @@ module Courier
       {
         name: String,
         nodes: ::Array[Courier::Models::journey_node],
+        cancelation_token: String,
         enabled: bool,
         state: Courier::Models::journey_state
       }
@@ -13,6 +14,10 @@ module Courier
 
       attr_accessor nodes: ::Array[Courier::Models::journey_node]
 
+      attr_reader cancelation_token: String?
+
+      def cancelation_token=: (String) -> String
+
       attr_reader enabled: bool?
 
       def enabled=: (bool) -> bool
@@ -26,6 +31,7 @@ module Courier
       def initialize: (
         name: String,
         nodes: ::Array[Courier::Models::journey_node],
+        ?cancelation_token: String,
         ?enabled: bool,
         ?state: Courier::Models::journey_state
       ) -> void
@@ -33,6 +39,7 @@ module Courier
       def to_hash: -> {
         name: String,
         nodes: ::Array[Courier::Models::journey_node],
+        cancelation_token: String,
         enabled: bool,
         state: Courier::Models::journey_state
       }

data/sig/courier/models/elemental_action_node.rbs

@@ -97,12 +97,14 @@ module Courier
         style: Courier::Models::ElementalActionNode::style?
       }
 
-      type style = :button | :link
+      type style = :button | :secondary | :tertiary | :link
 
       module Style
         extend Courier::Internal::Type::Enum
 
         BUTTON: :button
+        SECONDARY: :secondary
+        TERTIARY: :tertiary
         LINK: :link
 
         def self?.values: -> ::Array[Courier::Models::ElementalActionNode::style]

data/sig/courier/models/journey_response.rbs

@@ -3,6 +3,7 @@ module Courier
     type journey_response =
       {
         id: String,
+        cancelation_token: String?,
         created: Integer?,
         creator: String?,
         enabled: bool,
@@ -17,6 +18,8 @@ module Courier
     class JourneyResponse < Courier::Internal::Type::BaseModel
       attr_accessor id: String
 
+      attr_accessor cancelation_token: String?
+
       attr_accessor created: Integer?
 
       attr_accessor creator: String?
@@ -37,6 +40,7 @@ module Courier
 
       def initialize: (
         id: String,
+        cancelation_token: String?,
         created: Integer?,
         creator: String?,
         enabled: bool,
@@ -50,6 +54,7 @@ module Courier
 
       def to_hash: -> {
         id: String,
+        cancelation_token: String?,
         created: Integer?,
         creator: String?,
         enabled: bool,

data/sig/courier/models/topic_digest_request.rbs

@@ -2,16 +2,14 @@ module Courier
   module Models
     type topic_digest_request =
       {
-        schedules: ::Array[Courier::TopicDigestScheduleRequest],
         template_id: String,
         audience_id: String,
         categories: ::Array[Courier::TopicDigestCategory],
+        schedules: ::Array[Courier::TopicDigestScheduleRequest],
         trigger_empty: bool
       }
 
     class TopicDigestRequest < Courier::Internal::Type::BaseModel
-      attr_accessor schedules: ::Array[Courier::TopicDigestScheduleRequest]
-
       attr_accessor template_id: String
 
       attr_reader audience_id: String?
@@ -24,23 +22,29 @@ module Courier
         ::Array[Courier::TopicDigestCategory]
       ) -> ::Array[Courier::TopicDigestCategory]
 
+      attr_reader schedules: ::Array[Courier::TopicDigestScheduleRequest]?
+
+      def schedules=: (
+        ::Array[Courier::TopicDigestScheduleRequest]
+      ) -> ::Array[Courier::TopicDigestScheduleRequest]
+
       attr_reader trigger_empty: bool?
 
       def trigger_empty=: (bool) -> bool
 
       def initialize: (
-        schedules: ::Array[Courier::TopicDigestScheduleRequest],
         template_id: String,
         ?audience_id: String,
         ?categories: ::Array[Courier::TopicDigestCategory],
+        ?schedules: ::Array[Courier::TopicDigestScheduleRequest],
         ?trigger_empty: bool
       ) -> void
 
       def to_hash: -> {
-        schedules: ::Array[Courier::TopicDigestScheduleRequest],
         template_id: String,
         audience_id: String,
         categories: ::Array[Courier::TopicDigestCategory],
+        schedules: ::Array[Courier::TopicDigestScheduleRequest],
         trigger_empty: bool
       }
     end

data/sig/courier/models/workspace_preference_topic_create_request.rbs

@@ -6,7 +6,7 @@ module Courier
         name: String,
         allowed_preferences: ::Array[Courier::Models::WorkspacePreferenceTopicCreateRequest::allowed_preference]?,
         description: String?,
-        digest: Courier::TopicDigestRequest?,
+        digest: Courier::WorkspacePreferenceTopicCreateRequest::Digest?,
         include_unsubscribe_header: bool?,
         routing_options: ::Array[Courier::Models::channel_classification]?,
         topic_data: ::Hash[Symbol, top]?
@@ -21,7 +21,7 @@ module Courier
 
       attr_accessor description: String?
 
-      attr_accessor digest: Courier::TopicDigestRequest?
+      attr_accessor digest: Courier::WorkspacePreferenceTopicCreateRequest::Digest?
 
       attr_accessor include_unsubscribe_header: bool?
 
@@ -34,7 +34,7 @@ module Courier
         name: String,
         ?allowed_preferences: ::Array[Courier::Models::WorkspacePreferenceTopicCreateRequest::allowed_preference]?,
         ?description: String?,
-        ?digest: Courier::TopicDigestRequest?,
+        ?digest: Courier::WorkspacePreferenceTopicCreateRequest::Digest?,
         ?include_unsubscribe_header: bool?,
         ?routing_options: ::Array[Courier::Models::channel_classification]?,
         ?topic_data: ::Hash[Symbol, top]?
@@ -45,7 +45,7 @@ module Courier
         name: String,
         allowed_preferences: ::Array[Courier::Models::WorkspacePreferenceTopicCreateRequest::allowed_preference]?,
         description: String?,
-        digest: Courier::TopicDigestRequest?,
+        digest: Courier::WorkspacePreferenceTopicCreateRequest::Digest?,
         include_unsubscribe_header: bool?,
         routing_options: ::Array[Courier::Models::channel_classification]?,
         topic_data: ::Hash[Symbol, top]?
@@ -73,6 +73,51 @@ module Courier
 
         def self?.values: -> ::Array[Courier::Models::WorkspacePreferenceTopicCreateRequest::allowed_preference]
       end
+
+      type digest =
+        {
+          schedules: ::Array[Courier::TopicDigestScheduleRequest],
+          template_id: String,
+          audience_id: String,
+          categories: ::Array[Courier::TopicDigestCategory],
+          trigger_empty: bool
+        }
+
+      class Digest < Courier::Internal::Type::BaseModel
+        attr_accessor schedules: ::Array[Courier::TopicDigestScheduleRequest]
+
+        attr_accessor template_id: String
+
+        attr_reader audience_id: String?
+
+        def audience_id=: (String) -> String
+
+        attr_reader categories: ::Array[Courier::TopicDigestCategory]?
+
+        def categories=: (
+          ::Array[Courier::TopicDigestCategory]
+        ) -> ::Array[Courier::TopicDigestCategory]
+
+        attr_reader trigger_empty: bool?
+
+        def trigger_empty=: (bool) -> bool
+
+        def initialize: (
+          schedules: ::Array[Courier::TopicDigestScheduleRequest],
+          template_id: String,
+          ?audience_id: String,
+          ?categories: ::Array[Courier::TopicDigestCategory],
+          ?trigger_empty: bool
+        ) -> void
+
+        def to_hash: -> {
+          schedules: ::Array[Courier::TopicDigestScheduleRequest],
+          template_id: String,
+          audience_id: String,
+          categories: ::Array[Courier::TopicDigestCategory],
+          trigger_empty: bool
+        }
+      end
     end
   end
 end