trycourier 6.6.0 → 6.7.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 72f51e60173a98ce2cc1e4b6d3c0613e82f18de751e7ea855ed2418808cac4d9
-  data.tar.gz: 5a10110fea4a9c3b8c5acaf39d169a902c7a8566e4ddfb49933eaed3600c0924
+  metadata.gz: c665c6475e9af26f67197651f5599bac614c384d86086dd974ed410005ab407d
+  data.tar.gz: 4e037944cf9a6cd6346aa647a5f097e3cd04a5be4676b1b0bc392bed497be990
 SHA512:
-  metadata.gz: 7940121c65ecbb1ef483b5f8594cdde2a3b08f1c93d22c04ebbd829b2989030e6d3bc43359b98196fc749a4c21fe8d54cb2a3355f37e057996da472e807751eb
-  data.tar.gz: 569ff793ab8fa5d18202278cd38630cb6556c391f3097e2931c938afb87e2a6c163c4b061bab684dc4a18d668843d0b36a7ebbb5b11699976483d49e466d5370
+  metadata.gz: 244553b3412e7041264a0ceb8e355e89fcf67b8f00098cfab876e00408c39089e4e6bf0031693e7ab49749e43e74ac4fbf6b7ca16f8e91c00f63bc061157725e
+  data.tar.gz: 60ce9fc7ae0c32289b97208cad86e4c97c0ca4b44f6d7f0d10967e72ea4922bc19104a95a46c6c7ee146372a57ba9a255b773a26f9d2bad505f3e905c84d66e9

data/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## [6.7.0](https://github.com/trycourier/courier-ruby/compare/v6.6.0...v6.7.0) (2026-09-22)
+
+
+### Features
+
+* **api:** add cancelation_token to journey create, replace, and get ([#158](https://github.com/trycourier/courier-ruby/issues/158)) ([ec47880](https://github.com/trycourier/courier-ruby/commit/ec47880a79aaefde00dedcbdc84527ff234a99f2))
+
+
+### Documentation
+
+* **api:** correct the digest schedule contract, and make `schedules` optional ([#156](https://github.com/trycourier/courier-ruby/issues/156)) ([8578d77](https://github.com/trycourier/courier-ruby/commit/8578d77848275105865c1b29b799f2cc6621987e))
+
 ## [6.6.0](https://github.com/trycourier/courier-ruby/compare/v6.5.0...v6.6.0) (2026-09-15)
 
 

data/README.md

@@ -9,7 +9,7 @@ Add the gem to your `Gemfile`:
 <!-- x-release-please-start-version -->
 
 ```ruby
-gem "trycourier", "~> 6.6.0"
+gem "trycourier", "~> 6.7.0"
 ```
 
 <!-- x-release-please-end -->

data/lib/courier/models/create_journey_request.rb

@@ -13,6 +13,16 @@ module Courier
       #   @return [Array<Courier::Models::JourneyAPIInvokeTriggerNode, Courier::Models::JourneySegmentTriggerNode, Courier::Models::JourneyAudienceTriggerNode, Courier::Models::JourneyWebhookTriggerNode, Courier::Models::JourneySendNode, Courier::Models::JourneyDelayDurationNode, Courier::Models::JourneyDelayUntilNode, Courier::Models::JourneyFetchGetDeleteNode, Courier::Models::JourneyFetchPostPutNode, Courier::Models::JourneyAINode, Courier::Models::JourneyThrottleStaticNode, Courier::Models::JourneyThrottleDynamicNode, Courier::Models::JourneyNode::JourneyBatchNode, Courier::Models::JourneyNode::JourneyAddToDigestNode, Courier::Models::JourneyExitNode, Courier::Models::JourneyNode::JourneyBranchNode>]
       required :nodes, -> { Courier::Internal::Type::ArrayOf[union: Courier::JourneyNode] }
 
+      # @!attribute cancelation_token
+      #   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.
+      #
+      #   @return [String, nil]
+      optional :cancelation_token, String
+
       # @!attribute enabled
       #
       #   @return [Boolean, nil]
@@ -24,13 +34,18 @@ module Courier
       #   @return [Symbol, Courier::Models::JourneyState, nil]
       optional :state, enum: -> { Courier::JourneyState }
 
-      # @!method initialize(name:, nodes:, enabled: nil, state: nil)
+      # @!method initialize(name:, nodes:, cancelation_token: nil, enabled: nil, state: nil)
+      #   Some parameter documentations has been truncated, see
+      #   {Courier::Models::CreateJourneyRequest} for more details.
+      #
       #   Request body for creating a journey.
       #
       #   @param name [String]
       #
       #   @param nodes [Array<Courier::Models::JourneyAPIInvokeTriggerNode, Courier::Models::JourneySegmentTriggerNode, Courier::Models::JourneyAudienceTriggerNode, Courier::Models::JourneyWebhookTriggerNode, Courier::Models::JourneySendNode, Courier::Models::JourneyDelayDurationNode, Courier::Models::JourneyDelayUntilNode, Courier::Models::JourneyFetchGetDeleteNode, Courier::Models::JourneyFetchPostPutNode, Courier::Models::JourneyAINode, Courier::Models::JourneyThrottleStaticNode, Courier::Models::JourneyThrottleDynamicNode, Courier::Models::JourneyNode::JourneyBatchNode, Courier::Models::JourneyNode::JourneyAddToDigestNode, Courier::Models::JourneyExitNode, Courier::Models::JourneyNode::JourneyBranchNode>]
       #
+      #   @param cancelation_token [String] Cancelation token stored on the journey definition. It tags every run the journe
+      #
       #   @param enabled [Boolean]
       #
       #   @param state [Symbol, Courier::Models::JourneyState] Lifecycle state of a journey.

data/lib/courier/models/journey_response.rb

@@ -9,6 +9,14 @@ module Courier
       #   @return [String]
       required :id, String
 
+      # @!attribute cancelation_token
+      #   The journey cancelation token, or null when none is set. A token authored in the
+      #   dashboard is returned in its raw templated form, such as
+      #   `order-{{data.order_id}}`, so it can be read back and asserted.
+      #
+      #   @return [String, nil]
+      required :cancelation_token, String, nil?: true
+
       # @!attribute created
       #
       #   @return [Integer, nil]
@@ -55,11 +63,16 @@ module Courier
       #   @return [String, nil]
       required :updater, String, nil?: true
 
-      # @!method initialize(id:, created:, creator:, enabled:, name:, nodes:, published:, state:, updated:, updater:)
+      # @!method initialize(id:, cancelation_token:, created:, creator:, enabled:, name:, nodes:, published:, state:, updated:, updater:)
+      #   Some parameter documentations has been truncated, see
+      #   {Courier::Models::JourneyResponse} for more details.
+      #
       #   A journey, with its current draft or published nodes and metadata.
       #
       #   @param id [String]
       #
+      #   @param cancelation_token [String, nil] The journey cancelation token, or null when none is set. A token authored in the
+      #
       #   @param created [Integer, nil]
       #
       #   @param creator [String, nil]

data/lib/courier/models/topic_digest_request.rb

@@ -3,14 +3,6 @@
 module Courier
   module Models
     class TopicDigestRequest < Courier::Internal::Type::BaseModel
-      # @!attribute schedules
-      #   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`.
-      #
-      #   @return [Array<Courier::Models::TopicDigestScheduleRequest>]
-      required :schedules, -> { Courier::Internal::Type::ArrayOf[Courier::TopicDigestScheduleRequest] }
-
       # @!attribute template_id
       #   The notification template that renders the digest. A digest with no template
       #   collects nothing, so this is required.
@@ -31,13 +23,33 @@ module Courier
       #   @return [Array<Courier::Models::TopicDigestCategory>, nil]
       optional :categories, -> { Courier::Internal::Type::ArrayOf[Courier::TopicDigestCategory] }
 
+      # @!attribute schedules
+      #   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.
+      #
+      #   @return [Array<Courier::Models::TopicDigestScheduleRequest>, nil]
+      optional :schedules, -> { Courier::Internal::Type::ArrayOf[Courier::TopicDigestScheduleRequest] }
+
       # @!attribute trigger_empty
       #   Whether to deliver the digest even when nothing was collected.
       #
       #   @return [Boolean, nil]
       optional :trigger_empty, Courier::Internal::Type::Boolean
 
-      # @!method initialize(schedules:, template_id:, audience_id: nil, categories: nil, trigger_empty: nil)
+      # @!method initialize(template_id:, audience_id: nil, categories: nil, schedules: nil, trigger_empty: nil)
       #   Some parameter documentations has been truncated, see
       #   {Courier::Models::TopicDigestRequest} for more details.
       #
@@ -49,14 +61,14 @@ module Courier
       #   `schedules: []` is rejected, because both states are un-deliverable rather than
       #   merely off.
       #
-      #   @param schedules [Array<Courier::Models::TopicDigestScheduleRequest>] The cadences this digest delivers on. At least one is required: a digest with no
-      #
       #   @param template_id [String] The notification template that renders the digest. A digest with no template col
       #
       #   @param audience_id [String] Optional audience the digest is scoped to.
       #
       #   @param categories [Array<Courier::Models::TopicDigestCategory>] Retention rules per category key. Defaults to a single `digest` category retaini
       #
+      #   @param schedules [Array<Courier::Models::TopicDigestScheduleRequest>] The cadences this digest delivers on.
+      #
       #   @param trigger_empty [Boolean] Whether to deliver the digest even when nothing was collected.
     end
   end

data/lib/courier/models/topic_digest_schedule_request.rb

@@ -71,6 +71,12 @@ module Courier
       #   `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.
+      #
       #   @param frequency [Symbol, Courier::Models::DigestFrequency] How often a digest is delivered. `instant` delivers immediately without batching
       #
       #   @param day_of_month [Integer] Required when `frequency` is `monthly`.

data/lib/courier/models/topic_digest_schedule_response.rb

@@ -7,6 +7,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.
+      #
       #   @return [String]
       required :schedule_id, String
 

data/lib/courier/models/users/topic_preference.rb

@@ -44,8 +44,13 @@ module Courier
         # @!attribute digest_schedule_id
         #   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.
         #
         #   @return [String, nil]
         optional :digest_schedule_id, String

data/lib/courier/models/workspace_preference_topic_create_request.rb

@@ -33,16 +33,21 @@ module Courier
       optional :description, String, nil?: true
 
       # @!attribute digest
-      #   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.
       #
-      #   @return [Courier::Models::TopicDigestRequest, nil]
-      optional :digest, -> { Courier::TopicDigestRequest }, nil?: true
+      #   @return [Courier::Models::WorkspacePreferenceTopicCreateRequest::Digest, nil]
+      optional :digest, -> { Courier::WorkspacePreferenceTopicCreateRequest::Digest }, nil?: true
 
       # @!attribute include_unsubscribe_header
       #   Whether to include a list-unsubscribe header on emails for this topic.
@@ -78,7 +83,7 @@ module Courier
       #
       #   @param description [String, nil] Optional description shown under the topic on the hosted preferences page.
       #
-      #   @param digest [Courier::Models::TopicDigestRequest, nil] A topic's digest configuration: the template that renders it, the cadences it de
+      #   @param digest [Courier::Models::WorkspacePreferenceTopicCreateRequest::Digest, nil] A topic's digest, as supplied when the topic itself is created: the template tha
       #
       #   @param include_unsubscribe_header [Boolean, nil] Whether to include a list-unsubscribe header on emails for this topic.
       #
@@ -110,6 +115,83 @@ module Courier
         # @!method self.values
         #   @return [Array<Symbol>]
       end
+
+      # @see Courier::Models::WorkspacePreferenceTopicCreateRequest#digest
+      class Digest < Courier::Internal::Type::BaseModel
+        # @!attribute schedules
+        #   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.
+        #
+        #   @return [Array<Courier::Models::TopicDigestScheduleRequest>]
+        required :schedules, -> { Courier::Internal::Type::ArrayOf[Courier::TopicDigestScheduleRequest] }
+
+        # @!attribute template_id
+        #   The notification template that renders the digest. A digest with no template
+        #   collects nothing, so this is required.
+        #
+        #   @return [String]
+        required :template_id, String
+
+        # @!attribute audience_id
+        #   Optional audience the digest is scoped to.
+        #
+        #   @return [String, nil]
+        optional :audience_id, String
+
+        # @!attribute categories
+        #   Retention rules per category key. Defaults to a single `digest` category
+        #   retaining `FIRST`.
+        #
+        #   @return [Array<Courier::Models::TopicDigestCategory>, nil]
+        optional :categories, -> { Courier::Internal::Type::ArrayOf[Courier::TopicDigestCategory] }
+
+        # @!attribute trigger_empty
+        #   Whether to deliver the digest even when nothing was collected.
+        #
+        #   @return [Boolean, nil]
+        optional :trigger_empty, Courier::Internal::Type::Boolean
+
+        # @!method initialize(schedules:, template_id:, audience_id: nil, categories: nil, trigger_empty: nil)
+        #   Some parameter documentations has been truncated, see
+        #   {Courier::Models::WorkspacePreferenceTopicCreateRequest::Digest} for more
+        #   details.
+        #
+        #   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.
+        #
+        #   @param schedules [Array<Courier::Models::TopicDigestScheduleRequest>] The cadences this digest delivers on.
+        #
+        #   @param template_id [String] The notification template that renders the digest. A digest with no template col
+        #
+        #   @param audience_id [String] Optional audience the digest is scoped to.
+        #
+        #   @param categories [Array<Courier::Models::TopicDigestCategory>] Retention rules per category key. Defaults to a single `digest` category retaini
+        #
+        #   @param trigger_empty [Boolean] Whether to deliver the digest even when nothing was collected.
+      end
     end
   end
 end

data/lib/courier/resources/journeys.rb

@@ -21,12 +21,14 @@ module Courier
       # Creates a journey from a set of nodes, in draft state unless you pass a
       # published state. Send nodes cannot be included until their templates exist.
       #
-      # @overload create(name:, nodes:, enabled: nil, state: nil, idempotency_key: nil, x_idempotency_expiration: nil, request_options: {})
+      # @overload create(name:, nodes:, cancelation_token: nil, enabled: nil, state: nil, idempotency_key: nil, x_idempotency_expiration: nil, request_options: {})
       #
       # @param name [String] Body param
       #
       # @param nodes [Array<Courier::Models::JourneyAPIInvokeTriggerNode, Courier::Models::JourneySegmentTriggerNode, Courier::Models::JourneyAudienceTriggerNode, Courier::Models::JourneyWebhookTriggerNode, Courier::Models::JourneySendNode, Courier::Models::JourneyDelayDurationNode, Courier::Models::JourneyDelayUntilNode, Courier::Models::JourneyFetchGetDeleteNode, Courier::Models::JourneyFetchPostPutNode, Courier::Models::JourneyAINode, Courier::Models::JourneyThrottleStaticNode, Courier::Models::JourneyThrottleDynamicNode, Courier::Models::JourneyNode::JourneyBatchNode, Courier::Models::JourneyNode::JourneyAddToDigestNode, Courier::Models::JourneyExitNode, Courier::Models::JourneyNode::JourneyBranchNode>] Body param
       #
+      # @param cancelation_token [String] Body param: Cancelation token stored on the journey definition. It tags every ru
+      #
       # @param enabled [Boolean] Body param
       #
       # @param state [Symbol, Courier::Models::JourneyState] Body param: Lifecycle state of a journey.
@@ -259,10 +261,13 @@ module Courier
         )
       end
 
+      # Some parameter documentations has been truncated, see
+      # {Courier::Models::JourneyReplaceParams} for more details.
+      #
       # Replaces a journey's working draft, leaving the published version live until you
       # publish. Reach for this when editing a journey already running.
       #
-      # @overload replace(template_id, name:, nodes:, enabled: nil, state: nil, request_options: {})
+      # @overload replace(template_id, name:, nodes:, cancelation_token: nil, enabled: nil, state: nil, request_options: {})
       #
       # @param template_id [String] Journey id
       #
@@ -270,6 +275,8 @@ module Courier
       #
       # @param nodes [Array<Courier::Models::JourneyAPIInvokeTriggerNode, Courier::Models::JourneySegmentTriggerNode, Courier::Models::JourneyAudienceTriggerNode, Courier::Models::JourneyWebhookTriggerNode, Courier::Models::JourneySendNode, Courier::Models::JourneyDelayDurationNode, Courier::Models::JourneyDelayUntilNode, Courier::Models::JourneyFetchGetDeleteNode, Courier::Models::JourneyFetchPostPutNode, Courier::Models::JourneyAINode, Courier::Models::JourneyThrottleStaticNode, Courier::Models::JourneyThrottleDynamicNode, Courier::Models::JourneyNode::JourneyBatchNode, Courier::Models::JourneyNode::JourneyAddToDigestNode, Courier::Models::JourneyExitNode, Courier::Models::JourneyNode::JourneyBranchNode>]
       #
+      # @param cancelation_token [String] Cancelation token stored on the journey definition. It tags every run the journe
+      #
       # @param enabled [Boolean]
       #
       # @param state [Symbol, Courier::Models::JourneyState] Lifecycle state of a journey.

data/lib/courier/resources/workspace_preferences/topics.rb

@@ -22,7 +22,7 @@ module Courier
         #
         # @param description [String, nil] Body param: Optional description shown under the topic on the hosted preferences
         #
-        # @param digest [Courier::Models::TopicDigestRequest, nil] Body param: A topic's digest configuration: the template that renders it, the ca
+        # @param digest [Courier::Models::WorkspacePreferenceTopicCreateRequest::Digest, nil] Body param: A topic's digest, as supplied when the topic itself is created: the
         #
         # @param include_unsubscribe_header [Boolean, nil] Body param: Whether to include a list-unsubscribe header on emails for this topi
         #

data/lib/courier/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module Courier
-  VERSION = "6.6.0"
+  VERSION = "6.7.0"
 end

data/rbi/courier/models/create_journey_request.rbi

@@ -37,6 +37,17 @@ module Courier
       end
       attr_accessor :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.
+      sig { returns(T.nilable(String)) }
+      attr_reader :cancelation_token
+
+      sig { params(cancelation_token: String).void }
+      attr_writer :cancelation_token
+
       sig { returns(T.nilable(T::Boolean)) }
       attr_reader :enabled
 
@@ -75,6 +86,7 @@ module Courier
                 Courier::JourneyNode::JourneyBranchNode::OrHash
               )
             ],
+          cancelation_token: String,
           enabled: T::Boolean,
           state: Courier::JourneyState::OrSymbol
         ).returns(T.attached_class)
@@ -82,6 +94,12 @@ module Courier
       def self.new(
         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
@@ -113,6 +131,7 @@ module Courier
                   Courier::JourneyNode::JourneyBranchNode
                 )
               ],
+            cancelation_token: String,
             enabled: T::Boolean,
             state: Courier::JourneyState::OrSymbol
           }

data/rbi/courier/models/journey_response.rbi

@@ -11,6 +11,12 @@ module Courier
       sig { returns(String) }
       attr_accessor :id
 
+      # The journey cancelation token, or null when none is set. A token authored in the
+      # dashboard is returned in its raw templated form, such as
+      # `order-{{data.order_id}}`, so it can be read back and asserted.
+      sig { returns(T.nilable(String)) }
+      attr_accessor :cancelation_token
+
       sig { returns(T.nilable(Integer)) }
       attr_accessor :created
 
@@ -43,6 +49,7 @@ module Courier
       sig do
         params(
           id: String,
+          cancelation_token: T.nilable(String),
           created: T.nilable(Integer),
           creator: T.nilable(String),
           enabled: T::Boolean,
@@ -76,6 +83,10 @@ module Courier
       end
       def self.new(
         id:,
+        # The journey cancelation token, or null when none is set. A token authored in the
+        # dashboard is returned in its raw templated form, such as
+        # `order-{{data.order_id}}`, so it can be read back and asserted.
+        cancelation_token:,
         created:,
         creator:,
         enabled:,
@@ -93,6 +104,7 @@ module Courier
         override.returns(
           {
             id: String,
+            cancelation_token: T.nilable(String),
             created: T.nilable(Integer),
             creator: T.nilable(String),
             enabled: T::Boolean,

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/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

data/sig/courier/resources/journeys.rbs

@@ -8,6 +8,7 @@ module Courier
       def create: (
         name: String,
         nodes: ::Array[Courier::Models::journey_node],
+        ?cancelation_token: String,
         ?enabled: bool,
         ?state: Courier::Models::journey_state,
         ?idempotency_key: String,
@@ -66,6 +67,7 @@ module Courier
         String template_id,
         name: String,
         nodes: ::Array[Courier::Models::journey_node],
+        ?cancelation_token: String,
         ?enabled: bool,
         ?state: Courier::Models::journey_state,
         ?request_options: Courier::request_opts

data/sig/courier/resources/workspace_preferences/topics.rbs

@@ -8,7 +8,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]?,

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: trycourier
 version: !ruby/object:Gem::Version
-  version: 6.6.0
+  version: 6.7.0
 platform: ruby
 authors:
 - Courier
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-09-15 00:00:00.000000000 Z
+date: 2026-09-23 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: cgi