klaviyo_sdk 1.0.1.20220329 → 1.0.4.20220329

data/spec/api/lists_segments_api_spec.rb

@@ -1,239 +0,0 @@
-=begin
-#Klaviyo API
-
-#Empowering creators to own their destiny
-
-The version of the OpenAPI document: 2022.03.29
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.4.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Client::ListsSegmentsApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'ListsSegmentsApi' do
-  before do
-    # run before each test
-    @api_instance = Client::ListsSegmentsApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of ListsSegmentsApi' do
-    it 'should create an instance of ListsSegmentsApi' do
-      expect(@api_instance).to be_instance_of(Client::ListsSegmentsApi)
-    end
-  end
-
-  # unit tests for add_members
-  # Add Members to a List
-  # Adds profiles to a list. This endpoint is functionally equivalent to adding profiles to a list via a CSV upload and will immediately add profiles to the list. If you would like to subscribe profiles to a list and use the double opt-in settings for the list, please use the subscribe endpoint.
-  # @param list_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [InlineObject4] :inline_object4 
-  # @return [Array<Hash<String, Object>>]
-  describe 'add_members test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for create_list
-  # Create List
-  # Creates a new list.
-  # @param list_name 
-  # @param [Hash] opts the optional parameters
-  # @return [Hash<String, Object>]
-  describe 'create_list test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for delete_list
-  # Delete List
-  # Deletes a list from an account. This is a destructive operation and cannot be undone. It will also remove flow triggers associated with the list.
-  # @param list_id 
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'delete_list test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for exclude_globally
-  # Exclude Profile From All Email
-  # Marks a person as excluded from all email. This works the same way as manually excluding someone via the excluded people page. Someone who is excluded will no longer receive any campaigns or flow emails.
-  # @param email 
-  # @param [Hash] opts the optional parameters
-  # @return [Hash<String, Object>]
-  describe 'exclude_globally test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_global_exclusions
-  # Get Global Exclusions &amp; Unsubscribes
-  # Returns global exclusions/unsubscribes. Global exclusions are distinct from list exclusions in that these email addresses will not receive any emails from any list. Typically, when someone unsubscribes from a campaign, they are only unsubscribed from that list and are not globally unsubscribed.
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :reason Filter results based on the reason for someone being excluded. The possible values are &#x60;unsubscribed&#x60;, &#x60;bounced&#x60;, &#x60;invalid_email&#x60;, &#x60;reported_spam&#x60; and &#x60;manually_excluded&#x60;. Only a single value may be specified at a time. Defaults to return all profiles regardless of reason.
-  # @option opts [String] :sort Sort order to apply to results, either ascending or descending. Valid values are &#x60;asc&#x60; or &#x60;desc&#x60;. Defaults to &#x60;asc&#x60;.
-  # @option opts [Integer] :count For pagination, the number of results to return. Default &#x3D; 500
-  # @option opts [Integer] :page For pagination, which page of results to return. Default &#x3D; 0
-  # @return [GlobalExclusionResponseData]
-  describe 'get_global_exclusions test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_list_exclusions
-  # Get All Exclusions for a List
-  # Gets all of the emails and phone numbers that have been excluded from a list along with the exclusion reasons and exclusion time. This endpoint uses batching to return the records, so for a large list multiple calls will need to be made to get all of the records.
-  # @param list_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :marker A marker value returned by a previous GET call. Use this to grab the next batch of records.
-  # @return [Hash<String, Object>]
-  describe 'get_list_exclusions test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_list_info
-  # Get List Info
-  # Returns information about a list.
-  # @param list_id 
-  # @param [Hash] opts the optional parameters
-  # @return [Hash<String, Object>]
-  describe 'get_list_info test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_list_members
-  # Check if Profiles Are in a List
-  # Checks if one or more emails, phone numbers, or push tokens are in a given list. No distinction is made between a person not being in a given list, and not being present in Klaviyo at all. Can check up to a maximum of 100 emails at a time.
-  # @param list_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [CheckMembershipRequest] :check_membership_request 
-  # @return [Array<Hash<String, Object>>]
-  describe 'get_list_members test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_list_subscriptions
-  # Check if Profiles Are in a List and not Suppressed
-  # Checks if one or more emails are in a given list and not suppressed. No distinction is made between a person not being in a given list, and not being present in Klaviyo at all. Can check up to a maximum of 100 emails at a time.
-  # @param list_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [CheckMembershipRequest] :check_membership_request 
-  # @return [Array<Hash<String, Object>>]
-  describe 'get_list_subscriptions test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_lists
-  # Get Lists
-  # Returns a listing of all of the lists in an account.
-  # @param [Hash] opts the optional parameters
-  # @return [Array<Hash<String, Object>>]
-  describe 'get_lists test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_members
-  # Get List and Segment Members
-  # Gets all of the emails, phone numbers, and push tokens for profiles in a given list or segment
-  # @param list_or_segment_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :marker A marker value returned by a previous GET call. Use this to grab the next batch of records.
-  # @return [Hash<String, Object>]
-  describe 'get_members test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_segment_members
-  # Check if Profiles Are in a Segment
-  # Checks if one or more emails, phone numbers, or push tokens are in a given segment. No distinction is made between a person not being in a given segment, and not being present in Klaviyo at all. Can check up to a maximum of 100 emails at a time.
-  # @param segment_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [CheckMembershipRequest] :check_membership_request 
-  # @return [Array<Hash<String, Object>>]
-  describe 'get_segment_members test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for remove_members
-  # Remove Profiles From List
-  # Removes profiles from a list.
-  # @param list_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [InlineObject5] :inline_object5 
-  # @return [nil]
-  describe 'remove_members test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for subscribe
-  # Subscribe Profiles to List
-  # Subscribes profiles to a list. Profiles will be single or double opted into the specified list in accordance with that list’s settings. **Note:** If you have double opt-in enabled (default behavior), users will not be added to list until they opt-in, and so API will respond with an empty list: &#x60;[]&#x60;
-  # @param list_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [InlineObject3] :inline_object3 
-  # @return [Array<Object>]
-  describe 'subscribe test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for unsubscribe
-  # Unsubscribe Profiles From List
-  # Unsubscribes and removes profiles from a list.
-  # @param list_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [Hash<String, Object>] :request_body Unsubscribe and remove profiles from a list.
-  # @return [nil]
-  describe 'unsubscribe test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for update_list_name
-  # Update List Name
-  # Updates a list&#39;s name.
-  # @param list_id 
-  # @param list_name 
-  # @param [Hash] opts the optional parameters
-  # @return [nil]
-  describe 'update_list_name test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/spec/api/metrics_api_spec.rb

@@ -1,96 +0,0 @@
-=begin
-#Klaviyo API
-
-#Empowering creators to own their destiny
-
-The version of the OpenAPI document: 2022.03.29
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.4.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Client::MetricsApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'MetricsApi' do
-  before do
-    # run before each test
-    @api_instance = Client::MetricsApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of MetricsApi' do
-    it 'should create an instance of MetricsApi' do
-      expect(@api_instance).to be_instance_of(Client::MetricsApi)
-    end
-  end
-
-  # unit tests for get_metrics
-  # Get Metrics Info
-  # Returns a list of all the metrics in your account.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :page For pagination, which page of results to return. Default = 0
-  # @option opts [Integer] :count For pagination, the number of results to return. Default = 50 ; Max = 100
-  # @return [Hash<String, Object>]
-  describe 'get_metrics test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for metric_export
-  # Query Event Data
-  # Exports event data from Klaviyo, optionally filtering and segmenting on available event properties. Note that the only comparison operator currently supported is &#x60;&#x3D;&#x60;. To ensure a correct response, enter parameters in the curl request as they are ordered below:
-  # @param metric_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :start_date  Beginning of timeframe to pull event data for. The default value is 1 month ago. Can also accept a 10-digit UNIX timestamp. When sending a &#x60;start_date&#x60;, you must also send an &#x60;end_date&#x60;  Ex: &#x60;1610524800&#x60; OR &#x60;2021-01-13&#x60; 
-  # @option opts [String] :end_date  End of timeframe to pull event data for. The default is the current day, or 1 month from start_date, whichever is sooner. Can also accept a 10-digit UNIX timestamp. When sending an &#x60;end_date&#x60;, you must also send a &#x60;start_date&#x60;. Must be *at most* 31 days after &#x60;start_date&#x60;  Ex: &#x60;1612080000&#x60; OR &#x60;2021-01-31&#x60; 
-  # @option opts [String] :unit Granularity to bucket data points into - one of &#x60;day&#x60;, &#x60;week&#x60;, or &#x60;month&#x60;. Defaults to &#x60;day&#x60;.
-  # @option opts [String] :measurement  Type of metric to fetch - one of &#x60;unique&#x60;, &#x60;count&#x60;, &#x60;value&#x60;, or &#x60;sum&#x60;. Defaults to &#x60;count&#x60;. For &#x60;sum&#x60; a property name to operate on must be supplied as a JSON-encoded list like &#x60;[\&quot;sum\&quot;,\&quot;ItemCount\&quot;]&#x60; 
-  # @option opts [String] :where Optional, JSON-encoded list. Conditions to use to filter the set of events. A max of 1 condition can be given. &#x60;where&#x60; and &#x60;by&#x60; parameters cannot be specified at the same time.  ex: &#x60;[[\&quot;$attributed_flow\&quot;,\&quot;&#x3D;\&quot;,\&quot;FLOW_ID\&quot;]]&#x60; 
-  # @option opts [String] :by The name of a property to segment the event data on. &#x60;where&#x60; and &#x60;by&#x60; parameters cannot be specified at the same time. Cannot be used alongside &#x60;where&#x60; parameter.
-  # @option opts [Integer] :count Maximum number of segments to return. Default &#x3D; 25, **MAX &#x3D; 1000**
-  # @return [MetricExport]
-  describe 'metric_export test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for metric_timeline
-  # Get Events for a Specific Metric
-  # Returns a batched timeline for one specific metric.
-  # @param metric_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :since Either a 10-digit Unix timestamp (UTC) to use as starting datetime, OR a pagination token obtained from the &#x60;next&#x60; attribute of a prior API call. For backwards compatibility, UUIDs will continue to be supported for a limited time. Defaults to current time.
-  # @option opts [Integer] :count Number of events to return in a batch. Max &#x3D; 100
-  # @option opts [String] :sort Sort order to apply to timeline, either descending or ascending. Valid values are &#x60;desc&#x60; or &#x60;asc&#x60;. Defaults to &#x60;desc&#x60;. Always descending when &#x60;since&#x60; is not sent, as &#x60;since&#x60; defaults to current time.
-  # @return [MetricTimeline]
-  describe 'metric_timeline test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for metrics_timeline
-  # Get Events for All Metrics
-  # Returns a batched timeline of all events in your account.
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :since Either a 10-digit Unix timestamp (UTC) to use as starting datetime, OR a pagination token obtained from the next attribute of a prior API call. For backwards compatibility, UUIDs will continue to be supported for a limited time. Defaults to current time.
-  # @option opts [Integer] :count Number of events to return in a batch. Default &#x3D; 50, Max &#x3D; 100
-  # @option opts [String] :sort Sort order to apply to timeline, either descending or ascending. Valid values are &#x60;desc&#x60; or &#x60;asc&#x60;. Defaults to &#x60;desc&#x60;. Always descending when &#x60;since&#x60; is not sent, as &#x60;since&#x60; defaults to current time.
-  # @return [MetricTimeline]
-  describe 'metrics_timeline test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/spec/api/profiles_api_spec.rb

@@ -1,103 +0,0 @@
-=begin
-#Klaviyo API
-
-#Empowering creators to own their destiny
-
-The version of the OpenAPI document: 2022.03.29
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.4.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Client::ProfilesApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'ProfilesApi' do
-  before do
-    # run before each test
-    @api_instance = Client::ProfilesApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of ProfilesApi' do
-    it 'should create an instance of ProfilesApi' do
-      expect(@api_instance).to be_instance_of(Client::ProfilesApi)
-    end
-  end
-
-  # unit tests for exchange
-  # Exchange ID for Profile ID
-  # Klaviyo's web tracking uses an encrypted identifier. However, there are many use cases that require developers to have access to a given profile's email or phone number. In such cases, developers can use this operation to exchange an encrypted identifier for a profile ID, which they can then use to retrieve the full profile data (by making a subsequent request to the `get-profiles` operation).  The `exchange_id` takes the following form:  `<IDENTIFIER>.<COMPANY_ID>`  The `exchange_id` appears in the url as follows:  `?_kx=<IDENTIFIER>.<COMPANY_ID>`
-  # @param [Hash] opts the optional parameters
-  # @option opts [InlineObject] :inline_object 
-  # @return [Hash<String, Object>]
-  describe 'exchange test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_profile
-  # Get Profile
-  # Retrieves all the data attributes for a person, based on the Klaviyo Person ID.
-  # @param person_id 
-  # @param [Hash] opts the optional parameters
-  # @return [Person]
-  describe 'get_profile test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for profile_metric_timeline
-  # Get Profile&#39;s Events for a Specific Metric
-  # Returns a person&#39;s batched timeline for one specific event type.
-  # @param person_id 
-  # @param metric_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :since Either a 10-digit Unix timestamp (UTC) to use as starting datetime, OR a pagination token obtained from the next attribute of a prior API call. For backwards compatibility, UUIDs will continue to be supported for a limited time. Defaults to current time.
-  # @option opts [Integer] :count Number of events to return in a batch.
-  # @option opts [String] :sort Sort order to apply to timeline, either descending or ascending. Valid values are &#x60;desc&#x60; or &#x60;asc&#x60;. Defaults to &#x60;desc&#x60;.
-  # @return [MetricTimeline]
-  describe 'profile_metric_timeline test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for profile_metrics_timeline
-  # Get Profile&#39;s Events for all Metrics
-  # Returns a batched timeline of all events for a person.
-  # @param person_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :since Either a 10-digit Unix timestamp (UTC) to use as starting datetime, OR a pagination token obtained from the next attribute of a prior API call. For backwards compatibility, UUIDs will continue to be supported for a limited time. Defaults to current time.
-  # @option opts [Integer] :count Number of events to return in a batch. Default &#x3D; 50, Max &#x3D; 100
-  # @option opts [String] :sort Sort order to apply to timeline, either descending or ascending. Valid values are &#x60;desc&#x60; or &#x60;asc&#x60;. Defaults to &#x60;desc&#x60;. Always descending when &#x60;since&#x60; is not sent, as &#x60;since&#x60; defaults to current time.
-  # @return [MetricTimeline]
-  describe 'profile_metrics_timeline test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for update_profile
-  # Update Profile
-  # NOTE: If you are interested in creating or updating profiles in Klaviyo, you should be using the Identify API instead. The best use-case for this route is changing a profiles&#39;s email address or other primary identifier after a profile already exists in Klaviyo.  Add or update one more more attributes for a Person, based on the Klaviyo Person ID. If a property already exists, it will be updated. If a property is not set for that record, it will be created.  You can update any attribute, by sending one or more attributes along their new values, as query parameters. Recommended attributes for this endpoint: &#x60;$email&#x60;, &#x60;$phone_number&#x60;, &#x60;$id&#x60; 
-  # @param person_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [Hash<String, Object>] :params 
-  # @return [Person]
-  describe 'update_profile test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/spec/api/templates_api_spec.rb

@@ -1,130 +0,0 @@
-=begin
-#Klaviyo API
-
-#Empowering creators to own their destiny
-
-The version of the OpenAPI document: 2022.03.29
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.4.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Client::TemplatesApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'TemplatesApi' do
-  before do
-    # run before each test
-    @api_instance = Client::TemplatesApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of TemplatesApi' do
-    it 'should create an instance of TemplatesApi' do
-      expect(@api_instance).to be_instance_of(Client::TemplatesApi)
-    end
-  end
-
-  # unit tests for clone_template
-  # Clone Template
-  # Creates a copy of a given template with a new name.
-  # @param template_id 
-  # @param name The new name of the email template.
-  # @param [Hash] opts the optional parameters
-  # @return [Template]
-  describe 'clone_template test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for create_template
-  # Create New Template
-  # Creates a new email template.
-  # @param name The name of the email template.
-  # @param html 
-  # @param [Hash] opts the optional parameters
-  # @return [Template]
-  describe 'create_template test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for delete_template
-  # Delete Template
-  # Deletes a given template.
-  # @param template_id 
-  # @param [Hash] opts the optional parameters
-  # @return [Hash<String, Object>]
-  describe 'delete_template test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for get_templates
-  # Get All Templates
-  # Returns a list of all the email templates you&#39;ve created. The templates are returned in sorted order by &#x60;name&#x60;.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :page For pagination, which page of results to return. Default &#x3D; 0
-  # @option opts [Integer] :count For pagination, the number of results to return. Max &#x3D; 100
-  # @return [Hash<String, Object>]
-  describe 'get_templates test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for render_template
-  # Render Template
-  # Renders the specified template with the provided data and return HTML and text versions of the email.
-  # @param template_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :context This is the context your email template will be rendered with. Email templates are rendered with contexts in a similar manner to how Django templates are rendered. This means that nested template variables can be referenced via dot notation and template variables without corresponding context values are treated as falsy and output nothing.
-  # @return [RenderedTemplate]
-  describe 'render_template test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for send_template
-  # Render and Send Template
-  # Renders the specified template with the provided data and send the contents in an email via the service specified. This API is intended to test templates only, and is rate limited to the following thresholds: 100/hour, 1,000/day.
-  # @param template_id 
-  # @param from_email 
-  # @param from_name 
-  # @param subject 
-  # @param to **Mixed**. string, or JSON encoded array of objects with \\\&quot;email\\\&quot; and \\\&quot;name\\\&quot; keys. &#x60;abraham.lincoln@klaviyo.com&#x60; OR &#x60;[{\\\&quot;name\\\&quot;:\\\&quot;Abraham Lincoln\\\&quot;,\\\&quot;email\\\&quot;:\\\&quot;abraham.lincoln@klaviyo.com\\\&quot;}]&#x60; 
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :context Optional, JSON object. This is the context your email template will be rendered with. Email templates are rendered with contexts in a similar manner to how Django templates are rendered. This means that nested template variables can be referenced via dot notation and template variables without corresponding context values are treated as falsy and output nothing. ex: &#x60;{ \\\&quot;name\\\&quot; : \\\&quot;George Washington\\\&quot;, \\\&quot;state\\\&quot; : \\\&quot;VA\\\&quot; }&#x60; 
-  # @return [RenderedTemplate]
-  describe 'send_template test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for update_template
-  # Update Template
-  # Updates the name and/or HTML content of a template. Only updates imported HTML templates; does not currently update drag &amp; drop templates.
-  # @param template_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :name The new name of the email template.
-  # @option opts [String] :html The new HTML content for this template.
-  # @return [Template]
-  describe 'update_template test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/spec/api/track_identify_api_spec.rb

@@ -1,83 +0,0 @@
-=begin
-#Klaviyo API
-
-#Empowering creators to own their destiny
-
-The version of the OpenAPI document: 2022.03.29
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.4.0
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Client::TrackIdentifyApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'TrackIdentifyApi' do
-  before do
-    # run before each test
-    @api_instance = Client::TrackIdentifyApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of TrackIdentifyApi' do
-    it 'should create an instance of TrackIdentifyApi' do
-      expect(@api_instance).to be_instance_of(Client::TrackIdentifyApi)
-    end
-  end
-
-  # unit tests for identify_get
-  # Identify Profile (Legacy)
-  # This endpoint is also used to identify a profile and update its properties without an associated event. It takes as input the same payload as the above POST request, but as a base64-encoded string passed as a query parameter. NOTE: This is offered for backwards compatibility; we recommend all new implementations use the POST approach above.    **EXAMPLE:**      ```   {       \"token\": \"PUBLIC_KEY\",       \"properties\": {         \"$email\": \"abraham.lincoln@klaviyo.com\",         \"$first_name\": \"Abraham\",         \"$last_name\": \"Lincoln\",         \"$city\": \"Springfield\",         \"$region\": \"Illinois\"       }   }   ```   Gets encoded into the following string, which is passed into the `data` parameter:    `eyJ0b2tlbiI6ICJQVUJMSUNfS0VZIiwicHJvcGVydGllcyI6IHsiJGVtYWlsIjogImFicmFoYW0ubGluY29sbkBrbGF2aXlvLmNvbSIsIiRmaXJzdF9uYW1lIjogIkFicmFoYW0iLCIkbGFzdF9uYW1lIjogIkxpbmNvbG4iLCIkY2l0eSI6ICJTcHJpbmdmaWVsZCIsIiRyZWdpb24iOiAiSWxsaW5vaXMifX0K`     
-  # @param data String representation of base64 encoded JSON object
-  # @param [Hash] opts the optional parameters
-  # @return [String]
-  describe 'identify_get test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for identify_post
-  # Identify Profile
-  # This endpoint is used to track and update properties about an individual without tracking an associated event. The following data is stored in a JSON object.     **JSON OBJECT STRUCTURE:**    __token: *string*__   This is your public API key.      __properties: *JSON Object or null*__   Properties of the profile to track/update. You must identify the person by their email using a $email key (or by their phone number using a `$phone_number` key if you have SMS-only contacts). Other than that, you can include any data you want and it can then be used to create segments of people. For example, if you wanted to create a list of people on trial plans, include a person's plan type in this JSON object so you can use that information later.         **SPECIAL FIELDS:**    The Klaviyo CRM has the following special fields you can set for customer **properties** with the **Identify** endpoint, to unlock additional functionality:      **$email:** _string_   **$first_name:** _string_   **$last_name:** _string_   **$phone_number:** _string; eg: \"+13239169023\"_   **$city:** _string_   **$region:** _string; state, or other region_   **$country:** _string_   **$zip:** _string_   **$image:** _string; url to a photo of a person_   **$consent:** _list of strings; eg: ['sms', 'email', 'web', 'directmail', 'mobile']_         **EXAMPLE:**      ```   {       \"token\": \"PUBLIC_KEY\",       \"properties\": {         \"$email\": \"abraham.lincoln@klaviyo.com\",         \"$first_name\": \"Abraham\",         \"$last_name\": \"Lincoln\",         \"$city\": \"Springfield\",         \"$region\": \"Illinois\"       }   }    
-  # @param data 
-  # @param [Hash] opts the optional parameters
-  # @return [String]
-  describe 'identify_post test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for track_get
-  # Track Profile Activity (Legacy)
-  # This endpoint is also used to track a profile's activity. It takes as input the same payload as the above POST request, but as a base64-encoded string passed as a query parameter. NOTE: This is offered for backwards compatibility; we recommend all new implementations use the POST approach above.      **EXAMPLE:**      ```   {     \"token\": \"PUBLIC_KEY\",     \"event\": \"Ordered Product\",     \"customer_properties\": {       \"$email\": \"abraham.lincoln@klaviyo.com\"     },     \"properties\": {       \"item_name\": \"Boots\",       \"$value\": 100     }   }    ```   Gets encoded into the following string, which is passed into the `data` parameter:    `eyJ0b2tlbiI6ICJQVUJMSUNfS0VZIiwiZXZlbnQiOiAiT3JkZXJlZEl0ZW0iLCJjdXN0b21lcl9wcm9wZXJ0aWVzIjogeyIkZW1haWwiOiAiYWJyYWhhbS5saW5jb2xuQGtsYXZpeW8uY29tIn0sInByb3BlcnRpZXMiOiB7Iml0ZW1fbmFtZSI6ICJCb290cyIsIiR2YWx1ZSI6IDEwMH19` 
-  # @param data String representation of base64 encoded JSON object
-  # @param [Hash] opts the optional parameters
-  # @return [String]
-  describe 'track_get test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for track_post
-  # Track Profile Activity
-  # This endpoint is used to track a profile's activity. The following data is encoded in a JSON object. NOTE: an account can have up to 200 unique metrics (event types). This endpoint can accept payloads up to approximately 1MB.     **JSON OBJECT STRUCTURE:**    __token: *string*__   This is your public API key.      __event: *string*__   Name of the event you want to track.       __customer_properties: *JSON Object or null*__   Properties of the profile that triggered this event. You must identify the person by their email using a $email key (or by their phone number using a `$phone_number` key if you have SMS-only contacts). Other than that, you can include any data you want and it can then be used to create segments of people. For example, if you wanted to create a list of people on trial plans, include a person's plan type in this JSON object so you can use that information later.      __properties: *optional; JSON Object or null*__   Properties of this event. Any properties included here can be used for creating segments later For example, if you track an event called \"Ordered Product\" you could include a property for item type (e.g. image, article, etc.), size, etc.    __time: *optional; 10-digit UNIX timestamp or null*__   When this event occurred. By default, Klaviyo assumes events happen when a request is made. If you'd like to track an event that happened in past, use this property.         **SPECIAL FIELDS:**      The Klaviyo CRM has the following special fields you can set for **customer_properties** with the **Track** endpoint, to unlock additional functionality:      **$email:** _string_   **$first_name:** _string_   **$last_name:** _string_   **$phone_number:** _string; eg: \"+13239169023\"_   **$city:** _string_   **$region:** _string; state, or other region_   **$country:** _string_   **$zip:** _string_   **$image:** _string; url to a photo of a person_   **$consent:** _list of strings; eg: ['sms', 'email', 'web', 'directmail', 'mobile']_      You can also set the following special fields in event **properties** with the **Track** endpoint:      **$event_id:** _a unique identifier for an event_   **$value:** _a numeric value to associate with this event (e.g. the dollar value of a purchase)_      **EXAMPLE:**      ```   {     \"token\": \"PUBLIC_KEY\",     \"event\": \"Ordered Product\",     \"customer_properties\": {       \"$email\": \"abraham.lincoln@klaviyo.com\"     },     \"properties\": {       \"item_name\": \"Boots\",       \"$value\": 100     }   } 
-  # @param data 
-  # @param [Hash] opts the optional parameters
-  # @return [String]
-  describe 'track_post test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end