zyphr 0.1.46 → 0.1.48

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 77f15d268b6cde06333ab1c4730afbd297f5f5eab479921e5e43b65704f78f8a
-  data.tar.gz: b1018ca20b1b79c6e8eb6dbab973e046175ee9e3950bbb96fa734e608f12893a
+  metadata.gz: 2b5e4efe27496d1705a00bd68c41d08cd989868b1c6adcfd121020427d564cd3
+  data.tar.gz: 1609dd6b8ef90f34d467818f1a118c9e098b08f1eef3f9214998ca3b954fec5f
 SHA512:
-  metadata.gz: b918028f5a8ebf48f6573951e75b17fdee5f96ea7943416e9240f513be9f3b9204fee331e52ca355d82eb9ad111198ba5cf53bbcd7fe02641ef924d04e0aab24
-  data.tar.gz: 0e714ffc0bddf9ca677f420e2a97a4e4f1ae63612dd4935a417c0fb0a0f3c0cfb7a407a577a0b43a41819bdd9a012ae28259ce4cf138488b10e4d086abaf5f13
+  metadata.gz: b7aa153c3b521e7655329023a0e94435384ebbeff2d50bcf1a45d21b19445b4e41e20219059f5317e522b9b7804053cddadad1ec1b7def398abb16e38e6d4482
+  data.tar.gz: 3775721a2b16919ebc96ea0e792eeadb40eb14c24b8380f6e8ada9eb3a2d0c29472bb4df0a109ea369e3a7189e03424438cb7ddb035b283993059ae1f485faa6

data/docs/AuthSessionsApi.md

@@ -87,7 +87,7 @@ This endpoint does not need any parameter.
 
 Refresh access token
 
-Refresh access token using a refresh token. Accepts optional custom_claims to update JWT claims (if not provided, preserves existing claims).
+Refresh an end-user access token using a refresh token. Authenticated with the publishable application key (`X-Application-Key`) — no application secret is required, so client-side apps (browser / mobile) can refresh directly. The refresh token is the credential: it must be valid, unexpired, unrevoked, and issued for this application. Refresh tokens are single-use — each refresh returns a NEW refresh token and invalidates the one you presented, so persist the new token before the next refresh. Accepts optional custom_claims to update JWT claims (if not provided, current stored claims are preserved).
 
 ### Examples
 

data/docs/EmailMessage.md

@@ -9,6 +9,7 @@
 | **to** | [**EmailAddress**](EmailAddress.md) |  | [optional] |
 | **subject** | **String** |  | [optional] |
 | **status** | **String** |  | [optional] |
+| **status_reason** | **String** | Why the message is in its current status, when applicable. For a `suppressed` row this is the suppression reason (e.g. `recipient_not_allowlisted` when blocked by the auth application's test_recipients allowlist). Null for normal sends.  | [optional] |
 | **tags** | **Array<String>** |  | [optional] |
 | **queued_at** | **Time** |  | [optional] |
 | **sent_at** | **Time** |  | [optional] |
@@ -29,6 +30,7 @@ instance = Zyphr::EmailMessage.new(
   to: null,
   subject: null,
   status: null,
+  status_reason: null,
   tags: null,
   queued_at: null,
   sent_at: null,

data/lib/zyphr/api/auth_sessions_api.rb

@@ -77,7 +77,7 @@ module Zyphr
     end
 
     # Refresh access token
-    # Refresh access token using a refresh token. Accepts optional custom_claims to update JWT claims (if not provided, preserves existing claims).
+    # Refresh an end-user access token using a refresh token. Authenticated with the publishable application key (`X-Application-Key`) — no application secret is required, so client-side apps (browser / mobile) can refresh directly. The refresh token is the credential: it must be valid, unexpired, unrevoked, and issued for this application. Refresh tokens are single-use — each refresh returns a NEW refresh token and invalidates the one you presented, so persist the new token before the next refresh. Accepts optional custom_claims to update JWT claims (if not provided, current stored claims are preserved).
     # @param refresh_session_request [RefreshSessionRequest] 
     # @param [Hash] opts the optional parameters
     # @return [RefreshTokenResponse]
@@ -87,7 +87,7 @@ module Zyphr
     end
 
     # Refresh access token
-    # Refresh access token using a refresh token. Accepts optional custom_claims to update JWT claims (if not provided, preserves existing claims).
+    # Refresh an end-user access token using a refresh token. Authenticated with the publishable application key (`X-Application-Key`) — no application secret is required, so client-side apps (browser / mobile) can refresh directly. The refresh token is the credential: it must be valid, unexpired, unrevoked, and issued for this application. Refresh tokens are single-use — each refresh returns a NEW refresh token and invalidates the one you presented, so persist the new token before the next refresh. Accepts optional custom_claims to update JWT claims (if not provided, current stored claims are preserved).
     # @param refresh_session_request [RefreshSessionRequest] 
     # @param [Hash] opts the optional parameters
     # @return [Array<(RefreshTokenResponse, Integer, Hash)>] RefreshTokenResponse data, response status code and response headers

data/lib/zyphr/api/emails_api.rb

@@ -233,7 +233,7 @@ module Zyphr
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: EmailsApi.list_emails ...'
       end
-      allowable_values = ["pending", "queued", "sent", "delivered", "failed", "bounced", "rejected"]
+      allowable_values = ["pending", "queued", "sent", "delivered", "failed", "bounced", "rejected", "suppressed"]
       if @api_client.config.client_side_validation && opts[:'status'] && !allowable_values.include?(opts[:'status'])
         fail ArgumentError, "invalid value for \"status\", must be one of #{allowable_values}"
       end

data/lib/zyphr/models/email_message.rb

@@ -25,6 +25,9 @@ module Zyphr
 
     attr_accessor :status
 
+    # Why the message is in its current status, when applicable. For a `suppressed` row this is the suppression reason (e.g. `recipient_not_allowlisted` when blocked by the auth application's test_recipients allowlist). Null for normal sends. 
+    attr_accessor :status_reason
+
     attr_accessor :tags
 
     attr_accessor :queued_at
@@ -71,6 +74,7 @@ module Zyphr
         :'to' => :'to',
         :'subject' => :'subject',
         :'status' => :'status',
+        :'status_reason' => :'status_reason',
         :'tags' => :'tags',
         :'queued_at' => :'queued_at',
         :'sent_at' => :'sent_at',
@@ -100,6 +104,7 @@ module Zyphr
         :'to' => :'EmailAddress',
         :'subject' => :'String',
         :'status' => :'String',
+        :'status_reason' => :'String',
         :'tags' => :'Array<String>',
         :'queued_at' => :'Time',
         :'sent_at' => :'Time',
@@ -114,6 +119,7 @@ module Zyphr
     # List of attributes with nullable: true
     def self.openapi_nullable
       Set.new([
+        :'status_reason',
         :'sent_at',
         :'delivered_at',
         :'bounced_at',
@@ -158,6 +164,10 @@ module Zyphr
         self.status = attributes[:'status']
       end
 
+      if attributes.key?(:'status_reason')
+        self.status_reason = attributes[:'status_reason']
+      end
+
       if attributes.key?(:'tags')
         if (value = attributes[:'tags']).is_a?(Array)
           self.tags = value
@@ -205,7 +215,7 @@ module Zyphr
     # @return true if the model is valid
     def valid?
       warn '[DEPRECATED] the `valid?` method is obsolete'
-      status_validator = EnumAttributeValidator.new('String', ["pending", "queued", "sent", "delivered", "failed", "bounced", "rejected"])
+      status_validator = EnumAttributeValidator.new('String', ["pending", "queued", "sent", "delivered", "failed", "bounced", "rejected", "suppressed"])
       return false unless status_validator.valid?(@status)
       true
     end
@@ -213,7 +223,7 @@ module Zyphr
     # Custom attribute writer method checking allowed values (enum).
     # @param [Object] status Object to be assigned
     def status=(status)
-      validator = EnumAttributeValidator.new('String', ["pending", "queued", "sent", "delivered", "failed", "bounced", "rejected"])
+      validator = EnumAttributeValidator.new('String', ["pending", "queued", "sent", "delivered", "failed", "bounced", "rejected", "suppressed"])
       unless validator.valid?(status)
         fail ArgumentError, "invalid value for \"status\", must be one of #{validator.allowable_values}."
       end
@@ -230,6 +240,7 @@ module Zyphr
           to == o.to &&
           subject == o.subject &&
           status == o.status &&
+          status_reason == o.status_reason &&
           tags == o.tags &&
           queued_at == o.queued_at &&
           sent_at == o.sent_at &&
@@ -249,7 +260,7 @@ module Zyphr
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [id, from, to, subject, status, tags, queued_at, sent_at, delivered_at, bounced_at, opened_at, clicked_at, created_at].hash
+      [id, from, to, subject, status, status_reason, tags, queued_at, sent_at, delivered_at, bounced_at, opened_at, clicked_at, created_at].hash
     end
 
     # Builds the object from hash

data/spec/api/auth_sessions_api_spec.rb

@@ -45,7 +45,7 @@ describe 'AuthSessionsApi' do
 
   # unit tests for refresh_end_user_token
   # Refresh access token
-  # Refresh access token using a refresh token. Accepts optional custom_claims to update JWT claims (if not provided, preserves existing claims).
+  # Refresh an end-user access token using a refresh token. Authenticated with the publishable application key (`X-Application-Key`) — no application secret is required, so client-side apps (browser / mobile) can refresh directly. The refresh token is the credential: it must be valid, unexpired, unrevoked, and issued for this application. Refresh tokens are single-use — each refresh returns a NEW refresh token and invalidates the one you presented, so persist the new token before the next refresh. Accepts optional custom_claims to update JWT claims (if not provided, current stored claims are preserved).
   # @param refresh_session_request 
   # @param [Hash] opts the optional parameters
   # @return [RefreshTokenResponse]

data/spec/models/email_message_spec.rb

@@ -54,13 +54,19 @@ describe Zyphr::EmailMessage do
   describe 'test attribute "status"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
-      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["pending", "queued", "sent", "delivered", "failed", "bounced", "rejected"])
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["pending", "queued", "sent", "delivered", "failed", "bounced", "rejected", "suppressed"])
       # validator.allowable_values.each do |value|
       #   expect { instance.status = value }.not_to raise_error
       # end
     end
   end
 
+  describe 'test attribute "status_reason"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "tags"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/zyphr.gemspec

@@ -17,7 +17,7 @@ require "zyphr/version"
 
 Gem::Specification.new do |s|
   s.name        = "zyphr"
-  s.version = '0.1.46'
+  s.version = '0.1.48'
   s.platform    = Gem::Platform::RUBY
   s.authors     = ["Zyphr"]
   s.email       = ["support@zyphr.dev"]

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: zyphr
 version: !ruby/object:Gem::Version
-  version: 0.1.46
+  version: 0.1.48
 platform: ruby
 authors:
 - Zyphr
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-07-31 00:00:00.000000000 Z
+date: 2026-08-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: faraday