late-sdk 0.0.1305 → 0.0.1306

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (41) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +3 -0
  3. data/docs/ConnectApi.md +70 -0
  4. data/docs/ConnectWhopAdsCredentials200Response.md +24 -0
  5. data/docs/ConnectWhopAdsCredentialsRequest.md +24 -0
  6. data/docs/TrackingTagsApi.md +1 -1
  7. data/lib/zernio-sdk/api/accounts_api.rb +1 -1
  8. data/lib/zernio-sdk/api/connect_api.rb +68 -0
  9. data/lib/zernio-sdk/api/tracking_tags_api.rb +2 -2
  10. data/lib/zernio-sdk/models/account_with_follower_stats.rb +2 -2
  11. data/lib/zernio-sdk/models/connect_whop_ads_credentials200_response.rb +176 -0
  12. data/lib/zernio-sdk/models/connect_whop_ads_credentials_request.rb +212 -0
  13. data/lib/zernio-sdk/models/create_tracking_tag201_response.rb +2 -2
  14. data/lib/zernio-sdk/models/get_tracking_tag200_response.rb +2 -2
  15. data/lib/zernio-sdk/models/get_tracking_tag_stats200_response.rb +2 -2
  16. data/lib/zernio-sdk/models/get_tracking_tag_store_install200_response.rb +2 -2
  17. data/lib/zernio-sdk/models/install_tracking_tag_on_store200_response.rb +2 -2
  18. data/lib/zernio-sdk/models/list_tracking_tags200_response.rb +2 -2
  19. data/lib/zernio-sdk/models/remove_tracking_tag_from_store200_response.rb +2 -2
  20. data/lib/zernio-sdk/models/social_account.rb +2 -2
  21. data/lib/zernio-sdk/models/tracking_tag.rb +2 -2
  22. data/lib/zernio-sdk/version.rb +1 -1
  23. data/lib/zernio-sdk.rb +2 -0
  24. data/openapi.yaml +1 -1
  25. data/spec/api/connect_api_spec.rb +12 -0
  26. data/spec/api/tracking_tags_api_spec.rb +1 -1
  27. data/spec/models/account_with_follower_stats_spec.rb +1 -1
  28. data/spec/models/connect_whop_ads_credentials200_response_spec.rb +54 -0
  29. data/spec/models/connect_whop_ads_credentials_request_spec.rb +54 -0
  30. data/spec/models/create_tracking_tag201_response_spec.rb +1 -1
  31. data/spec/models/get_tracking_tag200_response_spec.rb +1 -1
  32. data/spec/models/get_tracking_tag_stats200_response_spec.rb +1 -1
  33. data/spec/models/get_tracking_tag_store_install200_response_spec.rb +1 -1
  34. data/spec/models/install_tracking_tag_on_store200_response_spec.rb +1 -1
  35. data/spec/models/list_tracking_tags200_response_spec.rb +1 -1
  36. data/spec/models/remove_tracking_tag_from_store200_response_spec.rb +1 -1
  37. data/spec/models/social_account_spec.rb +1 -1
  38. data/spec/models/tracking_tag_spec.rb +1 -1
  39. data/zernio-sdk-0.0.1306.gem +0 -0
  40. metadata +10 -2
  41. data/zernio-sdk-0.0.1305.gem +0 -0
@@ -203,6 +203,18 @@ describe 'ConnectApi' do
203
203
  end
204
204
  end
205
205
 
206
+ # unit tests for connect_whop_ads_credentials
207
+ # Connect a Whop account
208
+ # Connect a Whop account with an Account API key from the Whop dashboard (Developer > API keys). The key only has to be able to read its own account: Zernio calls `GET /accounts/me` once to learn the account id (`biz_...`) and name, then stores the key. What the connection unlocks today is the Whop Pixel through the tracking-tags API: the account id is the pixel, so `GET /v1/accounts/{accountId}/tracking-tags` lists it and `POST .../tracking-tags/{biz_...}/install` puts it on a Shopify store or WordPress site. Whop campaigns are not managed through Zernio. One Whop account per profile.
209
+ # @param connect_whop_ads_credentials_request
210
+ # @param [Hash] opts the optional parameters
211
+ # @return [ConnectWhopAdsCredentials200Response]
212
+ describe 'connect_whop_ads_credentials test' do
213
+ it 'should work' do
214
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
215
+ end
216
+ end
217
+
206
218
  # unit tests for connect_word_press_with_application_password
207
219
  # Connect self-hosted WordPress with an application password
208
220
  # Connects one self-hosted WordPress site using a WordPress username and application password. `siteUrl` must use HTTPS and may include the path where WordPress is installed. Zernio discovers the REST API, verifies the credentials and required post/media/taxonomy capabilities, then stores the password encrypted. Create an application password in the WordPress user's profile; do not send the user's login password. Reconnecting the same site and profile updates the connection in place.
@@ -175,7 +175,7 @@ describe 'TrackingTagsApi' do
175
175
 
176
176
  # unit tests for install_tracking_tag_on_store
177
177
  # Install on a Shopify store or WordPress site
178
- # Puts the Meta pixel on a connected Shopify store's storefront and checkout through Zernio's Shopify web pixel (a Shopify app pixel, no theme edits). The store then sends PageView, ViewContent, AddToCart, Search, InitiateCheckout, AddPaymentInfo and Purchase (with value, currency, content_ids and contents) to the pixel, each with an event id. Purchase uses `shopify_order_{orderId}` as its event id, so a Conversions API Purchase you send for the same order with that `eventId` is deduplicated by Meta. Idempotent: a store runs one Zernio web pixel holding one tag per platform, so calling it again updates the install, installing a different tag of the same platform replaces the previous one (reported in `replacedTagId`), and other platforms' tags are kept. Events respect the store's customer privacy settings (marketing consent). `accountId` is the Meta ads account that owns the pixel (`tagId`); `storeAccountId` is the Shopify account. OpenAI Ads on Shopify: each event is sent through OpenAI's documented image tag (`GET https://bzr.openai.com/v1/sdk/events`) as `page_viewed`, `contents_viewed`, `items_added`, `checkout_started`, `order_created`, and custom events `search` and `addpaymentinfo` (lowercase, so a Conversions API Search/AddPaymentInfo with the same event id deduplicates). Amounts are sent in the currency's minor unit. The landing page's `oppref` click id is kept in the `__oppref` cookie for 30 days and sent with every event. The image tag cannot carry the `__obref` browser id (OpenAI rejects the parameter), and the search text is never sent. On WordPress the widget holds the official `oaiq` base code and a `page_viewed` call. Stores connected before pixel support must re-approve the Zernio app: the call then answers 409 `reconnect_required` with `details.authUrl` to send the merchant to (the Shopify account id stays the same). Platforms without an install path return 501. **WordPress** (`storeAccountId` is a connected WordPress.com or self-hosted site): Zernio adds a Custom HTML widget with the Meta pixel base code (fbevents.js, `init`, `PageView`) to a widget area of the active theme (a footer area when there is one, else the first active area; pass `sidebarId` to choose), then reads the widget back to confirm WordPress kept the `<script>` tag. The widget carries a Zernio marker, so the call is idempotent per pixel: repeating it updates or moves the same widget, and pixel code the site owner pasted by hand is never touched. Several pixels can run side by side (one widget each). When the site cannot run the pixel, nothing is left behind and the call answers 422 `tracking_tag_install_blocked` with `details.reason`: - `insufficient_permissions`: the connected user lacks `edit_theme_options` (needs Administrator). - `scripts_stripped`: WordPress removed the script (the user lacks `unfiltered_html`, e.g. a multisite admin who is not a Super Admin, or `DISALLOW_UNFILTERED_HTML` is set). - `wordpress_com_plan`: a WordPress.com plan that strips scripts (plans without plugins). - `no_widget_areas`: the theme has no widget areas (block themes such as Twenty Twenty-Five). - `widgets_api_unavailable`: no widgets REST API (WordPress older than 5.8, or disabled). The `error` message names the manual alternative (Meta's official WordPress plugin). With `verifyHomepage` (default true) the homepage is fetched afterwards and `homepageCheck` says whether the pixel is visible; `not_found` can be a stale page cache, the widget read-back is authoritative. **LinkedIn** (`linkedinads`): Shopify sends every page view to the Insight Tag, plus each store event that has an enabled event-specific Insight Tag conversion rule of the matching type (view_content = VIEW_CONTENT, add_to_cart = ADD_TO_CART, search = SEARCH, initiate_checkout = START_CHECKOUT, add_payment_info = ADD_BILLING_INFO, purchase = PURCHASE). Each conversion carries the event id; Purchase uses `shopify_order_{orderId}`, so a Conversions API event sent to a separate CONVERSIONS_API rule with that `eventId` is deduplicated by LinkedIn. Conversions API rules cannot be fired from a page, and no rule is created for you. The `li_fat_id` click id is read from the landing URL and kept in a first-party cookie for 30 days. WordPress gets LinkedIn's base code, which records page views. **Pinterest (platform `pinterestads`)**: Shopify sends `pagevisit`, `viewcontent`, `addtocart`, `search`, `initiatecheckout`, `addpaymentinfo` and `checkout` to the tag, each with `event_id` (Purchase: `shopify_order_{orderId}`, for dedup with the Pinterest Conversions API), value, currency, order quantity and line items, plus the `epik` click id kept in the `_epik` cookie. WordPress gets Pinterest's base code (core.js, `load`, `page`) with a `pagevisit` event; the manual fallback is the official Pinterest for WooCommerce plugin (WooCommerce stores).
178
+ # Puts the Meta pixel on a connected Shopify store's storefront and checkout through Zernio's Shopify web pixel (a Shopify app pixel, no theme edits). The store then sends PageView, ViewContent, AddToCart, Search, InitiateCheckout, AddPaymentInfo and Purchase (with value, currency, content_ids and contents) to the pixel, each with an event id. Purchase uses `shopify_order_{orderId}` as its event id, so a Conversions API Purchase you send for the same order with that `eventId` is deduplicated by Meta. Idempotent: a store runs one Zernio web pixel holding one tag per platform, so calling it again updates the install, installing a different tag of the same platform replaces the previous one (reported in `replacedTagId`), and other platforms' tags are kept. Events respect the store's customer privacy settings (marketing consent). `accountId` is the Meta ads account that owns the pixel (`tagId`); `storeAccountId` is the Shopify account. OpenAI Ads on Shopify: each event is sent through OpenAI's documented image tag (`GET https://bzr.openai.com/v1/sdk/events`) as `page_viewed`, `contents_viewed`, `items_added`, `checkout_started`, `order_created`, and custom events `search` and `addpaymentinfo` (lowercase, so a Conversions API Search/AddPaymentInfo with the same event id deduplicates). Amounts are sent in the currency's minor unit. The landing page's `oppref` click id is kept in the `__oppref` cookie for 30 days and sent with every event. The image tag cannot carry the `__obref` browser id (OpenAI rejects the parameter), and the search text is never sent. On WordPress the widget holds the official `oaiq` base code and a `page_viewed` call. Whop (`whopads`, `tagId` = the Whop account id `biz_...`) on Shopify: events are posted to Whop's conversions endpoint (`https://t.whop.tw/conversions`) the way Whop's own Shopify pixel does: `page`, `view_content`, `add_to_cart`, `purchase` (with value and currency) and the custom `shopify_search_submitted`, `shopify_checkout_started` and `shopify_payment_info_submitted`, each with Whop's `shopify:<event>:<id>` event id so a store that also runs Whop's own pixel reports each event once. The visitor id is kept in Whop's `_wuid` cookie for two years. Whop records purchases itself only for checkouts on Whop, so Shopify orders are reported here. On WordPress the widget holds the official snippet with `whop.setScope` and `whop.track(\"page\")`. Stores connected before pixel support must re-approve the Zernio app: the call then answers 409 `reconnect_required` with `details.authUrl` to send the merchant to (the Shopify account id stays the same). Platforms without an install path return 501. **WordPress** (`storeAccountId` is a connected WordPress.com or self-hosted site): Zernio adds a Custom HTML widget with the Meta pixel base code (fbevents.js, `init`, `PageView`) to a widget area of the active theme (a footer area when there is one, else the first active area; pass `sidebarId` to choose), then reads the widget back to confirm WordPress kept the `<script>` tag. The widget carries a Zernio marker, so the call is idempotent per pixel: repeating it updates or moves the same widget, and pixel code the site owner pasted by hand is never touched. Several pixels can run side by side (one widget each). When the site cannot run the pixel, nothing is left behind and the call answers 422 `tracking_tag_install_blocked` with `details.reason`: - `insufficient_permissions`: the connected user lacks `edit_theme_options` (needs Administrator). - `scripts_stripped`: WordPress removed the script (the user lacks `unfiltered_html`, e.g. a multisite admin who is not a Super Admin, or `DISALLOW_UNFILTERED_HTML` is set). - `wordpress_com_plan`: a WordPress.com plan that strips scripts (plans without plugins). - `no_widget_areas`: the theme has no widget areas (block themes such as Twenty Twenty-Five). - `widgets_api_unavailable`: no widgets REST API (WordPress older than 5.8, or disabled). The `error` message names the manual alternative (Meta's official WordPress plugin). With `verifyHomepage` (default true) the homepage is fetched afterwards and `homepageCheck` says whether the pixel is visible; `not_found` can be a stale page cache, the widget read-back is authoritative. **LinkedIn** (`linkedinads`): Shopify sends every page view to the Insight Tag, plus each store event that has an enabled event-specific Insight Tag conversion rule of the matching type (view_content = VIEW_CONTENT, add_to_cart = ADD_TO_CART, search = SEARCH, initiate_checkout = START_CHECKOUT, add_payment_info = ADD_BILLING_INFO, purchase = PURCHASE). Each conversion carries the event id; Purchase uses `shopify_order_{orderId}`, so a Conversions API event sent to a separate CONVERSIONS_API rule with that `eventId` is deduplicated by LinkedIn. Conversions API rules cannot be fired from a page, and no rule is created for you. The `li_fat_id` click id is read from the landing URL and kept in a first-party cookie for 30 days. WordPress gets LinkedIn's base code, which records page views. **Pinterest (platform `pinterestads`)**: Shopify sends `pagevisit`, `viewcontent`, `addtocart`, `search`, `initiatecheckout`, `addpaymentinfo` and `checkout` to the tag, each with `event_id` (Purchase: `shopify_order_{orderId}`, for dedup with the Pinterest Conversions API), value, currency, order quantity and line items, plus the `epik` click id kept in the `_epik` cookie. WordPress gets Pinterest's base code (core.js, `load`, `page`) with a `pagevisit` event; the manual fallback is the official Pinterest for WooCommerce plugin (WooCommerce stores).
179
179
  # @param account_id
180
180
  # @param tag_id Tag id (`TrackingTag.id`).
181
181
  # @param install_tracking_tag_on_store_request
@@ -36,7 +36,7 @@ describe Zernio::AccountWithFollowerStats do
36
36
  describe 'test attribute "platform"' do
37
37
  it 'should work' do
38
38
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
39
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["tiktok", "instagram", "facebook", "youtube", "linkedin", "twitter", "threads", "pinterest", "reddit", "bluesky", "googlebusiness", "telegram", "snapchat", "discord", "slack", "whatsapp", "shopify", "wordpress", "linkedinads", "metaads", "pinterestads", "tiktokads", "xads", "googleads", "openaiads", "sms", "phone", "rcs"])
39
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["tiktok", "instagram", "facebook", "youtube", "linkedin", "twitter", "threads", "pinterest", "reddit", "bluesky", "googlebusiness", "telegram", "snapchat", "discord", "slack", "whatsapp", "shopify", "wordpress", "linkedinads", "metaads", "pinterestads", "tiktokads", "xads", "googleads", "openaiads", "sms", "phone", "rcs", "whopads"])
40
40
  # validator.allowable_values.each do |value|
41
41
  # expect { instance.platform = value }.not_to raise_error
42
42
  # end
@@ -0,0 +1,54 @@
1
+ =begin
2
+ #Zernio API
3
+
4
+ #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). Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id.
5
+
6
+ The version of the OpenAPI document: 1.223.0
7
+ Contact: support@zernio.com
8
+ Generated by: https://openapi-generator.tech
9
+ Generator version: 7.19.0
10
+
11
+ =end
12
+
13
+ require 'spec_helper'
14
+ require 'json'
15
+ require 'date'
16
+
17
+ # Unit tests for Zernio::ConnectWhopAdsCredentials200Response
18
+ # Automatically generated by openapi-generator (https://openapi-generator.tech)
19
+ # Please update as you see appropriate
20
+ describe Zernio::ConnectWhopAdsCredentials200Response do
21
+ #let(:instance) { Zernio::ConnectWhopAdsCredentials200Response.new }
22
+
23
+ describe 'test an instance of ConnectWhopAdsCredentials200Response' do
24
+ it 'should create an instance of ConnectWhopAdsCredentials200Response' do
25
+ # uncomment below to test the instance creation
26
+ #expect(instance).to be_instance_of(Zernio::ConnectWhopAdsCredentials200Response)
27
+ end
28
+ end
29
+
30
+ describe 'test attribute "account_id"' do
31
+ it 'should work' do
32
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
33
+ end
34
+ end
35
+
36
+ describe 'test attribute "whop_account_id"' do
37
+ it 'should work' do
38
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
39
+ end
40
+ end
41
+
42
+ describe 'test attribute "account_name"' do
43
+ it 'should work' do
44
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
45
+ end
46
+ end
47
+
48
+ describe 'test attribute "redirect_url"' do
49
+ it 'should work' do
50
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
51
+ end
52
+ end
53
+
54
+ end
@@ -0,0 +1,54 @@
1
+ =begin
2
+ #Zernio API
3
+
4
+ #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). Request ids: responses carry an X-Request-Id header with the id we log the request under. Quote it when reporting a problem. A valid x-request-id you send is reused as that id.
5
+
6
+ The version of the OpenAPI document: 1.223.0
7
+ Contact: support@zernio.com
8
+ Generated by: https://openapi-generator.tech
9
+ Generator version: 7.19.0
10
+
11
+ =end
12
+
13
+ require 'spec_helper'
14
+ require 'json'
15
+ require 'date'
16
+
17
+ # Unit tests for Zernio::ConnectWhopAdsCredentialsRequest
18
+ # Automatically generated by openapi-generator (https://openapi-generator.tech)
19
+ # Please update as you see appropriate
20
+ describe Zernio::ConnectWhopAdsCredentialsRequest do
21
+ #let(:instance) { Zernio::ConnectWhopAdsCredentialsRequest.new }
22
+
23
+ describe 'test an instance of ConnectWhopAdsCredentialsRequest' do
24
+ it 'should create an instance of ConnectWhopAdsCredentialsRequest' do
25
+ # uncomment below to test the instance creation
26
+ #expect(instance).to be_instance_of(Zernio::ConnectWhopAdsCredentialsRequest)
27
+ end
28
+ end
29
+
30
+ describe 'test attribute "api_key"' do
31
+ it 'should work' do
32
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
33
+ end
34
+ end
35
+
36
+ describe 'test attribute "profile_id"' do
37
+ it 'should work' do
38
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
39
+ end
40
+ end
41
+
42
+ describe 'test attribute "state"' do
43
+ it 'should work' do
44
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
45
+ end
46
+ end
47
+
48
+ describe 'test attribute "redirect_url"' do
49
+ it 'should work' do
50
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
51
+ end
52
+ end
53
+
54
+ end
@@ -30,7 +30,7 @@ describe Zernio::CreateTrackingTag201Response do
30
30
  describe 'test attribute "platform"' do
31
31
  it 'should work' do
32
32
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
33
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "openaiads", "tiktokads", "googleads", "xads", "linkedinads", "pinterestads"])
33
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "openaiads", "tiktokads", "googleads", "xads", "linkedinads", "pinterestads", "whopads"])
34
34
  # validator.allowable_values.each do |value|
35
35
  # expect { instance.platform = value }.not_to raise_error
36
36
  # end
@@ -30,7 +30,7 @@ describe Zernio::GetTrackingTag200Response do
30
30
  describe 'test attribute "platform"' do
31
31
  it 'should work' do
32
32
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
33
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "tiktokads", "googleads", "xads", "openaiads", "linkedinads", "pinterestads"])
33
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "tiktokads", "googleads", "xads", "openaiads", "linkedinads", "pinterestads", "whopads"])
34
34
  # validator.allowable_values.each do |value|
35
35
  # expect { instance.platform = value }.not_to raise_error
36
36
  # end
@@ -30,7 +30,7 @@ describe Zernio::GetTrackingTagStats200Response do
30
30
  describe 'test attribute "platform"' do
31
31
  it 'should work' do
32
32
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
33
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "tiktokads", "googleads", "xads", "openaiads", "linkedinads", "pinterestads"])
33
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "tiktokads", "googleads", "xads", "openaiads", "linkedinads", "pinterestads", "whopads"])
34
34
  # validator.allowable_values.each do |value|
35
35
  # expect { instance.platform = value }.not_to raise_error
36
36
  # end
@@ -30,7 +30,7 @@ describe Zernio::GetTrackingTagStoreInstall200Response do
30
30
  describe 'test attribute "platform"' do
31
31
  it 'should work' do
32
32
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
33
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "tiktokads", "googleads", "xads", "openaiads", "linkedinads", "pinterestads"])
33
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "tiktokads", "googleads", "xads", "openaiads", "linkedinads", "pinterestads", "whopads"])
34
34
  # validator.allowable_values.each do |value|
35
35
  # expect { instance.platform = value }.not_to raise_error
36
36
  # end
@@ -30,7 +30,7 @@ describe Zernio::InstallTrackingTagOnStore200Response do
30
30
  describe 'test attribute "platform"' do
31
31
  it 'should work' do
32
32
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
33
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "tiktokads", "googleads", "xads", "openaiads", "linkedinads", "pinterestads"])
33
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "tiktokads", "googleads", "xads", "openaiads", "linkedinads", "pinterestads", "whopads"])
34
34
  # validator.allowable_values.each do |value|
35
35
  # expect { instance.platform = value }.not_to raise_error
36
36
  # end
@@ -30,7 +30,7 @@ describe Zernio::ListTrackingTags200Response do
30
30
  describe 'test attribute "platform"' do
31
31
  it 'should work' do
32
32
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
33
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "openaiads", "tiktokads", "googleads", "xads", "linkedinads", "pinterestads"])
33
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "openaiads", "tiktokads", "googleads", "xads", "linkedinads", "pinterestads", "whopads"])
34
34
  # validator.allowable_values.each do |value|
35
35
  # expect { instance.platform = value }.not_to raise_error
36
36
  # end
@@ -30,7 +30,7 @@ describe Zernio::RemoveTrackingTagFromStore200Response do
30
30
  describe 'test attribute "platform"' do
31
31
  it 'should work' do
32
32
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
33
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "tiktokads", "googleads", "xads", "openaiads", "linkedinads", "pinterestads"])
33
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "tiktokads", "googleads", "xads", "openaiads", "linkedinads", "pinterestads", "whopads"])
34
34
  # validator.allowable_values.each do |value|
35
35
  # expect { instance.platform = value }.not_to raise_error
36
36
  # end
@@ -36,7 +36,7 @@ describe Zernio::SocialAccount do
36
36
  describe 'test attribute "platform"' do
37
37
  it 'should work' do
38
38
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
39
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["tiktok", "instagram", "facebook", "youtube", "linkedin", "twitter", "threads", "pinterest", "reddit", "bluesky", "googlebusiness", "telegram", "snapchat", "discord", "slack", "whatsapp", "shopify", "wordpress", "linkedinads", "metaads", "pinterestads", "tiktokads", "xads", "googleads", "openaiads", "sms", "phone", "rcs"])
39
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["tiktok", "instagram", "facebook", "youtube", "linkedin", "twitter", "threads", "pinterest", "reddit", "bluesky", "googlebusiness", "telegram", "snapchat", "discord", "slack", "whatsapp", "shopify", "wordpress", "linkedinads", "metaads", "pinterestads", "tiktokads", "xads", "googleads", "openaiads", "sms", "phone", "rcs", "whopads"])
40
40
  # validator.allowable_values.each do |value|
41
41
  # expect { instance.platform = value }.not_to raise_error
42
42
  # end
@@ -54,7 +54,7 @@ describe Zernio::TrackingTag do
54
54
  describe 'test attribute "platform"' do
55
55
  it 'should work' do
56
56
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
57
- # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "openaiads", "tiktokads", "googleads", "xads", "linkedinads", "pinterestads"])
57
+ # validator = Petstore::EnumTest::EnumAttributeValidator.new('String', ["metaads", "openaiads", "tiktokads", "googleads", "xads", "linkedinads", "pinterestads", "whopads"])
58
58
  # validator.allowable_values.each do |value|
59
59
  # expect { instance.platform = value }.not_to raise_error
60
60
  # end
Binary file
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: late-sdk
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.1305
4
+ version: 0.0.1306
5
5
  platform: ruby
6
6
  authors:
7
7
  - OpenAPI-Generator
@@ -439,6 +439,8 @@ files:
439
439
  - docs/ConnectWhatsAppEmbeddedSignup200Response.md
440
440
  - docs/ConnectWhatsAppEmbeddedSignup200ResponseAccount.md
441
441
  - docs/ConnectWhatsAppEmbeddedSignupRequest.md
442
+ - docs/ConnectWhopAdsCredentials200Response.md
443
+ - docs/ConnectWhopAdsCredentialsRequest.md
442
444
  - docs/ConnectWordPressWithApplicationPassword200Response.md
443
445
  - docs/ConnectWordPressWithApplicationPassword200ResponseAccount.md
444
446
  - docs/ConnectWordPressWithApplicationPasswordRequest.md
@@ -3259,6 +3261,8 @@ files:
3259
3261
  - lib/zernio-sdk/models/connect_whats_app_embedded_signup200_response.rb
3260
3262
  - lib/zernio-sdk/models/connect_whats_app_embedded_signup200_response_account.rb
3261
3263
  - lib/zernio-sdk/models/connect_whats_app_embedded_signup_request.rb
3264
+ - lib/zernio-sdk/models/connect_whop_ads_credentials200_response.rb
3265
+ - lib/zernio-sdk/models/connect_whop_ads_credentials_request.rb
3262
3266
  - lib/zernio-sdk/models/connect_word_press_with_application_password200_response.rb
3263
3267
  - lib/zernio-sdk/models/connect_word_press_with_application_password200_response_account.rb
3264
3268
  - lib/zernio-sdk/models/connect_word_press_with_application_password_request.rb
@@ -6018,6 +6022,8 @@ files:
6018
6022
  - spec/models/connect_whats_app_embedded_signup200_response_account_spec.rb
6019
6023
  - spec/models/connect_whats_app_embedded_signup200_response_spec.rb
6020
6024
  - spec/models/connect_whats_app_embedded_signup_request_spec.rb
6025
+ - spec/models/connect_whop_ads_credentials200_response_spec.rb
6026
+ - spec/models/connect_whop_ads_credentials_request_spec.rb
6021
6027
  - spec/models/connect_word_press_with_application_password200_response_account_spec.rb
6022
6028
  - spec/models/connect_word_press_with_application_password200_response_spec.rb
6023
6029
  - spec/models/connect_word_press_with_application_password_request_spec.rb
@@ -8353,7 +8359,7 @@ files:
8353
8359
  - spec/models/you_tube_video_retention_response_retention_curve_inner_spec.rb
8354
8360
  - spec/models/you_tube_video_retention_response_spec.rb
8355
8361
  - spec/spec_helper.rb
8356
- - zernio-sdk-0.0.1305.gem
8362
+ - zernio-sdk-0.0.1306.gem
8357
8363
  - zernio-sdk.gemspec
8358
8364
  homepage: https://openapi-generator.tech
8359
8365
  licenses:
@@ -9066,6 +9072,7 @@ test_files:
9066
9072
  - spec/models/list_google_business_locations200_response_locations_inner_spec.rb
9067
9073
  - spec/models/create_broadcast_request_template_variable_mapping_value_spec.rb
9068
9074
  - spec/models/fetch_google_business_verification_options200_response_spec.rb
9075
+ - spec/models/connect_whop_ads_credentials_request_spec.rb
9069
9076
  - spec/models/get_google_business_search_keywords400_response_spec.rb
9070
9077
  - spec/models/list_branded_calling_identities200_response_spec.rb
9071
9078
  - spec/models/business_agent_faq_spec.rb
@@ -9313,6 +9320,7 @@ test_files:
9313
9320
  - spec/models/list_ad_keywords200_response_spec.rb
9314
9321
  - spec/models/create_tracking_tag_event_request_spec.rb
9315
9322
  - spec/models/discord_platform_data_embeds_inner_fields_inner_spec.rb
9323
+ - spec/models/connect_whop_ads_credentials200_response_spec.rb
9316
9324
  - spec/models/list_ad_audiences200_response_spec.rb
9317
9325
  - spec/models/create_google_asset_group201_response_asset_group_spec.rb
9318
9326
  - spec/models/create_blog_article_request_spec.rb
Binary file