late-sdk 0.0.680 → 0.0.682

data/openapi.yaml

@@ -134,7 +134,7 @@ x-documentation:
 
     Receive real-time notifications for post status changes, account events, and incoming messages:
 
-    - `post.scheduled` - Post created and scheduled for publishing
+    - `post.scheduled` - Post entered the scheduled state: created with a schedule, added to a queue, a draft promoted to scheduled or queued, a failed post retried, or a recycled clone created
     - `post.published` - Post successfully published
     - `post.failed` - Post failed on all platforms
     - `post.partial` - Post published to some platforms, failed on others
@@ -6753,7 +6753,68 @@ components:
         videoAvgTimeWatchedActions:
           type: number
           description: "Average seconds watched per play (Meta `video_avg_time_watched_actions`). Aggregated over date ranges and across children as a play-weighted average (total watch time / total plays), never a plain average of averages."
+        costPerThruplay:
+          type: number
+          description: "Derived `spend / videoThruplayWatchedActions`, in ad-account native currency. Rounded to 4 decimals rather than the usual 2 because a ThruPlay routinely costs well under a cent. 0 when the ad has no ThruPlays."
+        funnel:
+          $ref: '#/components/schemas/AdFunnelCounts'
+        engagementBreakdown:
+          $ref: '#/components/schemas/AdEngagementCounts'
         lastSyncedAt: { type: string, format: date-time, description: "Present on individual ads only, not on campaign aggregations" }
+    AdFunnelCounts:
+      type: object
+      description: |
+        Named conversion-funnel steps, resolved from the same data as `actions`
+        so you never have to parse action-type strings yourself.
+
+        Meta reports one event under several action types at once
+        (`offsite_conversion.fb_pixel_purchase`, `omni_purchase`, `purchase`, …).
+        Each field below takes the FIRST family member present rather than
+        summing them, which is what makes these counts safe to add up — summing
+        the raw `actions` keys yourself double or triple counts. The same
+        priority order backs `conversions`, so a purchase-optimised campaign
+        reports the identical number in `conversions` and `funnel.purchases`.
+
+        Every field is 0 when that step never fired. Populated for Meta ads;
+        other platforms report a different action taxonomy and generally leave
+        these at 0 (read `actions` for those). At ad-set and campaign level each
+        step is summed from its per-ad values.
+      properties:
+        landingPageViews: { type: integer, description: "Landing page views — the visitor actually loaded the destination, unlike a link click. Meta `landing_page_view`." }
+        contentViews: { type: integer, description: "Content views (Meta `ViewContent` pixel event)." }
+        searches: { type: integer, description: "On-site searches (Meta `Search` pixel event)." }
+        wishlistAdds: { type: integer, description: "Adds to wishlist (Meta `AddToWishlist` pixel event)." }
+        cartAdds: { type: integer, description: "Adds to cart (Meta `AddToCart` pixel event)." }
+        checkoutsInitiated: { type: integer, description: "Checkouts started (Meta `InitiateCheckout` pixel event)." }
+        paymentInfoAdds: { type: integer, description: "Payment details added at checkout (Meta `AddPaymentInfo` pixel event)." }
+        purchases: { type: integer, description: "Purchases (Meta `Purchase` pixel event). Pair with `purchaseValue` for revenue." }
+        leads: { type: integer, description: "Leads, from either the website pixel or an instant form — whichever the ad uses." }
+        registrationsCompleted: { type: integer, description: "Completed registrations (Meta `CompleteRegistration` pixel event)." }
+        appInstalls: { type: integer, description: "Mobile app installs attributed to the ad." }
+        messagingConversationsStarted: { type: integer, description: "Messaging conversations started within 7 days — the headline metric for click-to-WhatsApp and click-to-Messenger ads." }
+        messagingFirstReplies: { type: integer, description: "Messaging threads where the person sent a first reply." }
+    AdEngagementCounts:
+      type: object
+      description: |
+        The single `engagement` total split into the interactions behind it.
+
+        Note that `engagement` is not the sum of these: Meta's own
+        `post_engagement` and `page_engagement` totals already contain the
+        individual interactions, and all of them are counted into `engagement`.
+        Use these fields when you need a specific interaction, and `engagement`
+        only as the coarse total it has always been.
+
+        Meta-only; other platforms leave these at 0.
+      properties:
+        postEngagement: { type: integer, description: "Meta's own post-engagement total (`post_engagement`)." }
+        pageEngagement: { type: integer, description: "Meta's own page-engagement total (`page_engagement`)." }
+        reactions: { type: integer, description: "Reactions on the ad's post (`post_reaction`)." }
+        comments: { type: integer, description: "Comments on the ad's post." }
+        shares: { type: integer, description: "Shares of the ad's post. Meta reports these under the action type literally named `post`." }
+        saves: { type: integer, description: "Saves of the ad's post (`onsite_conversion.post_save`)." }
+        pageLikes: { type: integer, description: "New Page likes attributed to the ad (`like`)." }
+        videoViews: { type: integer, description: "3-second video views (`video_view`). For completion-based counts use `videoThruplayWatchedActions`." }
+        linkClicks: { type: integer, description: "Attributed link clicks (`link_click`). This is the attribution-window count, which differs from the in-session `inline_link_clicks` reported by `GET /v1/ads/{adId}/analytics`." }
     AdDailyMetrics:
       description: |
         One day of metrics. Same fields as `AdMetrics` plus the `date` they
@@ -7095,6 +7156,11 @@ components:
           allOf: [{ $ref: '#/components/schemas/AdReviewStatus' }]
           description: "Platform review state of this ad, independent of delivery `status` / `configuredStatus`. Absent when the platform reports no review signal."
         adType: { type: string, enum: [boost, standalone] }
+        creativeType:
+          type: [string, "null"]
+          enum: [carousel, video, document, image, null]
+          description: "Creative format, classified from the media the creative carries. `null` when the creative carries no media to classify — an unsynced creative and a genuine text-only ad are indistinguishable, so neither is guessed at. Returned by `GET /v1/ads`, `GET /v1/ads/{adId}` and the ad nodes of `GET /v1/ads/tree`."
+          example: video
         goal: { type: string, enum: [engagement, traffic, awareness, video_views, lead_generation, lead_conversion, conversions, app_promotion, catalog_sales, job_applicants], description: "Available goals vary by platform. Meta (Facebook/Instagram) supports all 9 (incl. `lead_conversion` = website pixel lead optimization and `catalog_sales` = Advantage+ catalog ads). TikTok supports the 7 non-`lead_conversion` goals. LinkedIn supports all except app_promotion / lead_conversion. Twitter/X supports engagement, traffic, awareness, video_views, app_promotion. Pinterest and Google Ads support only engagement, traffic, awareness, video_views." }
         isExternal: { type: boolean, description: True for ads synced from platform ad managers }
         budget:
@@ -7733,7 +7799,7 @@ webhooks:
     post:
       operationId: onPostScheduled
       summary: Post scheduled event
-      description: Fired when a post is created and scheduled for publishing.
+      description: 'Fired whenever a post enters the scheduled state: created with a schedule, added to a queue, a draft promoted to scheduled or queued, a failed or partial post retried, or a recycled clone created. Not fired when an already-scheduled post is edited or rescheduled.'
       tags: [Webhook Events]
       requestBody:
         required: true
@@ -7808,7 +7874,7 @@ webhooks:
     post:
       operationId: onPostRecycled
       summary: Post recycled event
-      description: Fired when a post is recycled (cloned and re-scheduled for publishing).
+      description: 'Fired when a post is recycled (cloned and re-scheduled for publishing). The new clone also fires a post.scheduled event.'
       tags: [Webhook Events]
       requestBody:
         required: true
@@ -35641,7 +35707,9 @@ paths:
                         platformPostId: { type: string }
                         postTitle: { type: string }
                         keywords: { type: array, items: { type: string } }
-                        matchMode: { type: string, enum: [exact, contains] }
+                        matchMode: { type: string, enum: [exact, contains, word], description: "How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword." }
+                        excludeKeywords: { type: array, items: { type: string }, description: "Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode." }
+                        typoTolerance: { type: boolean, description: "Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched." }
                         dmMessage: { type: string }
                         buttons:
                           type: array
@@ -35716,7 +35784,9 @@ paths:
                   type: array
                   items: { type: string }
                   description: Trigger keywords (empty = any comment triggers)
-                matchMode: { type: string, enum: [exact, contains], default: contains }
+                matchMode: { type: string, enum: [exact, contains, word], default: contains, description: "How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword." }
+                excludeKeywords: { type: array, items: { type: string }, description: "Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode." }
+                typoTolerance: { type: boolean, description: "Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched." }
                 dmMessage: { type: string, description: "DM text to send to commenter. Max 640 chars when buttons are set, otherwise ~1000." }
                 buttons:
                   type: array
@@ -35754,7 +35824,9 @@ paths:
                       trigger: { type: string, enum: [comment, story_reply] }
                       platformPostId: { type: string }
                       keywords: { type: array, items: { type: string } }
-                      matchMode: { type: string, enum: [exact, contains] }
+                      matchMode: { type: string, enum: [exact, contains, word], description: "How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword." }
+                      excludeKeywords: { type: array, items: { type: string }, description: "Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode." }
+                      typoTolerance: { type: boolean, description: "Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched." }
                       dmMessage: { type: string }
                       buttons:
                         type: array
@@ -35804,7 +35876,9 @@ paths:
                       postId: { type: string }
                       postTitle: { type: string }
                       keywords: { type: array, items: { type: string } }
-                      matchMode: { type: string, enum: [exact, contains] }
+                      matchMode: { type: string, enum: [exact, contains, word], description: "How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword." }
+                      excludeKeywords: { type: array, items: { type: string }, description: "Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode." }
+                      typoTolerance: { type: boolean, description: "Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched." }
                       dmMessage: { type: string }
                       buttons:
                         type: array
@@ -35857,7 +35931,9 @@ paths:
               properties:
                 name: { type: string }
                 keywords: { type: array, items: { type: string } }
-                matchMode: { type: string, enum: [exact, contains] }
+                matchMode: { type: string, enum: [exact, contains, word], description: "How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword." }
+                excludeKeywords: { type: array, items: { type: string }, description: "Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode." }
+                typoTolerance: { type: boolean, description: "Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched." }
                 dmMessage: { type: string }
                 buttons:
                   type: array
@@ -35893,7 +35969,9 @@ paths:
                       id: { type: string }
                       name: { type: string }
                       keywords: { type: array, items: { type: string } }
-                      matchMode: { type: string, enum: [exact, contains] }
+                      matchMode: { type: string, enum: [exact, contains, word], description: "How a keyword is compared with the comment. 'contains' (default) matches anywhere, even inside another word (keyword 'app' fires on 'happy'). 'word' matches the keyword only as a standalone word. 'exact' requires the whole comment to be exactly the keyword." }
+                      excludeKeywords: { type: array, items: { type: string }, description: "Comments containing one of these never trigger the automation, even when a trigger keyword also matches. Compared using the same matchMode." }
+                      typoTolerance: { type: boolean, description: "Only with matchMode=word: also fire on close misspellings of a keyword (one edit for 4-7 character keywords, two from 8 up). Keywords shorter than 4 characters are never fuzzy-matched." }
                       dmMessage: { type: string }
                       buttons:
                         type: array

data/spec/models/ad_daily_metrics_spec.rb

@@ -165,6 +165,24 @@ describe Zernio::AdDailyMetrics do
     end
   end
 
+  describe 'test attribute "cost_per_thruplay"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "funnel"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "engagement_breakdown"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "last_synced_at"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/ad_engagement_counts_spec.rb

@@ -0,0 +1,84 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api 
+
+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::AdEngagementCounts
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zernio::AdEngagementCounts do
+  #let(:instance) { Zernio::AdEngagementCounts.new }
+
+  describe 'test an instance of AdEngagementCounts' do
+    it 'should create an instance of AdEngagementCounts' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zernio::AdEngagementCounts)
+    end
+  end
+
+  describe 'test attribute "post_engagement"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "page_engagement"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "reactions"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "comments"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "shares"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "saves"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "page_likes"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "video_views"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "link_clicks"' 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/ad_funnel_counts_spec.rb

@@ -0,0 +1,108 @@
+=begin
+#Zernio API
+
+#API reference for Zernio. Authenticate with a Bearer API key. Base URL: https://zernio.com/api 
+
+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::AdFunnelCounts
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Zernio::AdFunnelCounts do
+  #let(:instance) { Zernio::AdFunnelCounts.new }
+
+  describe 'test an instance of AdFunnelCounts' do
+    it 'should create an instance of AdFunnelCounts' do
+      # uncomment below to test the instance creation
+      #expect(instance).to be_instance_of(Zernio::AdFunnelCounts)
+    end
+  end
+
+  describe 'test attribute "landing_page_views"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "content_views"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "searches"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "wishlist_adds"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "cart_adds"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "checkouts_initiated"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "payment_info_adds"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "purchases"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "leads"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "registrations_completed"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "app_installs"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "messaging_conversations_started"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "messaging_first_replies"' 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/ad_metrics_spec.rb

@@ -165,6 +165,24 @@ describe Zernio::AdMetrics do
     end
   end
 
+  describe 'test attribute "cost_per_thruplay"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "funnel"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "engagement_breakdown"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "last_synced_at"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/ad_spec.rb

@@ -77,6 +77,16 @@ describe Zernio::Ad do
     end
   end
 
+  describe 'test attribute "creative_type"' 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', ["carousel", "video", "document", "image"])
+      # validator.allowable_values.each do |value|
+      #   expect { instance.creative_type = value }.not_to raise_error
+      # end
+    end
+  end
+
   describe 'test attribute "goal"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/create_comment_automation200_response_automation_spec.rb

@@ -70,13 +70,25 @@ describe Zernio::CreateCommentAutomation200ResponseAutomation do
   describe 'test attribute "match_mode"' 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', ["exact", "contains"])
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["exact", "contains", "word"])
       # validator.allowable_values.each do |value|
       #   expect { instance.match_mode = value }.not_to raise_error
       # end
     end
   end
 
+  describe 'test attribute "exclude_keywords"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "typo_tolerance"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "dm_message"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/create_comment_automation_request_spec.rb

@@ -82,13 +82,25 @@ describe Zernio::CreateCommentAutomationRequest do
   describe 'test attribute "match_mode"' 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', ["exact", "contains"])
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["exact", "contains", "word"])
       # validator.allowable_values.each do |value|
       #   expect { instance.match_mode = value }.not_to raise_error
       # end
     end
   end
 
+  describe 'test attribute "exclude_keywords"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "typo_tolerance"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "dm_message"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/get_campaign_analytics200_response_analytics_daily_inner_spec.rb

@@ -165,6 +165,24 @@ describe Zernio::GetCampaignAnalytics200ResponseAnalyticsDailyInner do
     end
   end
 
+  describe 'test attribute "cost_per_thruplay"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "funnel"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "engagement_breakdown"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "last_synced_at"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/get_comment_automation200_response_automation_spec.rb

@@ -88,13 +88,25 @@ describe Zernio::GetCommentAutomation200ResponseAutomation do
   describe 'test attribute "match_mode"' 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', ["exact", "contains"])
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["exact", "contains", "word"])
       # validator.allowable_values.each do |value|
       #   expect { instance.match_mode = value }.not_to raise_error
       # end
     end
   end
 
+  describe 'test attribute "exclude_keywords"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "typo_tolerance"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "dm_message"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/list_comment_automations200_response_automations_inner_spec.rb

@@ -86,13 +86,25 @@ describe Zernio::ListCommentAutomations200ResponseAutomationsInner do
   describe 'test attribute "match_mode"' 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', ["exact", "contains"])
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["exact", "contains", "word"])
       # validator.allowable_values.each do |value|
       #   expect { instance.match_mode = value }.not_to raise_error
       # end
     end
   end
 
+  describe 'test attribute "exclude_keywords"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "typo_tolerance"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "dm_message"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/update_comment_automation200_response_automation_spec.rb

@@ -48,13 +48,25 @@ describe Zernio::UpdateCommentAutomation200ResponseAutomation do
   describe 'test attribute "match_mode"' 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', ["exact", "contains"])
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["exact", "contains", "word"])
       # validator.allowable_values.each do |value|
       #   expect { instance.match_mode = value }.not_to raise_error
       # end
     end
   end
 
+  describe 'test attribute "exclude_keywords"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "typo_tolerance"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "dm_message"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/

data/spec/models/update_comment_automation_request_spec.rb

@@ -42,13 +42,25 @@ describe Zernio::UpdateCommentAutomationRequest do
   describe 'test attribute "match_mode"' 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', ["exact", "contains"])
+      # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["exact", "contains", "word"])
       # validator.allowable_values.each do |value|
       #   expect { instance.match_mode = value }.not_to raise_error
       # end
     end
   end
 
+  describe 'test attribute "exclude_keywords"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  describe 'test attribute "typo_tolerance"' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   describe 'test attribute "dm_message"' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/