zernio-sdk 0.0.810 → 0.0.812

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: efee100b19cee0588302d4a9f5c0fc7e1de393694cfdff7b9c718d4cb34c19d5
-  data.tar.gz: 33c0cebb565cb9ce81e7d14f65abe09a2e26049b757a487e81d92e94bda9d213
+  metadata.gz: 94c1b8d8762e8ac96f0dcd54ac2a3fba405f9aea07fa6537bb49cd4cb20011e3
+  data.tar.gz: 6674637bdcfaa210cd85c62a3d83bb8ef0dae4d666fc73773c0f17d3c3b29439
 SHA512:
-  metadata.gz: fe2f79eddbe62681e4143cdc567bebc0b470773eb4e4dab23549a16d4e4fff61ed4938c35635c8aafa9e28c09971044685b0cc49c68a4fe47a0ad4d2e05cdcce
-  data.tar.gz: d1e2f6ee12c5a05375f21997ae41b7d2030371a48fa925d077043be223fe4e0a2dadf3a02fe6ca7205e93a898c74a3daa1d03aba59b679fcd08d0417661919f5
+  metadata.gz: eda431e1568c572d5ded0d20d0d40b9f35d7f005bcf85110e3ee753ec508fab1f181268c600c4eeaf03f2935525aabf06fbc90c2344a0ad9b7f6de438d08d503
+  data.tar.gz: de31319ad6da45239d98df7bffbc50c86223786d2aa8b8c7c771bc2175c16ad738c8d79df32a36a6edf3b5bf0892d70db233b78ad4f2383e7d145ade82ebc0fe

data/docs/CreateContactRequest.md

@@ -12,7 +12,7 @@
 | **is_subscribed** | **Boolean** |  | [optional][default to true] |
 | **notes** | **String** |  | [optional] |
 | **account_id** | **String** | Optional. Creates a channel if provided with platform + platformIdentifier | [optional] |
-| **platform** | **String** |  | [optional] |
+| **platform** | **String** | Channel platform. Only the enum values support contact channels; any other platform is rejected with code platform_not_supported. | [optional] |
 | **platform_identifier** | **String** |  | [optional] |
 | **display_identifier** | **String** |  | [optional] |
 

data/docs/CreateInboxConversationRequest.md

@@ -13,7 +13,7 @@
 | **category** | **String** | WhatsApp only (Meta Direct Send). Combined with message and without templateName, starts the conversation with a business-initiated UTILITY message and no pre-approved template; Meta matches or auto-creates a template asynchronously. The WhatsApp Business Account must be eligible for Direct Send, otherwise the send fails with an error telling you to use an approved message template instead. Cannot be combined with templateName (templates are already categorized at creation). Utility messages only; marketing content is not allowed under this category. Accepted on the JSON body only, not on multipart requests. | [optional] |
 | **link_preview** | **Boolean** | WhatsApp only. Set false to send the Direct Send (category: 'utility') text message without a link-preview thumbnail for the first URL in the text. Defaults to true, which is how every WhatsApp text has been sent to date. Does not apply to template sends. Accepted on the JSON body only, not on multipart requests. | [optional][default to true] |
 | **template_language** | **String** | WhatsApp only. Template language code (e.g. en_US). | [optional] |
-| **template_params** | **Array<String>** | WhatsApp only. Template variable values as one flat array, in the order the variables appear across the whole template: text-header variables first, then body variables, then one value per dynamic URL button (in button order). Works with positional placeholders ({{1}}, {{2}}, ...) and with named placeholders ({{name}}, {{company}} - how Meta Business Manager creates templates), where values fill the named slots in order of appearance. Example - a body with {{1}}, {{2}} plus a URL button https://example.com/{{1}} takes three values: [body1, body2, buttonSuffix]. Media headers (image, video, document) are filled automatically from the approved template and take no value here (use headerMedia to override the header asset per send). Buttons that are not dynamic-URL buttons (copy-code, flow) take no value here either; use templateButtonParams. | [optional] |
+| **template_params** | **Array<String>** | WhatsApp only. Template variable values as one flat array, in the order the variables appear across the whole template: text-header variables first, then body variables, then one value per dynamic URL button (in button order). Works with positional placeholders ({{1}}, {{2}}, ...) and with named placeholders ({{name}}, {{company}} - how Meta Business Manager creates templates), where values fill the named slots in order of appearance. Example - a body with {{1}}, {{2}} plus a URL button https://example.com/{{1}} takes three values: [body1, body2, buttonSuffix]. For positional templates the list must cover every slot: supplying fewer values than the template's header + body + dynamic URL-button count is rejected with a 400 (code INVALID_TEMPLATE_PARAMS) naming the expected split, rather than delivering a template whose button URL was filled from the wrong value. A dynamic URL button covered by templateButtonParams needs no value here unless another uncovered dynamic URL button follows it, since the override applies after slot numbering. Media headers (image, video, document) are filled automatically from the approved template and take no value here (use headerMedia to override the header asset per send). Buttons that are not dynamic-URL buttons (copy-code, flow) take no value here either; use templateButtonParams. | [optional] |
 | **template_button_params** | [**Array<CreateInboxConversationRequestTemplateButtonParamsInner>**](CreateInboxConversationRequestTemplateButtonParamsInner.md) | WhatsApp only. Values for template buttons that carry one at send time, each addressed by the button's position in the approved template. This is the only way to send a copy-code button's payload (a Pix payment code, a coupon) or a flow token, because templateParams is a flat array of text variables and covers dynamic URL buttons only. Supplying a button here overrides whatever templateParams would have derived for that same index, so the send never carries one button twice; repeating an index within this array is rejected with 400. Each index must name a button of the matching kind on the approved template, which is also checked before the send and returns 400 (INVALID_TEMPLATE_BUTTON_PARAM) rather than a Meta rejection. | [optional] |
 | **header_media** | [**CreateInboxConversationRequestHeaderMedia**](CreateInboxConversationRequestHeaderMedia.md) |  | [optional] |
 | **header_location** | [**CreateInboxConversationRequestHeaderLocation**](CreateInboxConversationRequestHeaderLocation.md) |  | [optional] |

data/lib/zernio-sdk/api/contacts_api.rb

@@ -379,7 +379,7 @@ module Zernio
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: ContactsApi.list_contacts ...'
       end
-      allowable_values = ["instagram", "facebook", "telegram", "twitter", "bluesky", "reddit", "whatsapp"]
+      allowable_values = ["instagram", "facebook", "telegram", "twitter", "bluesky", "reddit", "whatsapp", "slack"]
       if @api_client.config.client_side_validation && opts[:'platform'] && !allowable_values.include?(opts[:'platform'])
         fail ArgumentError, "invalid value for \"platform\", must be one of #{allowable_values}"
       end

data/lib/zernio-sdk/models/create_contact_request.rb

@@ -32,12 +32,35 @@ module Zernio
     # Optional. Creates a channel if provided with platform + platformIdentifier
     attr_accessor :account_id
 
+    # Channel platform. Only the enum values support contact channels; any other platform is rejected with code platform_not_supported.
     attr_accessor :platform
 
     attr_accessor :platform_identifier
 
     attr_accessor :display_identifier
 
+    class EnumAttributeValidator
+      attr_reader :datatype
+      attr_reader :allowable_values
+
+      def initialize(datatype, allowable_values)
+        @allowable_values = allowable_values.map do |value|
+          case datatype.to_s
+          when /Integer/i
+            value.to_i
+          when /Float/i
+            value.to_f
+          else
+            value
+          end
+        end
+      end
+
+      def valid?(value)
+        !value || allowable_values.include?(value)
+      end
+    end
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
@@ -179,6 +202,8 @@ module Zernio
       warn '[DEPRECATED] the `valid?` method is obsolete'
       return false if @profile_id.nil?
       return false if @name.nil?
+      platform_validator = EnumAttributeValidator.new('String', ["instagram", "facebook", "telegram", "twitter", "bluesky", "reddit", "whatsapp", "slack"])
+      return false unless platform_validator.valid?(@platform)
       true
     end
 
@@ -202,6 +227,16 @@ module Zernio
       @name = name
     end
 
+    # Custom attribute writer method checking allowed values (enum).
+    # @param [Object] platform Object to be assigned
+    def platform=(platform)
+      validator = EnumAttributeValidator.new('String', ["instagram", "facebook", "telegram", "twitter", "bluesky", "reddit", "whatsapp", "slack"])
+      unless validator.valid?(platform)
+        fail ArgumentError, "invalid value for \"platform\", must be one of #{validator.allowable_values}."
+      end
+      @platform = platform
+    end
+
     # Checks equality by comparing each attribute.
     # @param [Object] Object to be compared
     def ==(o)

data/lib/zernio-sdk/models/create_inbox_conversation_request.rb

@@ -42,7 +42,7 @@ module Zernio
     # WhatsApp only. Template language code (e.g. en_US).
     attr_accessor :template_language
 
-    # WhatsApp only. Template variable values as one flat array, in the order the variables appear across the whole template: text-header variables first, then body variables, then one value per dynamic URL button (in button order). Works with positional placeholders ({{1}}, {{2}}, ...) and with named placeholders ({{name}}, {{company}} - how Meta Business Manager creates templates), where values fill the named slots in order of appearance. Example - a body with {{1}}, {{2}} plus a URL button https://example.com/{{1}} takes three values: [body1, body2, buttonSuffix]. Media headers (image, video, document) are filled automatically from the approved template and take no value here (use headerMedia to override the header asset per send). Buttons that are not dynamic-URL buttons (copy-code, flow) take no value here either; use templateButtonParams.
+    # WhatsApp only. Template variable values as one flat array, in the order the variables appear across the whole template: text-header variables first, then body variables, then one value per dynamic URL button (in button order). Works with positional placeholders ({{1}}, {{2}}, ...) and with named placeholders ({{name}}, {{company}} - how Meta Business Manager creates templates), where values fill the named slots in order of appearance. Example - a body with {{1}}, {{2}} plus a URL button https://example.com/{{1}} takes three values: [body1, body2, buttonSuffix]. For positional templates the list must cover every slot: supplying fewer values than the template's header + body + dynamic URL-button count is rejected with a 400 (code INVALID_TEMPLATE_PARAMS) naming the expected split, rather than delivering a template whose button URL was filled from the wrong value. A dynamic URL button covered by templateButtonParams needs no value here unless another uncovered dynamic URL button follows it, since the override applies after slot numbering. Media headers (image, video, document) are filled automatically from the approved template and take no value here (use headerMedia to override the header asset per send). Buttons that are not dynamic-URL buttons (copy-code, flow) take no value here either; use templateButtonParams.
     attr_accessor :template_params
 
     # WhatsApp only. Values for template buttons that carry one at send time, each addressed by the button's position in the approved template. This is the only way to send a copy-code button's payload (a Pix payment code, a coupon) or a flow token, because templateParams is a flat array of text variables and covers dynamic URL buttons only. Supplying a button here overrides whatever templateParams would have derived for that same index, so the send never carries one button twice; repeating an index within this array is rejected with 400. Each index must name a button of the matching kind on the approved template, which is also checked before the send and returns 400 (INVALID_TEMPLATE_BUTTON_PARAM) rather than a Meta rejection.

data/lib/zernio-sdk/version.rb

@@ -11,5 +11,5 @@ Generator version: 7.19.0
 =end
 
 module Zernio
-  VERSION = '0.0.810'
+  VERSION = '0.0.812'
 end

data/openapi.yaml

@@ -26264,7 +26264,13 @@ paths:
                     ({{name}}, {{company}} - how Meta Business Manager creates templates), where
                     values fill the named slots in order of appearance. Example - a body with
                     {{1}}, {{2}} plus a URL button https://example.com/{{1}} takes three values:
-                    [body1, body2, buttonSuffix]. Media headers (image, video, document) are filled
+                    [body1, body2, buttonSuffix]. For positional templates the list must cover
+                    every slot: supplying fewer values than the template's header + body + dynamic
+                    URL-button count is rejected with a 400 (code INVALID_TEMPLATE_PARAMS) naming
+                    the expected split, rather than delivering a template whose button URL was
+                    filled from the wrong value. A dynamic URL button covered by templateButtonParams
+                    needs no value here unless another uncovered dynamic URL button follows it, since
+                    the override applies after slot numbering. Media headers (image, video, document) are filled
                     automatically from the approved template and take no value here (use headerMedia
                     to override the header asset per send). Buttons that are not dynamic-URL buttons
                     (copy-code, flow) take no value here either; use templateButtonParams.
@@ -37877,7 +37883,7 @@ paths:
         - { name: search, in: query, schema: { type: string }, description: 'Case-insensitive substring match on the contact name, email and company. Phone numbers and other platform identifiers are not matched: they live on the contact channel, not on the contact. To reach a contact from an inbox webhook, use the conversation.contactId it already carries.' }
         - { name: tag, in: query, schema: { type: string } }
         - { name: tags, in: query, schema: { type: string }, description: 'Comma-separated tags, matches contacts carrying any of them' }
-        - { name: platform, in: query, schema: { type: string, enum: [instagram, facebook, telegram, twitter, bluesky, reddit, whatsapp] } }
+        - { name: platform, in: query, schema: { type: string, enum: [instagram, facebook, telegram, twitter, bluesky, reddit, whatsapp, slack] } }
         - { name: isSubscribed, in: query, schema: { type: string, enum: ['true', 'false'] } }
         - { name: limit, in: query, schema: { type: integer, default: 50, maximum: 200 } }
         - { name: skip, in: query, schema: { type: integer, default: 0 } }
@@ -37948,7 +37954,7 @@ paths:
                 isSubscribed: { type: boolean, default: true }
                 notes: { type: string }
                 accountId: { type: string, description: Optional. Creates a channel if provided with platform + platformIdentifier }
-                platform: { type: string }
+                platform: { type: string, enum: [instagram, facebook, telegram, twitter, bluesky, reddit, whatsapp, slack], description: 'Channel platform. Only the enum values support contact channels; any other platform is rejected with code platform_not_supported.' }
                 platformIdentifier: { type: string }
                 displayIdentifier: { type: string }
       responses:
@@ -37982,7 +37988,7 @@ paths:
                       platformIdentifier: { type: string }
                       displayIdentifier: { type: string }
                   warning: { type: string }
-        '400': { description: Invalid request }
+        '400': { description: 'Invalid request. Channel fields are all-or-nothing: accountId, platform and platformIdentifier must be sent together (code: missing_required_field). A platform outside the enum does not support contact channels (code: platform_not_supported, details.supportedPlatforms lists the valid values).' }
         '401': { $ref: '#/components/responses/Unauthorized' }
         '409': { description: 'Duplicate channel. The platformIdentifier is already bound to a channel on this accountId.' }
 
@@ -38182,7 +38188,7 @@ paths:
                   skipped: { type: integer }
                   errors: { type: array, items: { type: string }, description: 'Per-contact failures, e.g. an identifier that is not a valid phone number' }
                   total: { type: integer }
-        '400': { description: 'Contact missing required field name, or a row carries platformIdentifier/accountId with no top-level accountId to attach it to. A row missing platformIdentifier while accountId IS set is not a 400: it is reported in errors[] under a 200.' }
+        '400': { description: 'Contact missing required field name, or a row carries platformIdentifier/accountId with no top-level accountId to attach it to. A row missing platformIdentifier while accountId IS set is not a 400: it is reported in errors[] under a 200. An accountId on a platform with no contact channels rejects the whole import (code: platform_not_supported, details.supportedPlatforms lists the valid values).' }
         '401': { $ref: '#/components/responses/Unauthorized' }
 
   /v1/contacts/{contactId}/fields/{slug}:

data/spec/models/create_contact_request_spec.rb

@@ -78,6 +78,10 @@ describe Zernio::CreateContactRequest do
   describe 'test attribute "platform"' 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', ["instagram", "facebook", "telegram", "twitter", "bluesky", "reddit", "whatsapp", "slack"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.platform = value }.not_to raise_error
+      # end
     end
   end
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: zernio-sdk
 version: !ruby/object:Gem::Version
-  version: 0.0.810
+  version: 0.0.812
 platform: ruby
 authors:
 - OpenAPI-Generator
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2026-08-31 00:00:00.000000000 Z
+date: 2026-09-01 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: typhoeus