zernio-sdk 0.0.809 → 0.0.811

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 99efc3c0a5149d104aacd53a7e08b4683eb5ea5c39d34e60baaf34078d383b04
-  data.tar.gz: fc4b1aa17db17d9fa4e3eff504e7f4e2efdc6bf97af1207537c1244b98dd0563
+  metadata.gz: 82188c0fde606e07ab9ae54f8b8f364552edf3efea72c34b472f277b434ace42
+  data.tar.gz: 7e857db3d92e972732e360f80890d7aff9412f83ae7f48440075acab0347d07c
 SHA512:
-  metadata.gz: fa12d26b387723babbc25c446e17b70a8c0cad6640e21266af7c48125fc3844b79b2e1c9a597826c82e69230ccb2f26657883d18c4711ebbbe73bee7fe573159
-  data.tar.gz: 2b3244ad925082cf470bd406367484e248a5a32323ef5cb8ff4a9441984e163a3b5b322c216e067cef2b6fd0f339c36eaa56949b02dc5e15bc120e03d0c2b1b8
+  metadata.gz: 24d28291846e591d151a32d84874ebd2e5ddd67da400b779568a5344e72cff1ad749bfcd20b9e4363ae667683a1b437ceec354e896a8f78ee1e5e1218a93d222
+  data.tar.gz: 524acd6ced10aaee5126f10d045a8d8abc883bfa6def39d3523de1449ead03dd0267a3e416f0914d6843b6d9dcba415f831488a8eb823edc2664a23b04823c16

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/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.809'
+  VERSION = '0.0.811'
 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.

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: zernio-sdk
 version: !ruby/object:Gem::Version
-  version: 0.0.809
+  version: 0.0.811
 platform: ruby
 authors:
 - OpenAPI-Generator