late-sdk 0.0.790 → 0.0.792

data/openapi.yaml

@@ -22196,8 +22196,8 @@ paths:
         Important: The mentions array field in POST /v1/posts is stored for reference only and does NOT trigger @mentions on LinkedIn. You must embed the mention format directly in the content text.
 
         Requirements:
-        - Person mentions require the LinkedIn account to be admin of at least one organization. This is a LinkedIn API limitation: the only endpoints that resolve profile URLs to member URNs (vanityUrl, peopleTypeahead) are scoped to organization followers. There is no public LinkedIn API to resolve a vanity URL without organization context.
-        - Organization mentions (e.g. @Microsoft) work without this requirement.
+        - Person mentions require the LinkedIn account to be admin of at least one organization: both endpoints that resolve a profile URL to a member URN take an organization you administer. Organization mentions (e.g. @Microsoft) have no such requirement.
+        - The two are not scoped alike. peopleTypeahead?q=organizationFollowers only returns that organization's followers; vanityUrl?q=vanityUrlAsOrganization does not, and its resolvable set is opaque. A 404 here does not mean the person is unknown to you or unknown to LinkedIn: a live public profile can 404 with no reason given.
         - For person mentions to be clickable, the displayName parameter must exactly match the name shown on their LinkedIn profile.
         - Person mentions DO work when published from personal profiles (the URN just needs to be valid). The limitation is only in the resolution step (URL to URN), not in publishing.
       parameters:
@@ -22328,7 +22328,7 @@ paths:
                   error: { type: string }
               examples:
                 memberNotFound:
-                  value: { error: "Member not found. Check the LinkedIn URL is correct." }
+                  value: { error: "LinkedIn couldn't resolve this profile. Not every profile is resolvable through LinkedIn's API, even public ones, and LinkedIn gives no reason. Check the profile address is current (people can change theirs), or mention a company instead." }
                 orgNotFound:
                   value: { error: "Organization not found. Check the LinkedIn company URL is correct." }
 
@@ -29933,8 +29933,9 @@ paths:
       tags: [WhatsApp]
       summary: List templates
       description: |
-        List all message templates for the WhatsApp Business Account (WABA) associated with the given account.
-        Templates are fetched directly from the WhatsApp Cloud API.
+        List message templates for the WhatsApp Business Account (WABA) associated with the given account.
+        Templates are fetched directly from the WhatsApp Cloud API. One entry per **name + language**:
+        a multi-language template appears once per language, each with its own Meta `id`.
       security:
         - bearerAuth: []
       parameters:
@@ -29944,6 +29945,24 @@ paths:
           description: WhatsApp social account ID
           schema:
             type: string
+        - name: name
+          in: query
+          required: false
+          description: 'Exact template name; returns every language variant of that family.'
+          schema:
+            type: string
+        - name: language
+          in: query
+          required: false
+          description: 'Exact language code (e.g. en_US).'
+          schema:
+            type: string
+        - name: status
+          in: query
+          required: false
+          schema:
+            type: string
+            enum: [APPROVED, REJECTED, PENDING, PAUSED, DISABLED, IN_APPEAL, PENDING_DELETION]
       responses:
         '200':
           description: Templates retrieved successfully
@@ -30115,14 +30134,21 @@ paths:
       tags: [WhatsApp]
       summary: Get template
       description: |
-        Retrieve a single message template by name.
+        Retrieve one message template variant by name.
+
+        Meta stores one template per **name + language**, so a name identifies a family of variants,
+        each with its own Meta id. Pass `language` to address one variant. Without it, a name with a
+        single variant resolves to that variant; a name with several returns `409 ambiguous_template`
+        with `details.languages`. A bare language (`es`) matches a single regional variant (`es_ES`);
+        if the family has several regional variants for it, that is also a 409. A full code (`es_ES`)
+        must match exactly. Variants in `PENDING_DELETION` are not part of the family.
       security:
         - bearerAuth: []
       parameters:
         - name: templateName
           in: path
           required: true
-          description: Template name
+          description: Template name (the family).
           schema:
             type: string
         - name: accountId
@@ -30131,6 +30157,12 @@ paths:
           description: WhatsApp social account ID
           schema:
             type: string
+        - name: language
+          in: query
+          required: false
+          description: 'Language code of the variant (e.g. en_US, es, pt_BR). Required when the family has several languages.'
+          schema:
+            type: string
       responses:
         '200':
           description: Template retrieved successfully
@@ -30143,18 +30175,35 @@ paths:
                   template:
                     type: object
                     properties:
-                      id: { type: string }
+                      id: { type: string, description: 'Meta template id. Unique per language variant; usable on /v1/whatsapp/templates/id/{templateId}.' }
                       name: { type: string }
                       status: { type: string }
                       category: { type: string }
-                      language: { type: string }
+                      language: { type: string, description: 'The variant actually returned.' }
                       components:
                         type: array
                         items:
                           type: object
-        '400': { description: accountId is required }
+                      rejected_reason: { type: string, description: 'Only when status is REJECTED.' }
+                      quality_score: { type: object, description: 'Post-approval quality (GREEN/YELLOW/RED), when Meta reports one.' }
+        '400': { $ref: '#/components/responses/BadRequest' }
         '401': { $ref: '#/components/responses/Unauthorized' }
-        '404': { $ref: '#/components/responses/NotFound' }
+        '404': { description: 'Account not found, or no template with that name (and language, when given). details.languages lists the family''s languages when the name exists (code template_not_found).' }
+        '409':
+          description: 'The template name exists in several languages and no language was given (code ambiguous_template). details.languages lists them.'
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  error: { type: string }
+                  type: { type: string, enum: [invalid_request_error] }
+                  code: { type: string, enum: [ambiguous_template] }
+                  param: { type: string, enum: [language] }
+                  details:
+                    type: object
+                    properties:
+                      languages: { type: array, items: { type: string } }
         '502': { description: Meta rejected the request or was unreachable. Meta 4xx statuses are forwarded as-is. }
     patch:
       x-resource-group: "accounts"
@@ -30162,20 +30211,28 @@ paths:
       tags: [WhatsApp]
       summary: Update template
       description: |
-        Update a message template's components. Only certain fields can be updated depending on
-        the template's current approval state. Approved templates can only have components updated.
+        Update one variant's components. Name, language and category cannot change after creation.
+
+        Meta stores one template per **name + language**, so a name identifies a family of variants,
+        each with its own Meta id. Pass `language` to address one variant. Without it, a name with a
+        single variant resolves to that variant; a name with several returns `409 ambiguous_template`
+        with `details.languages`. A bare language (`es`) matches a single regional variant (`es_ES`);
+        if the family has several regional variants for it, that is also a 409. A full code (`es_ES`)
+        must match exactly. Variants in `PENDING_DELETION` are not part of the family.
 
-        A successful update sends the template back to Meta for review, so the `status` returned
-        here is normally `PENDING`. The final outcome arrives later on the
-        `whatsapp.template.status_updated` webhook. A template already in `PENDING` cannot be
-        edited again until Meta finishes reviewing it.
+        Meta only allows editing templates in `APPROVED`, `REJECTED` or `PAUSED` state; an approved
+        template can be edited once per 24 hours and up to 10 times per 30 days. A successful update
+        sends the variant back to Meta for review, so the `status` returned here is normally `PENDING`.
+        The final outcome arrives on the `whatsapp.template.status_updated` webhook (which carries the
+        variant's `templateId` and `language`). A variant already in `PENDING` cannot be edited again
+        until Meta finishes reviewing it.
       security:
         - bearerAuth: []
       parameters:
         - name: templateName
           in: path
           required: true
-          description: Template name
+          description: Template name (the family).
           schema:
             type: string
       requestBody:
@@ -30191,6 +30248,9 @@ paths:
                 accountId:
                   type: string
                   description: WhatsApp social account ID
+                language:
+                  type: string
+                  description: 'Language code of the variant to edit (e.g. en_US, es, pt_BR). Required when the family has several languages. Body only: a language query parameter on PATCH is a 400.'
                 components:
                   type: array
                   description: Updated template components
@@ -30199,15 +30259,16 @@ paths:
                     $ref: '#/components/schemas/WhatsAppTemplateComponent'
             example:
               accountId: "507f1f77bcf86cd799439011"
+              language: "es"
               components:
                 - type: "body"
-                  text: "Updated: Your order {{1}} is confirmed. Delivery by {{2}}"
+                  text: "Actualizado: tu pedido {{1}} está confirmado. Entrega el {{2}}"
                   example:
-                    body_text: [["ORD-12345", "April 1"]]
+                    body_text: [["ORD-12345", "1 de abril"]]
                 - type: "buttons"
                   buttons:
                     - type: "quick_reply"
-                      text: "Track Order"
+                      text: "Seguir pedido"
       responses:
         '200':
           description: Template updated successfully
@@ -30220,15 +30281,31 @@ paths:
                   template:
                     type: object
                     properties:
-                      id: { type: string }
+                      id: { type: string, description: 'Meta id of the edited variant.' }
                       name: { type: string }
+                      language: { type: string, description: 'The variant that was edited.' }
                       status:
                         type: string
                         description: 'Approval state read back from Meta after the update, normally PENDING. If the state cannot be read back, the last known status is returned instead.'
                         example: PENDING
-        '400': { description: Validation error (missing fields) }
+        '400': { $ref: '#/components/responses/BadRequest' }
         '401': { $ref: '#/components/responses/Unauthorized' }
-        '404': { $ref: '#/components/responses/NotFound' }
+        '404': { description: 'Account not found, or no template with that name (and language, when given) (code template_not_found).' }
+        '409':
+          description: 'The template name exists in several languages and no language was given (code ambiguous_template). details.languages lists them.'
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  error: { type: string }
+                  type: { type: string, enum: [invalid_request_error] }
+                  code: { type: string, enum: [ambiguous_template] }
+                  param: { type: string, enum: [language] }
+                  details:
+                    type: object
+                    properties:
+                      languages: { type: array, items: { type: string } }
         '502': { description: Meta rejected the update or was unreachable. Meta 4xx statuses are forwarded as-is. }
     delete:
       x-resource-group: "accounts"
@@ -30236,14 +30313,19 @@ paths:
       tags: [WhatsApp]
       summary: Delete template
       description: |
-        Permanently delete a message template by name.
+        Permanently delete a message template.
+
+        **Without `language` this deletes every language variant of the name** (Meta's own
+        contract for deletion by name). Pass `language` to delete one variant only; the response
+        `scope` says which happened. Meta keeps a deleted approved template in `PENDING_DELETION`
+        for a while and the name cannot be reused for 30 days.
       security:
         - bearerAuth: []
       parameters:
         - name: templateName
           in: path
           required: true
-          description: Template name
+          description: Template name (the family).
           schema:
             type: string
         - name: accountId
@@ -30252,6 +30334,12 @@ paths:
           description: WhatsApp social account ID
           schema:
             type: string
+        - name: language
+          in: query
+          required: false
+          description: 'Delete only this language variant (e.g. es). Omit to delete the whole family.'
+          schema:
+            type: string
       responses:
         '200':
           description: Template deleted successfully
@@ -30261,19 +30349,183 @@ paths:
                 type: object
                 properties:
                   success: { type: boolean }
+                  scope: { type: string, enum: [all_languages, language], description: 'Whether the whole family or one variant was deleted.' }
+                  language: { type: string, description: 'The deleted variant; only when scope is language.' }
                   message: { type: string }
-              example:
-                success: true
-                message: "Template \"order_confirmation\" deleted successfully"
-        '400': { description: accountId or template name is required }
+        '400': { $ref: '#/components/responses/BadRequest' }
         '401': { $ref: '#/components/responses/Unauthorized' }
-        '404': { $ref: '#/components/responses/NotFound' }
-        '502': { description: Meta rejected the delete or was unreachable. Meta 4xx statuses are forwarded as-is. }
-
-  # ──────────────────────────────────────────────────────────────────────────
-  # WHATSAPP BUSINESS CALLING
-  # ──────────────────────────────────────────────────────────────────────────
+        '404': { description: 'Account not found, or (with language) no such variant (code template_not_found).' }
+        '409':
+          description: 'Only with language: a bare code (es) matched several regional variants (es_ES, es_MX), so nothing was deleted (code ambiguous_template). Without language there is no 409: the whole family is deleted.'
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  error: { type: string }
+                  type: { type: string, enum: [invalid_request_error] }
+                  code: { type: string, enum: [ambiguous_template] }
+                  param: { type: string, enum: [language] }
+                  details:
+                    type: object
+                    properties:
+                      languages: { type: array, items: { type: string } }
+        '502': { description: Meta rejected the request or was unreachable. Meta 4xx statuses are forwarded as-is. }
+  /v1/whatsapp/templates/id/{templateId}:
+    get:
+      x-resource-group: "accounts"
+      operationId: getWhatsAppTemplateById
+      tags: [WhatsApp]
+      summary: Get template by id
+      description: |
+        Retrieve one template variant by its Meta id, the id every variant of a family has on its own
+        and the one the `whatsapp.template.status_updated` webhook carries.
+      security:
+        - bearerAuth: []
+      parameters:
+        - name: templateId
+          in: path
+          required: true
+          description: Meta template id (numeric).
+          schema:
+            type: string
+        - name: accountId
+          in: query
+          required: true
+          description: WhatsApp social account ID
+          schema:
+            type: string
+      responses:
+        '200':
+          description: Template retrieved successfully
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  success: { type: boolean }
+                  template:
+                    type: object
+                    properties:
+                      id: { type: string, description: 'Meta template id. Unique per language variant; usable on /v1/whatsapp/templates/id/{templateId}.' }
+                      name: { type: string }
+                      status: { type: string }
+                      category: { type: string }
+                      language: { type: string, description: 'The variant actually returned.' }
+                      components:
+                        type: array
+                        items:
+                          type: object
+                      rejected_reason: { type: string, description: 'Only when status is REJECTED.' }
+                      quality_score: { type: object, description: 'Post-approval quality (GREEN/YELLOW/RED), when Meta reports one.' }
+        '400': { $ref: '#/components/responses/BadRequest' }
+        '401': { $ref: '#/components/responses/Unauthorized' }
+        '404': { description: Account not found. }
+        '502': { description: 'Meta rejected the request (including an id the account cannot access) or was unreachable. Meta 4xx statuses are forwarded as-is.' }
+    patch:
+      x-resource-group: "accounts"
+      operationId: updateWhatsAppTemplateById
+      tags: [WhatsApp]
+      summary: Update template by id
+      description: |
+        Update one variant's components by its Meta id. Name, language and category cannot change.
 
+        Meta only allows editing templates in `APPROVED`, `REJECTED` or `PAUSED` state; an approved
+        template can be edited once per 24 hours and up to 10 times per 30 days. A successful update
+        sends the variant back to Meta for review, so the `status` returned here is normally `PENDING`.
+        The final outcome arrives on the `whatsapp.template.status_updated` webhook (which carries the
+        variant's `templateId` and `language`). A variant already in `PENDING` cannot be edited again
+        until Meta finishes reviewing it.
+      security:
+        - bearerAuth: []
+      parameters:
+        - name: templateId
+          in: path
+          required: true
+          description: Meta template id (numeric).
+          schema:
+            type: string
+      requestBody:
+        required: true
+        content:
+          application/json:
+            schema:
+              type: object
+              required:
+                - accountId
+                - components
+              properties:
+                accountId:
+                  type: string
+                  description: WhatsApp social account ID
+                components:
+                  type: array
+                  description: Updated template components
+                  minItems: 1
+                  items:
+                    $ref: '#/components/schemas/WhatsAppTemplateComponent'
+      responses:
+        '200':
+          description: Template updated successfully
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  success: { type: boolean }
+                  template:
+                    type: object
+                    properties:
+                      id: { type: string }
+                      name: { type: string }
+                      language: { type: string }
+                      status:
+                        type: string
+                        description: 'Approval state read back from Meta after the update, normally PENDING. If the state cannot be read back, the last known status is returned instead.'
+                        example: PENDING
+        '400': { $ref: '#/components/responses/BadRequest' }
+        '401': { $ref: '#/components/responses/Unauthorized' }
+        '404': { description: Account not found. }
+        '502': { description: 'Meta rejected the update (including an id the account cannot access) or was unreachable. Meta 4xx statuses are forwarded as-is.' }
+    delete:
+      x-resource-group: "accounts"
+      operationId: deleteWhatsAppTemplateById
+      tags: [WhatsApp]
+      summary: Delete template by id
+      description: |
+        Delete one language variant by its Meta id. Other languages of the same name are untouched.
+        The name cannot be reused for 30 days once its last variant is deleted.
+      security:
+        - bearerAuth: []
+      parameters:
+        - name: templateId
+          in: path
+          required: true
+          description: Meta template id (numeric).
+          schema:
+            type: string
+        - name: accountId
+          in: query
+          required: true
+          description: WhatsApp social account ID
+          schema:
+            type: string
+      responses:
+        '200':
+          description: Variant deleted successfully
+          content:
+            application/json:
+              schema:
+                type: object
+                properties:
+                  success: { type: boolean }
+                  scope: { type: string, enum: [language] }
+                  language: { type: string }
+                  message: { type: string }
+        '400': { $ref: '#/components/responses/BadRequest' }
+        '401': { $ref: '#/components/responses/Unauthorized' }
+        '404': { description: Account not found. }
+        '502': { description: 'Meta rejected the request (including an id the account cannot access) or was unreachable. Meta 4xx statuses are forwarded as-is.' }
   /v1/whatsapp/calling:
     get:
       x-resource-group: "accounts"

data/spec/api/linked_in_mentions_api_spec.rb

@@ -34,7 +34,7 @@ describe 'LinkedInMentionsApi' do
 
   # unit tests for get_linked_in_mentions
   # Resolve LinkedIn mention
-  # Converts a LinkedIn profile or company URL to a URN for @mentions in posts.  How to use LinkedIn @mentions (2-step workflow):  1. Call this endpoint with the LinkedIn profile/company URL to get the mention URN and format. 2. Embed the returned mentionFormat (e.g. @[Vincent Jong](urn:li:person:xxx)) directly in your post's content field.  Example: - Resolve: GET /v1/accounts/{id}/linkedin-mentions?url=linkedin.com/in/vincentjong&displayName=Vincent Jong - Returns: mentionFormat: \"@[Vincent Jong](urn:li:person:xxx)\" - Use in post content: \"Great talk with @[Vincent Jong](urn:li:person:xxx) today!\"  Important: The mentions array field in POST /v1/posts is stored for reference only and does NOT trigger @mentions on LinkedIn. You must embed the mention format directly in the content text.  Requirements: - Person mentions require the LinkedIn account to be admin of at least one organization. This is a LinkedIn API limitation: the only endpoints that resolve profile URLs to member URNs (vanityUrl, peopleTypeahead) are scoped to organization followers. There is no public LinkedIn API to resolve a vanity URL without organization context. - Organization mentions (e.g. @Microsoft) work without this requirement. - For person mentions to be clickable, the displayName parameter must exactly match the name shown on their LinkedIn profile. - Person mentions DO work when published from personal profiles (the URN just needs to be valid). The limitation is only in the resolution step (URL to URN), not in publishing. 
+  # Converts a LinkedIn profile or company URL to a URN for @mentions in posts.  How to use LinkedIn @mentions (2-step workflow):  1. Call this endpoint with the LinkedIn profile/company URL to get the mention URN and format. 2. Embed the returned mentionFormat (e.g. @[Vincent Jong](urn:li:person:xxx)) directly in your post's content field.  Example: - Resolve: GET /v1/accounts/{id}/linkedin-mentions?url=linkedin.com/in/vincentjong&displayName=Vincent Jong - Returns: mentionFormat: \"@[Vincent Jong](urn:li:person:xxx)\" - Use in post content: \"Great talk with @[Vincent Jong](urn:li:person:xxx) today!\"  Important: The mentions array field in POST /v1/posts is stored for reference only and does NOT trigger @mentions on LinkedIn. You must embed the mention format directly in the content text.  Requirements: - Person mentions require the LinkedIn account to be admin of at least one organization: both endpoints that resolve a profile URL to a member URN take an organization you administer. Organization mentions (e.g. @Microsoft) have no such requirement. - The two are not scoped alike. peopleTypeahead?q=organizationFollowers only returns that organization's followers; vanityUrl?q=vanityUrlAsOrganization does not, and its resolvable set is opaque. A 404 here does not mean the person is unknown to you or unknown to LinkedIn: a live public profile can 404 with no reason given. - For person mentions to be clickable, the displayName parameter must exactly match the name shown on their LinkedIn profile. - Person mentions DO work when published from personal profiles (the URN just needs to be valid). The limitation is only in the resolution step (URL to URN), not in publishing. 
   # @param account_id The LinkedIn account ID
   # @param url LinkedIn profile URL, company URL, or vanity name.
   # @param [Hash] opts the optional parameters

data/spec/api/whats_app_api_spec.rb

@@ -136,17 +136,31 @@ describe 'WhatsAppApi' do
 
   # unit tests for delete_whats_app_template
   # Delete template
-  # Permanently delete a message template by name. 
-  # @param template_name Template name
+  # Permanently delete a message template.  **Without `language` this deletes every language variant of the name** (Meta's own contract for deletion by name). Pass `language` to delete one variant only; the response `scope` says which happened. Meta keeps a deleted approved template in `PENDING_DELETION` for a while and the name cannot be reused for 30 days. 
+  # @param template_name Template name (the family).
   # @param account_id WhatsApp social account ID
   # @param [Hash] opts the optional parameters
-  # @return [UnpublishPost200Response]
+  # @option opts [String] :language Delete only this language variant (e.g. es). Omit to delete the whole family.
+  # @return [DeleteWhatsAppTemplate200Response]
   describe 'delete_whats_app_template 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 delete_whats_app_template_by_id
+  # Delete template by id
+  # Delete one language variant by its Meta id. Other languages of the same name are untouched. The name cannot be reused for 30 days once its last variant is deleted. 
+  # @param template_id Meta template id (numeric).
+  # @param account_id WhatsApp social account ID
+  # @param [Hash] opts the optional parameters
+  # @return [DeleteWhatsAppTemplateById200Response]
+  describe 'delete_whats_app_template_by_id 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 delete_whatsapp_business_username
   # Delete business username
   # Release the currently claimed WhatsApp Business username from the account. After deletion the username becomes available for other accounts to claim. 
@@ -250,10 +264,11 @@ describe 'WhatsAppApi' do
 
   # unit tests for get_whats_app_template
   # Get template
-  # Retrieve a single message template by name. 
-  # @param template_name Template name
+  # Retrieve one message template variant by name.  Meta stores one template per **name + language**, so a name identifies a family of variants, each with its own Meta id. Pass `language` to address one variant. Without it, a name with a single variant resolves to that variant; a name with several returns `409 ambiguous_template` with `details.languages`. A bare language (`es`) matches a single regional variant (`es_ES`); if the family has several regional variants for it, that is also a 409. A full code (`es_ES`) must match exactly. Variants in `PENDING_DELETION` are not part of the family. 
+  # @param template_name Template name (the family).
   # @param account_id WhatsApp social account ID
   # @param [Hash] opts the optional parameters
+  # @option opts [String] :language Language code of the variant (e.g. en_US, es, pt_BR). Required when the family has several languages.
   # @return [GetWhatsAppTemplate200Response]
   describe 'get_whats_app_template test' do
     it 'should work' do
@@ -261,11 +276,27 @@ describe 'WhatsAppApi' do
     end
   end
 
+  # unit tests for get_whats_app_template_by_id
+  # Get template by id
+  # Retrieve one template variant by its Meta id, the id every variant of a family has on its own and the one the `whatsapp.template.status_updated` webhook carries. 
+  # @param template_id Meta template id (numeric).
+  # @param account_id WhatsApp social account ID
+  # @param [Hash] opts the optional parameters
+  # @return [GetWhatsAppTemplate200Response]
+  describe 'get_whats_app_template_by_id 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_whats_app_templates
   # List templates
-  # List all message templates for the WhatsApp Business Account (WABA) associated with the given account. Templates are fetched directly from the WhatsApp Cloud API. 
+  # List message templates for the WhatsApp Business Account (WABA) associated with the given account. Templates are fetched directly from the WhatsApp Cloud API. One entry per **name + language**: a multi-language template appears once per language, each with its own Meta `id`. 
   # @param account_id WhatsApp social account ID
   # @param [Hash] opts the optional parameters
+  # @option opts [String] :name Exact template name; returns every language variant of that family.
+  # @option opts [String] :language Exact language code (e.g. en_US).
+  # @option opts [String] :status 
   # @return [GetWhatsAppTemplates200Response]
   describe 'get_whats_app_templates test' do
     it 'should work' do
@@ -467,8 +498,8 @@ describe 'WhatsAppApi' do
 
   # unit tests for update_whats_app_template
   # Update template
-  # Update a message template's components. Only certain fields can be updated depending on the template's current approval state. Approved templates can only have components updated.  A successful update sends the template back to Meta for review, so the `status` returned here is normally `PENDING`. The final outcome arrives later on the `whatsapp.template.status_updated` webhook. A template already in `PENDING` cannot be edited again until Meta finishes reviewing it. 
-  # @param template_name Template name
+  # Update one variant's components. Name, language and category cannot change after creation.  Meta stores one template per **name + language**, so a name identifies a family of variants, each with its own Meta id. Pass `language` to address one variant. Without it, a name with a single variant resolves to that variant; a name with several returns `409 ambiguous_template` with `details.languages`. A bare language (`es`) matches a single regional variant (`es_ES`); if the family has several regional variants for it, that is also a 409. A full code (`es_ES`) must match exactly. Variants in `PENDING_DELETION` are not part of the family.  Meta only allows editing templates in `APPROVED`, `REJECTED` or `PAUSED` state; an approved template can be edited once per 24 hours and up to 10 times per 30 days. A successful update sends the variant back to Meta for review, so the `status` returned here is normally `PENDING`. The final outcome arrives on the `whatsapp.template.status_updated` webhook (which carries the variant's `templateId` and `language`). A variant already in `PENDING` cannot be edited again until Meta finishes reviewing it. 
+  # @param template_name Template name (the family).
   # @param update_whats_app_template_request 
   # @param [Hash] opts the optional parameters
   # @return [UpdateWhatsAppTemplate200Response]
@@ -478,6 +509,19 @@ describe 'WhatsAppApi' do
     end
   end
 
+  # unit tests for update_whats_app_template_by_id
+  # Update template by id
+  # Update one variant's components by its Meta id. Name, language and category cannot change.  Meta only allows editing templates in `APPROVED`, `REJECTED` or `PAUSED` state; an approved template can be edited once per 24 hours and up to 10 times per 30 days. A successful update sends the variant back to Meta for review, so the `status` returned here is normally `PENDING`. The final outcome arrives on the `whatsapp.template.status_updated` webhook (which carries the variant's `templateId` and `language`). A variant already in `PENDING` cannot be edited again until Meta finishes reviewing it. 
+  # @param template_id Meta template id (numeric).
+  # @param update_whats_app_template_by_id_request 
+  # @param [Hash] opts the optional parameters
+  # @return [UpdateWhatsAppTemplateById200Response]
+  describe 'update_whats_app_template_by_id 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 upload_whats_app_profile_photo
   # Upload profile picture
   # Upload a new profile picture for the WhatsApp Business Profile. Uses Meta's resumable upload API under the hood: creates an upload session, uploads the image bytes, then updates the business profile with the resulting handle.  Provide the image either as a binary upload (`multipart/form-data` with `file`) or as a download URL (`application/json` with `url`) — with a URL we fetch the image server-side and upload the bytes for you. Meta's profile-photo API is bytes-only, so there is no direct URL passthrough. JPEG/PNG, max 5MB either way. 

data/spec/models/delete_whats_app_template200_response_spec.rb

@@ -0,0 +1,58 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api  Versioning and deprecation: all endpoints are versioned in the URL path (current version: /v1). Breaking changes only ship in a new path version; existing versions keep working. Deprecated operations are marked 'deprecated: true' in this spec and announced in the changelog (https://zernio.com/changelog) before removal.  Errors: every 4xx/5xx response is application/json with a machine-readable 'code' and a human-readable 'error' message (see the ErrorResponse schema). 
+
+The version of the OpenAPI document: 1.0.4
+Contact: support@zernio.com
+Generated by: https://openapi-generator.tech
+Generator version: 7.19.0
+
+=end
+
+require 'spec_helper'
+require 'json'
+require 'date'
+
+# Unit tests for Zernio::DeleteWhatsAppTemplate200Response
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zernio::DeleteWhatsAppTemplate200Response do
+  #let(:instance) { Zernio::DeleteWhatsAppTemplate200Response.new }
+
+  describe 'test an instance of DeleteWhatsAppTemplate200Response' do
+    it 'should create an instance of DeleteWhatsAppTemplate200Response' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zernio::DeleteWhatsAppTemplate200Response)
+    end
+  end
+
+  describe 'test attribute "success"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "scope"' 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', ["all_languages", "language"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.scope = value }.not_to raise_error
+      # end
+    end
+  end
+
+  describe 'test attribute "language"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "message"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end