late-sdk 0.0.940 → 0.0.942

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: eea18f021beb7aff1f375442b6ef474bcaa7d330fe7f0386e6028361e12d6296
-  data.tar.gz: dfec92c6178e641234a2aa38e544d9b8bb1fa6e1cb41b3145d7a1c42c21a9b7a
+  metadata.gz: ba18187caa8b6099fdf28c0abe6acfa0d95375d823c900b8abc1ade97734d099
+  data.tar.gz: e7a776db55e898700be2659797e3f592afd00b01cc81b7c26101dc6b68f5e8ce
 SHA512:
-  metadata.gz: 6ad07eeb8b90dec07fdd1bf3296d2a2e5a867965b4561d0bf94335c16f2a76af071165ab34e5d76ca63beb5c350f0f7349ea2ac67cc1e5d0d5e8ceb9fe6c4ce7
-  data.tar.gz: fc897afdb5c8dcd0e7dcc41191d38550f045a22b60a367852098a7138b0c07ba8d5df57a9be9051f2851f3f6e5ddd77f1140de0dfb986f5ef80700a3bc89c838
+  metadata.gz: 25d1bfee0f1ec7ca57750f4cb1d2c1821746b89f5e4f8ef16323dfc0fa7e9284a82628958e673b8125bfbc2e0ea99992a3d2ddad9f368ce7ebd2f757bf2a5ffd
+  data.tar.gz: 757c1d2e618073bb7a4f928c4eaab259c82166c41ed2cbfcc8a8bce647bb429442ba303fe5fca3cedfd3e689ada83657b1cbb38ce62b48ba332c1162016617d1

data/docs/CommentsApi.md

@@ -487,7 +487,7 @@ end
 api_instance = Zernio::CommentsApi.new
 opts = {
   profile_id: 'profile_id_example', # String | Filter by profile ID
-  platform: 'facebook', # String | Filter by platform. `metaads` is a synthetic value meaning the user's ads (boosted/dark posts) only; `facebook`/`instagram` return organic posts only.
+  platform: 'facebook', # String | Filter by platform. `metaads` is a synthetic value meaning the user's ads (boosted/dark posts) only; `facebook`/`instagram` return organic posts only. `tiktok` covers accounts connected through the TikTok Business app only; developer-app TikTok accounts are returned under `meta.accountsSkipped`.
   min_comments: 56, # Integer | Minimum comment count
   since: Time.parse('2013-10-20T19:20:30+01:00'), # Time | Posts created after this date
   sort_by: 'date', # String | Sort field
@@ -529,7 +529,7 @@ end
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **profile_id** | **String** | Filter by profile ID | [optional] |
-| **platform** | **String** | Filter by platform. `metaads` is a synthetic value meaning the user's ads (boosted/dark posts) only; `facebook`/`instagram` return organic posts only. | [optional] |
+| **platform** | **String** | Filter by platform. `metaads` is a synthetic value meaning the user's ads (boosted/dark posts) only; `facebook`/`instagram` return organic posts only. `tiktok` covers accounts connected through the TikTok Business app only; developer-app TikTok accounts are returned under `meta.accountsSkipped`. | [optional] |
 | **min_comments** | **Integer** | Minimum comment count | [optional] |
 | **since** | **Time** | Posts created after this date | [optional] |
 | **sort_by** | **String** | Sort field | [optional][default to 'date'] |

data/docs/WhatsAppApi.md

@@ -53,7 +53,7 @@ All URIs are relative to *https://zernio.com/api*
 
 Add participants
 
-Add participants to a WhatsApp group. Maximum 8 participants per request.  Not available on [Coexistence](/platforms/whatsapp/connection#whatsapp-business-app-coexistence) numbers. Requires a Cloud API-only number. 
+Add participants to a WhatsApp group. Maximum 8 participants per request. A group holds at most 8 participants in total (a Meta limit), so later requests cannot grow a group past 8. Meta documents groups as invite-only, so people normally join through the group's invite link.  Not available on [Coexistence](/platforms/whatsapp/connection#whatsapp-business-app-coexistence) numbers. Requires a Cloud API-only number. 
 
 ### Examples
 

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

@@ -504,7 +504,7 @@ module Zernio
     # Returns posts with comment counts from all connected accounts. Aggregates data across multiple accounts.  Responses are cached for up to 10 minutes, so the feed may lag new comments by that window. Do not poll this endpoint for real-time updates: subscribe to the `comment.received` webhook, which fires for every new comment across your posts and carries the post reference needed to keep this list current.  For users with the Ads add-on (accounts on usage-based billing always qualify), the user's Meta ads (boosted/dark posts) are included too. There's one row per (ad, placement-with-comments): an ad that runs on both Facebook feed and Instagram feed produces up to two rows (the Page dark post and the IG media have separate comment threads), each flagged `isAd: true` with `adId` and `placement` (`id` is `{adId}:{placement}`). Use `?platform=metaads` to return *only* ad rows; passing `facebook`/`instagram` returns *organic* posts only (no ads); omitting `platform` returns both. Fetch a row's thread from GET /v1/ads/{adId}/comments?placement={placement}. Ad comment counts are read with the Marketing API token (Facebook side) or the connected Instagram account's token (Instagram side); a row whose count can't be read is omitted.  Pagination walks each account's platform listing. Following `nextCursor` reaches past the first page on Facebook, Instagram, Threads, LinkedIn and YouTube, since they are the platforms that support a server-side date window; on the others the listing stops at its first page. Cursor pagination is only coherent for the default sort (`sortBy=date`, `sortOrder=desc`): with `sortOrder=asc`, or with `sortBy=comments`, the cursor filter does not match the sort order and the second page is unreliable.  `nextCursor` is opaque: pass it back verbatim, never construct or parse it, its composition may change without notice. Because each page re-queries a live window, results can still shift between requests, so dedupe by `id` on the client.  `commentCount` semantics differ by platform: YouTube's includes replies, Facebook's counts top-level comments only. 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :profile_id Filter by profile ID
-    # @option opts [String] :platform Filter by platform. `metaads` is a synthetic value meaning the user's ads (boosted/dark posts) only; `facebook`/`instagram` return organic posts only.
+    # @option opts [String] :platform Filter by platform. `metaads` is a synthetic value meaning the user's ads (boosted/dark posts) only; `facebook`/`instagram` return organic posts only. `tiktok` covers accounts connected through the TikTok Business app only; developer-app TikTok accounts are returned under `meta.accountsSkipped`.
     # @option opts [Integer] :min_comments Minimum comment count
     # @option opts [Time] :since Posts created after this date
     # @option opts [String] :sort_by Sort field (default to 'date')
@@ -522,7 +522,7 @@ module Zernio
     # Returns posts with comment counts from all connected accounts. Aggregates data across multiple accounts.  Responses are cached for up to 10 minutes, so the feed may lag new comments by that window. Do not poll this endpoint for real-time updates: subscribe to the `comment.received` webhook, which fires for every new comment across your posts and carries the post reference needed to keep this list current.  For users with the Ads add-on (accounts on usage-based billing always qualify), the user's Meta ads (boosted/dark posts) are included too. There's one row per (ad, placement-with-comments): an ad that runs on both Facebook feed and Instagram feed produces up to two rows (the Page dark post and the IG media have separate comment threads), each flagged `isAd: true` with `adId` and `placement` (`id` is `{adId}:{placement}`). Use `?platform=metaads` to return *only* ad rows; passing `facebook`/`instagram` returns *organic* posts only (no ads); omitting `platform` returns both. Fetch a row's thread from GET /v1/ads/{adId}/comments?placement={placement}. Ad comment counts are read with the Marketing API token (Facebook side) or the connected Instagram account's token (Instagram side); a row whose count can't be read is omitted.  Pagination walks each account's platform listing. Following `nextCursor` reaches past the first page on Facebook, Instagram, Threads, LinkedIn and YouTube, since they are the platforms that support a server-side date window; on the others the listing stops at its first page. Cursor pagination is only coherent for the default sort (`sortBy=date`, `sortOrder=desc`): with `sortOrder=asc`, or with `sortBy=comments`, the cursor filter does not match the sort order and the second page is unreliable.  `nextCursor` is opaque: pass it back verbatim, never construct or parse it, its composition may change without notice. Because each page re-queries a live window, results can still shift between requests, so dedupe by `id` on the client.  `commentCount` semantics differ by platform: YouTube's includes replies, Facebook's counts top-level comments only. 
     # @param [Hash] opts the optional parameters
     # @option opts [String] :profile_id Filter by profile ID
-    # @option opts [String] :platform Filter by platform. `metaads` is a synthetic value meaning the user's ads (boosted/dark posts) only; `facebook`/`instagram` return organic posts only.
+    # @option opts [String] :platform Filter by platform. `metaads` is a synthetic value meaning the user's ads (boosted/dark posts) only; `facebook`/`instagram` return organic posts only. `tiktok` covers accounts connected through the TikTok Business app only; developer-app TikTok accounts are returned under `meta.accountsSkipped`.
     # @option opts [Integer] :min_comments Minimum comment count
     # @option opts [Time] :since Posts created after this date
     # @option opts [String] :sort_by Sort field (default to 'date')
@@ -535,7 +535,7 @@ module Zernio
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: CommentsApi.list_inbox_comments ...'
       end
-      allowable_values = ["facebook", "instagram", "twitter", "bluesky", "threads", "youtube", "linkedin", "reddit", "metaads"]
+      allowable_values = ["facebook", "instagram", "twitter", "bluesky", "threads", "youtube", "linkedin", "reddit", "tiktok", "metaads"]
       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/api/whats_app_api.rb

@@ -20,7 +20,7 @@ module Zernio
       @api_client = api_client
     end
     # Add participants
-    # Add participants to a WhatsApp group. Maximum 8 participants per request.  Not available on [Coexistence](/platforms/whatsapp/connection#whatsapp-business-app-coexistence) numbers. Requires a Cloud API-only number. 
+    # Add participants to a WhatsApp group. Maximum 8 participants per request. A group holds at most 8 participants in total (a Meta limit), so later requests cannot grow a group past 8. Meta documents groups as invite-only, so people normally join through the group's invite link.  Not available on [Coexistence](/platforms/whatsapp/connection#whatsapp-business-app-coexistence) numbers. Requires a Cloud API-only number. 
     # @param group_id [String] Group ID
     # @param account_id [String] WhatsApp account ID
     # @param add_whats_app_group_participants_request [AddWhatsAppGroupParticipantsRequest] 
@@ -32,7 +32,7 @@ module Zernio
     end
 
     # Add participants
-    # Add participants to a WhatsApp group. Maximum 8 participants per request.  Not available on [Coexistence](/platforms/whatsapp/connection#whatsapp-business-app-coexistence) numbers. Requires a Cloud API-only number. 
+    # Add participants to a WhatsApp group. Maximum 8 participants per request. A group holds at most 8 participants in total (a Meta limit), so later requests cannot grow a group past 8. Meta documents groups as invite-only, so people normally join through the group's invite link.  Not available on [Coexistence](/platforms/whatsapp/connection#whatsapp-business-app-coexistence) numbers. Requires a Cloud API-only number. 
     # @param group_id [String] Group ID
     # @param account_id [String] WhatsApp account ID
     # @param add_whats_app_group_participants_request [AddWhatsAppGroupParticipantsRequest] 

data/lib/zernio-sdk/version.rb

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

data/openapi.yaml

@@ -31327,8 +31327,8 @@ paths:
           description: Filter by profile ID
         - name: platform
           in: query
-          schema: { type: string, enum: [facebook, instagram, twitter, bluesky, threads, youtube, linkedin, reddit, metaads] }
-          description: "Filter by platform. `metaads` is a synthetic value meaning the user's ads (boosted/dark posts) only; `facebook`/`instagram` return organic posts only."
+          schema: { type: string, enum: [facebook, instagram, twitter, bluesky, threads, youtube, linkedin, reddit, tiktok, metaads] }
+          description: "Filter by platform. `metaads` is a synthetic value meaning the user's ads (boosted/dark posts) only; `facebook`/`instagram` return organic posts only. `tiktok` covers accounts connected through the TikTok Business app only; developer-app TikTok accounts are returned under `meta.accountsSkipped`."
         - name: minComments
           in: query
           schema: { type: integer, minimum: 0 }
@@ -40199,7 +40199,7 @@ paths:
       tags: [WhatsApp]
       summary: Add participants
       description: |
-        Add participants to a WhatsApp group. Maximum 8 participants per request.
+        Add participants to a WhatsApp group. Maximum 8 participants per request. A group holds at most 8 participants in total (a Meta limit), so later requests cannot grow a group past 8. Meta documents groups as invite-only, so people normally join through the group's invite link.
 
         Not available on [Coexistence](/platforms/whatsapp/connection#whatsapp-business-app-coexistence) numbers. Requires a Cloud API-only number.
       security:

data/spec/api/comments_api_spec.rb

@@ -123,7 +123,7 @@ describe 'CommentsApi' do
   # Returns posts with comment counts from all connected accounts. Aggregates data across multiple accounts.  Responses are cached for up to 10 minutes, so the feed may lag new comments by that window. Do not poll this endpoint for real-time updates: subscribe to the `comment.received` webhook, which fires for every new comment across your posts and carries the post reference needed to keep this list current.  For users with the Ads add-on (accounts on usage-based billing always qualify), the user's Meta ads (boosted/dark posts) are included too. There's one row per (ad, placement-with-comments): an ad that runs on both Facebook feed and Instagram feed produces up to two rows (the Page dark post and the IG media have separate comment threads), each flagged `isAd: true` with `adId` and `placement` (`id` is `{adId}:{placement}`). Use `?platform=metaads` to return *only* ad rows; passing `facebook`/`instagram` returns *organic* posts only (no ads); omitting `platform` returns both. Fetch a row's thread from GET /v1/ads/{adId}/comments?placement={placement}. Ad comment counts are read with the Marketing API token (Facebook side) or the connected Instagram account's token (Instagram side); a row whose count can't be read is omitted.  Pagination walks each account's platform listing. Following `nextCursor` reaches past the first page on Facebook, Instagram, Threads, LinkedIn and YouTube, since they are the platforms that support a server-side date window; on the others the listing stops at its first page. Cursor pagination is only coherent for the default sort (`sortBy=date`, `sortOrder=desc`): with `sortOrder=asc`, or with `sortBy=comments`, the cursor filter does not match the sort order and the second page is unreliable.  `nextCursor` is opaque: pass it back verbatim, never construct or parse it, its composition may change without notice. Because each page re-queries a live window, results can still shift between requests, so dedupe by `id` on the client.  `commentCount` semantics differ by platform: YouTube's includes replies, Facebook's counts top-level comments only. 
   # @param [Hash] opts the optional parameters
   # @option opts [String] :profile_id Filter by profile ID
-  # @option opts [String] :platform Filter by platform. `metaads` is a synthetic value meaning the user's ads (boosted/dark posts) only; `facebook`/`instagram` return organic posts only.
+  # @option opts [String] :platform Filter by platform. `metaads` is a synthetic value meaning the user's ads (boosted/dark posts) only; `facebook`/`instagram` return organic posts only. `tiktok` covers accounts connected through the TikTok Business app only; developer-app TikTok accounts are returned under `meta.accountsSkipped`.
   # @option opts [Integer] :min_comments Minimum comment count
   # @option opts [Time] :since Posts created after this date
   # @option opts [String] :sort_by Sort field

data/spec/api/whats_app_api_spec.rb

@@ -34,7 +34,7 @@ describe 'WhatsAppApi' do
 
   # unit tests for add_whats_app_group_participants
   # Add participants
-  # Add participants to a WhatsApp group. Maximum 8 participants per request.  Not available on [Coexistence](/platforms/whatsapp/connection#whatsapp-business-app-coexistence) numbers. Requires a Cloud API-only number. 
+  # Add participants to a WhatsApp group. Maximum 8 participants per request. A group holds at most 8 participants in total (a Meta limit), so later requests cannot grow a group past 8. Meta documents groups as invite-only, so people normally join through the group's invite link.  Not available on [Coexistence](/platforms/whatsapp/connection#whatsapp-business-app-coexistence) numbers. Requires a Cloud API-only number. 
   # @param group_id Group ID
   # @param account_id WhatsApp account ID
   # @param add_whats_app_group_participants_request 

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: late-sdk
 version: !ruby/object:Gem::Version
-  version: 0.0.940
+  version: 0.0.942
 platform: ruby
 authors:
 - OpenAPI-Generator
@@ -6400,7 +6400,7 @@ files:
 - spec/models/you_tube_video_retention_response_retention_curve_inner_spec.rb
 - spec/models/you_tube_video_retention_response_spec.rb
 - spec/spec_helper.rb
-- zernio-sdk-0.0.940.gem
+- zernio-sdk-0.0.942.gem
 - zernio-sdk.gemspec
 homepage: https://openapi-generator.tech
 licenses: