zyphr 0.1.43 → 0.1.44

data/spec/api/auth_user_directory_api_spec.rb

@@ -44,6 +44,18 @@ describe 'AuthUserDirectoryApi' do
     end
   end
 
+  # unit tests for get_end_user_auth_methods
+  # Get an end user's sign-in methods (server-side admin)
+  # Secret-key-scoped, aggregate view of the sign-in methods configured for a single end user within the authenticating application. Reports whether the user has a password, which OAuth providers are linked, whether MFA is enabled, whether email/phone are verified, and how many passkeys are registered — everything a customer admin needs to build a \"sign-in methods\" screen. Scoped to the application — a caller can never read a user belonging to another application. 
+  # @param user_id 
+  # @param [Hash] opts the optional parameters
+  # @return [GetEndUserAuthMethods200Response]
+  describe 'get_end_user_auth_methods test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   # unit tests for get_end_user_by_email
   # Look up an end user by email (server-side admin)
   # Secret-key-scoped lookup of a single end user by email address within the authenticating application. Scoped to the application — never resolves a user from another application. Does not return the password hash. 

data/spec/models/application_self_response_spec.rb

@@ -0,0 +1,42 @@
+=begin
+#Zyphr API
+
+#Zyphr is a multi-channel notification platform that enables developers to send emails, push notifications, SMS, and in-app messages through a unified API.  ## Authentication  All API requests require authentication using an API key. Include your API key in the `X-API-Key` header:  ``` X-API-Key: zy_live_xxxxxxxxxxxx ```  API keys can be created in the Zyphr Dashboard. Use `zy_test_*` keys for testing and `zy_live_*` keys for production.  ## Rate Limiting  The API implements rate limiting to ensure fair usage. Rate limit information is included in response headers:  - `X-RateLimit-Limit`: Maximum requests per window - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: Unix timestamp when the window resets  ## Account Sending Status  Every authenticated response carries the account's current sending state so you can surface it in your own tooling without a separate call:  - `X-Account-Sending-Status`: `active`, `throttled`, or `frozen` - `X-Account-Sending-Status-Reason`: human-readable reason (present only when the status is `throttled` or `frozen`)  This header is informational and non-blocking on non-send endpoints (reads, billing, and deliverability stay available). Send-capable endpoints additionally enforce the state: a frozen account receives `403 account_frozen` and a throttled account receives `429 account_throttled`, both with the reason in the error message.  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@zyphr.dev
+Generated by: https://openapi-generator.tech
+Generator version: 7.12.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Zyphr::ApplicationSelfResponse
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zyphr::ApplicationSelfResponse do
+  let(:instance) { Zyphr::ApplicationSelfResponse.new }
+
+  describe 'test an instance of ApplicationSelfResponse' do
+    it 'should create an instance of ApplicationSelfResponse' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zyphr::ApplicationSelfResponse)
+    end
+  end
+
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "meta"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/application_self_spec.rb

@@ -0,0 +1,62 @@
+=begin
+#Zyphr API
+
+#Zyphr is a multi-channel notification platform that enables developers to send emails, push notifications, SMS, and in-app messages through a unified API.  ## Authentication  All API requests require authentication using an API key. Include your API key in the `X-API-Key` header:  ``` X-API-Key: zy_live_xxxxxxxxxxxx ```  API keys can be created in the Zyphr Dashboard. Use `zy_test_*` keys for testing and `zy_live_*` keys for production.  ## Rate Limiting  The API implements rate limiting to ensure fair usage. Rate limit information is included in response headers:  - `X-RateLimit-Limit`: Maximum requests per window - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: Unix timestamp when the window resets  ## Account Sending Status  Every authenticated response carries the account's current sending state so you can surface it in your own tooling without a separate call:  - `X-Account-Sending-Status`: `active`, `throttled`, or `frozen` - `X-Account-Sending-Status-Reason`: human-readable reason (present only when the status is `throttled` or `frozen`)  This header is informational and non-blocking on non-send endpoints (reads, billing, and deliverability stay available). Send-capable endpoints additionally enforce the state: a frozen account receives `403 account_frozen` and a throttled account receives `429 account_throttled`, both with the reason in the error message.  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@zyphr.dev
+Generated by: https://openapi-generator.tech
+Generator version: 7.12.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Zyphr::ApplicationSelf
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zyphr::ApplicationSelf do
+  let(:instance) { Zyphr::ApplicationSelf.new }
+
+  describe 'test an instance of ApplicationSelf' do
+    it 'should create an instance of ApplicationSelf' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zyphr::ApplicationSelf)
+    end
+  end
+
+  describe 'test attribute "id"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "name"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "environment"' 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', ["test", "live"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.environment = value }.not_to raise_error
+      # end
+    end
+  end
+
+  describe 'test attribute "signing_algorithm"' 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', ["HS256", "RS256", "ES256"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.signing_algorithm = value }.not_to raise_error
+      # end
+    end
+  end
+
+end

data/spec/models/auth_methods_spec.rb

@@ -0,0 +1,66 @@
+=begin
+#Zyphr API
+
+#Zyphr is a multi-channel notification platform that enables developers to send emails, push notifications, SMS, and in-app messages through a unified API.  ## Authentication  All API requests require authentication using an API key. Include your API key in the `X-API-Key` header:  ``` X-API-Key: zy_live_xxxxxxxxxxxx ```  API keys can be created in the Zyphr Dashboard. Use `zy_test_*` keys for testing and `zy_live_*` keys for production.  ## Rate Limiting  The API implements rate limiting to ensure fair usage. Rate limit information is included in response headers:  - `X-RateLimit-Limit`: Maximum requests per window - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: Unix timestamp when the window resets  ## Account Sending Status  Every authenticated response carries the account's current sending state so you can surface it in your own tooling without a separate call:  - `X-Account-Sending-Status`: `active`, `throttled`, or `frozen` - `X-Account-Sending-Status-Reason`: human-readable reason (present only when the status is `throttled` or `frozen`)  This header is informational and non-blocking on non-send endpoints (reads, billing, and deliverability stay available). Send-capable endpoints additionally enforce the state: a frozen account receives `403 account_frozen` and a throttled account receives `429 account_throttled`, both with the reason in the error message.  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@zyphr.dev
+Generated by: https://openapi-generator.tech
+Generator version: 7.12.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Zyphr::AuthMethods
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zyphr::AuthMethods do
+  let(:instance) { Zyphr::AuthMethods.new }
+
+  describe 'test an instance of AuthMethods' do
+    it 'should create an instance of AuthMethods' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zyphr::AuthMethods)
+    end
+  end
+
+  describe 'test attribute "has_password"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "oauth_providers"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "mfa_enabled"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "email_verified"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "phone_verified"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "passkeys"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/models/get_end_user_auth_methods200_response_spec.rb

@@ -0,0 +1,42 @@
+=begin
+#Zyphr API
+
+#Zyphr is a multi-channel notification platform that enables developers to send emails, push notifications, SMS, and in-app messages through a unified API.  ## Authentication  All API requests require authentication using an API key. Include your API key in the `X-API-Key` header:  ``` X-API-Key: zy_live_xxxxxxxxxxxx ```  API keys can be created in the Zyphr Dashboard. Use `zy_test_*` keys for testing and `zy_live_*` keys for production.  ## Rate Limiting  The API implements rate limiting to ensure fair usage. Rate limit information is included in response headers:  - `X-RateLimit-Limit`: Maximum requests per window - `X-RateLimit-Remaining`: Remaining requests in current window - `X-RateLimit-Reset`: Unix timestamp when the window resets  ## Account Sending Status  Every authenticated response carries the account's current sending state so you can surface it in your own tooling without a separate call:  - `X-Account-Sending-Status`: `active`, `throttled`, or `frozen` - `X-Account-Sending-Status-Reason`: human-readable reason (present only when the status is `throttled` or `frozen`)  This header is informational and non-blocking on non-send endpoints (reads, billing, and deliverability stay available). Send-capable endpoints additionally enforce the state: a frozen account receives `403 account_frozen` and a throttled account receives `429 account_throttled`, both with the reason in the error message.  ## Errors  All errors follow a consistent format:  ```json {   \"error\": {     \"code\": \"error_code\",     \"message\": \"Human readable message\",     \"details\": {}   },   \"meta\": {     \"request_id\": \"req_xxxx\"   } } ```
+
+The version of the OpenAPI document: 1.0.0
+Contact: support@zyphr.dev
+Generated by: https://openapi-generator.tech
+Generator version: 7.12.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Zyphr::GetEndUserAuthMethods200Response
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zyphr::GetEndUserAuthMethods200Response do
+  let(:instance) { Zyphr::GetEndUserAuthMethods200Response.new }
+
+  describe 'test an instance of GetEndUserAuthMethods200Response' do
+    it 'should create an instance of GetEndUserAuthMethods200Response' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zyphr::GetEndUserAuthMethods200Response)
+    end
+  end
+
+  describe 'test attribute "data"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "meta"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/zyphr.gemspec

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

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: zyphr
 version: !ruby/object:Gem::Version
-  version: 0.1.43
+  version: 0.1.44
 platform: ruby
 authors:
 - Zyphr
@@ -98,6 +98,9 @@ files:
 - docs/ApiError.md
 - docs/ApiErrorError.md
 - docs/ApiErrorMeta.md
+- docs/ApplicationSelf.md
+- docs/ApplicationSelfResponse.md
+- docs/AuthApplicationApi.md
 - docs/AuthEmailOTPApi.md
 - docs/AuthEmailTemplate.md
 - docs/AuthEmailTemplateDefault.md
@@ -124,6 +127,7 @@ files:
 - docs/AuthLoginResultMfaChallenge.md
 - docs/AuthMFAApi.md
 - docs/AuthMagicLinksApi.md
+- docs/AuthMethods.md
 - docs/AuthOAuthApi.md
 - docs/AuthOrganizationsApi.md
 - docs/AuthPasswordResetApi.md
@@ -230,6 +234,7 @@ files:
 - docs/GenerateWaaSPortalToken201Response.md
 - docs/GetDomain200Response.md
 - docs/GetDomain200ResponseMeta.md
+- docs/GetEndUserAuthMethods200Response.md
 - docs/GetEndUserById200Response.md
 - docs/GetEndUserClaims200Response.md
 - docs/GetEndUserClaims200ResponseData.md
@@ -616,6 +621,7 @@ files:
 - docs/WorkflowsApi.md
 - git_push.sh
 - lib/zyphr.rb
+- lib/zyphr/api/auth_application_api.rb
 - lib/zyphr/api/auth_email_otp_api.rb
 - lib/zyphr/api/auth_email_templates_api.rb
 - lib/zyphr/api/auth_email_verification_api.rb
@@ -665,6 +671,8 @@ files:
 - lib/zyphr/models/api_error.rb
 - lib/zyphr/models/api_error_error.rb
 - lib/zyphr/models/api_error_meta.rb
+- lib/zyphr/models/application_self.rb
+- lib/zyphr/models/application_self_response.rb
 - lib/zyphr/models/auth_email_template.rb
 - lib/zyphr/models/auth_email_template_default.rb
 - lib/zyphr/models/auth_email_template_default_response.rb
@@ -685,6 +693,7 @@ files:
 - lib/zyphr/models/auth_login_response.rb
 - lib/zyphr/models/auth_login_result.rb
 - lib/zyphr/models/auth_login_result_mfa_challenge.rb
+- lib/zyphr/models/auth_methods.rb
 - lib/zyphr/models/auth_result.rb
 - lib/zyphr/models/auth_result_response.rb
 - lib/zyphr/models/auth_session.rb
@@ -778,6 +787,7 @@ files:
 - lib/zyphr/models/generate_waa_s_portal_token201_response.rb
 - lib/zyphr/models/get_domain200_response.rb
 - lib/zyphr/models/get_domain200_response_meta.rb
+- lib/zyphr/models/get_end_user_auth_methods200_response.rb
 - lib/zyphr/models/get_end_user_by_id200_response.rb
 - lib/zyphr/models/get_end_user_claims200_response.rb
 - lib/zyphr/models/get_end_user_claims200_response_data.rb
@@ -1146,6 +1156,7 @@ files:
 - lib/zyphr/models/workflow_step_execution_status.rb
 - lib/zyphr/models/workflow_step_type.rb
 - lib/zyphr/version.rb
+- spec/api/auth_application_api_spec.rb
 - spec/api/auth_email_otp_api_spec.rb
 - spec/api/auth_email_templates_api_spec.rb
 - spec/api/auth_email_verification_api_spec.rb
@@ -1192,6 +1203,8 @@ files:
 - spec/models/api_error_error_spec.rb
 - spec/models/api_error_meta_spec.rb
 - spec/models/api_error_spec.rb
+- spec/models/application_self_response_spec.rb
+- spec/models/application_self_spec.rb
 - spec/models/auth_email_template_default_response_spec.rb
 - spec/models/auth_email_template_default_spec.rb
 - spec/models/auth_email_template_delete_response_data_spec.rb
@@ -1212,6 +1225,7 @@ files:
 - spec/models/auth_login_response_spec.rb
 - spec/models/auth_login_result_mfa_challenge_spec.rb
 - spec/models/auth_login_result_spec.rb
+- spec/models/auth_methods_spec.rb
 - spec/models/auth_result_response_spec.rb
 - spec/models/auth_result_spec.rb
 - spec/models/auth_session_spec.rb
@@ -1305,6 +1319,7 @@ files:
 - spec/models/generate_waa_s_portal_token201_response_spec.rb
 - spec/models/get_domain200_response_meta_spec.rb
 - spec/models/get_domain200_response_spec.rb
+- spec/models/get_end_user_auth_methods200_response_spec.rb
 - spec/models/get_end_user_by_id200_response_spec.rb
 - spec/models/get_end_user_claims200_response_data_spec.rb
 - spec/models/get_end_user_claims200_response_spec.rb
@@ -1721,6 +1736,7 @@ test_files:
 - spec/api/auth_mfa_api_spec.rb
 - spec/api/push_api_spec.rb
 - spec/api/auth_email_templates_api_spec.rb
+- spec/api/auth_application_api_spec.rb
 - spec/api/waa_s_portal_api_spec.rb
 - spec/api/auth_organizations_api_spec.rb
 - spec/api/sms_api_spec.rb
@@ -1834,6 +1850,7 @@ test_files:
 - spec/models/sms_detail_response_spec.rb
 - spec/models/withdraw_subscriber_consent_request_spec.rb
 - spec/models/invite_end_user200_response_data_spec.rb
+- spec/models/get_end_user_auth_methods200_response_spec.rb
 - spec/models/get_waa_s_endpoint_circuit200_response_spec.rb
 - spec/models/verify_email_otp_registration_request_spec.rb
 - spec/models/send_email_response_data_spec.rb
@@ -2081,6 +2098,7 @@ test_files:
 - spec/models/inbound_email_list_response_meta_spec.rb
 - spec/models/create_topic_request_spec.rb
 - spec/models/webhook_delivery_retry_response_spec.rb
+- spec/models/application_self_response_spec.rb
 - spec/models/sms_list_response_spec.rb
 - spec/models/update_end_user_by_application_request_spec.rb
 - spec/models/auth_login_result_spec.rb
@@ -2098,6 +2116,7 @@ test_files:
 - spec/models/o_auth_tokens_refresh_response_spec.rb
 - spec/models/delete_result_spec.rb
 - spec/models/sms_batch_result_summary_spec.rb
+- spec/models/application_self_spec.rb
 - spec/models/reset_password_request_spec.rb
 - spec/models/webhook_region_spec.rb
 - spec/models/set_preferences_request_spec.rb
@@ -2211,6 +2230,7 @@ test_files:
 - spec/models/batch_publish_waa_s_events201_response_spec.rb
 - spec/models/push_topic_subscribe_data_spec.rb
 - spec/models/auth_result_response_spec.rb
+- spec/models/auth_methods_spec.rb
 - spec/models/auth_email_template_response_spec.rb
 - spec/models/waa_s_portal_token_request_theme_spec.rb
 - spec/models/send_template_test_email202_response_data_spec.rb