klaviyo_sdk 1.0.1.20220329 → 1.0.4.20220329

data/docs/TrackIdentifyApi.md

@@ -1,267 +0,0 @@
-# Client::TrackIdentifyApi
-
-All URIs are relative to *https://a.klaviyo.com/api*
-
-| Method | HTTP request | Description |
-| ------ | ------------ | ----------- |
-| [**identify_get**](TrackIdentifyApi.md#identify_get) | **GET** /identify | Identify Profile (Legacy) |
-| [**identify_post**](TrackIdentifyApi.md#identify_post) | **POST** /identify | Identify Profile |
-| [**track_get**](TrackIdentifyApi.md#track_get) | **GET** /track | Track Profile Activity (Legacy) |
-| [**track_post**](TrackIdentifyApi.md#track_post) | **POST** /track | Track Profile Activity |
-
-
-## identify_get
-
-> String identify_get(data)
-
-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`     
-
-### Examples
-
-```ruby
-require 'time'
-require 'klaviyo_sdk'
-
-api_instance = Client::TrackIdentifyApi.new
-data = 'BASE_64_STRING' # String | String representation of base64 encoded JSON object
-
-begin
-  # Identify Profile (Legacy)
-  result = api_instance.identify_get(data)
-  p result
-rescue Client::ApiError => e
-  puts "Error when calling TrackIdentifyApi->identify_get: #{e}"
-end
-```
-
-#### Using the identify_get_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(String, Integer, Hash)> identify_get_with_http_info(data)
-
-```ruby
-begin
-  # Identify Profile (Legacy)
-  data, status_code, headers = api_instance.identify_get_with_http_info(data)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => String
-rescue Client::ApiError => e
-  puts "Error when calling TrackIdentifyApi->identify_get_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **data** | **String** | String representation of base64 encoded JSON object | [default to &#39;BASE_64_STRING&#39;] |
-
-### Return type
-
-**String**
-
-### Authorization
-
-No authorization required
-
-### HTTP request headers
-
-- **Content-Type**: Not defined
-- **Accept**: text/html
-
-
-## identify_post
-
-> String identify_post(data)
-
-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\"       }   }    
-
-### Examples
-
-```ruby
-require 'time'
-require 'klaviyo_sdk'
-
-api_instance = Client::TrackIdentifyApi.new
-data = 'data_example' # String | 
-
-begin
-  # Identify Profile
-  result = api_instance.identify_post(data)
-  p result
-rescue Client::ApiError => e
-  puts "Error when calling TrackIdentifyApi->identify_post: #{e}"
-end
-```
-
-#### Using the identify_post_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(String, Integer, Hash)> identify_post_with_http_info(data)
-
-```ruby
-begin
-  # Identify Profile
-  data, status_code, headers = api_instance.identify_post_with_http_info(data)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => String
-rescue Client::ApiError => e
-  puts "Error when calling TrackIdentifyApi->identify_post_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **data** | **String** |  | [default to &#39;{\&quot;token\&quot;: \&quot;PUBLIC_KEY\&quot;,\&quot;properties\&quot;: {\&quot;$email\&quot;:\&quot;ben.franklin@klaviyo.com\&quot;}}&#39;] |
-
-### Return type
-
-**String**
-
-### Authorization
-
-No authorization required
-
-### HTTP request headers
-
-- **Content-Type**: application/x-www-form-urlencoded
-- **Accept**: text/html
-
-
-## track_get
-
-> String track_get(data)
-
-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` 
-
-### Examples
-
-```ruby
-require 'time'
-require 'klaviyo_sdk'
-
-api_instance = Client::TrackIdentifyApi.new
-data = 'BASE_64_STRING' # String | String representation of base64 encoded JSON object
-
-begin
-  # Track Profile Activity (Legacy)
-  result = api_instance.track_get(data)
-  p result
-rescue Client::ApiError => e
-  puts "Error when calling TrackIdentifyApi->track_get: #{e}"
-end
-```
-
-#### Using the track_get_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(String, Integer, Hash)> track_get_with_http_info(data)
-
-```ruby
-begin
-  # Track Profile Activity (Legacy)
-  data, status_code, headers = api_instance.track_get_with_http_info(data)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => String
-rescue Client::ApiError => e
-  puts "Error when calling TrackIdentifyApi->track_get_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **data** | **String** | String representation of base64 encoded JSON object | [default to &#39;BASE_64_STRING&#39;] |
-
-### Return type
-
-**String**
-
-### Authorization
-
-No authorization required
-
-### HTTP request headers
-
-- **Content-Type**: Not defined
-- **Accept**: text/html
-
-
-## track_post
-
-> String track_post(data)
-
-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     }   } 
-
-### Examples
-
-```ruby
-require 'time'
-require 'klaviyo_sdk'
-
-api_instance = Client::TrackIdentifyApi.new
-data = 'data_example' # String | 
-
-begin
-  # Track Profile Activity
-  result = api_instance.track_post(data)
-  p result
-rescue Client::ApiError => e
-  puts "Error when calling TrackIdentifyApi->track_post: #{e}"
-end
-```
-
-#### Using the track_post_with_http_info variant
-
-This returns an Array which contains the response data, status code and headers.
-
-> <Array(String, Integer, Hash)> track_post_with_http_info(data)
-
-```ruby
-begin
-  # Track Profile Activity
-  data, status_code, headers = api_instance.track_post_with_http_info(data)
-  p status_code # => 2xx
-  p headers # => { ... }
-  p data # => String
-rescue Client::ApiError => e
-  puts "Error when calling TrackIdentifyApi->track_post_with_http_info: #{e}"
-end
-```
-
-### Parameters
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **data** | **String** |  | [default to &#39;{\&quot;token\&quot;: \&quot;PUBLIC_KEY\&quot;, \&quot;event\&quot;: \&quot;Ordered Product\&quot;, \&quot;customer_properties\&quot;: {\&quot;$email\&quot;: \&quot;abraham.lincoln@klaviyo.com\&quot;}, \&quot;properties\&quot;: {\&quot;item_name\&quot;: \&quot;Boots\&quot;,\&quot;$value\&quot;: 100}}&#39;] |
-
-### Return type
-
-**String**
-
-### Authorization
-
-No authorization required
-
-### HTTP request headers
-
-- **Content-Type**: application/x-www-form-urlencoded
-- **Accept**: text/html
-

data/docs/TrackPayload.md

@@ -1,24 +0,0 @@
-# Client::TrackPayload
-
-## Properties
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **token** | **String** |  |  |
-| **customer_properties** | [**TrackPayloadCustomerProperties**](TrackPayloadCustomerProperties.md) |  |  |
-| **properties** | [**TrackPayloadProperties**](TrackPayloadProperties.md) |  |  |
-| **time** | [**OneOfstringinteger**](OneOfstringinteger.md) |  | [optional] |
-
-## Example
-
-```ruby
-require 'klaviyo_sdk'
-
-instance = Client::TrackPayload.new(
-  token: null,
-  customer_properties: null,
-  properties: null,
-  time: null
-)
-```
-

data/docs/TrackPayloadCustomerProperties.md

@@ -1,20 +0,0 @@
-# Client::TrackPayloadCustomerProperties
-
-## Properties
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **_email** | **String** |  | [optional] |
-| **_phone_number** | **String** |  | [optional] |
-
-## Example
-
-```ruby
-require 'klaviyo_sdk'
-
-instance = Client::TrackPayloadCustomerProperties.new(
-  _email: null,
-  _phone_number: null
-)
-```
-

data/docs/TrackPayloadProperties.md

@@ -1,22 +0,0 @@
-# Client::TrackPayloadProperties
-
-## Properties
-
-| Name | Type | Description | Notes |
-| ---- | ---- | ----------- | ----- |
-| **event_id** | **String** |  | [optional] |
-| **value** | **String** |  | [optional] |
-| **your_custom_field** | [**OneOfstringintegernumberbooleanarray**](OneOfstringintegernumberbooleanarray.md) |  | [optional] |
-
-## Example
-
-```ruby
-require 'klaviyo_sdk'
-
-instance = Client::TrackPayloadProperties.new(
-  event_id: null,
-  value: null,
-  your_custom_field: null
-)
-```
-

data/git_push.sh

@@ -1,57 +0,0 @@
-#!/bin/sh
-# ref: https://help.github.com/articles/adding-an-existing-project-to-github-using-the-command-line/
-#
-# Usage example: /bin/sh ./git_push.sh wing328 openapi-petstore-perl "minor update" "gitlab.com"
-
-git_user_id=$1
-git_repo_id=$2
-release_note=$3
-git_host=$4
-
-if [ "$git_host" = "" ]; then
-    git_host="github.com"
-    echo "[INFO] No command line input provided. Set \$git_host to $git_host"
-fi
-
-if [ "$git_user_id" = "" ]; then
-    git_user_id="GIT_USER_ID"
-    echo "[INFO] No command line input provided. Set \$git_user_id to $git_user_id"
-fi
-
-if [ "$git_repo_id" = "" ]; then
-    git_repo_id="GIT_REPO_ID"
-    echo "[INFO] No command line input provided. Set \$git_repo_id to $git_repo_id"
-fi
-
-if [ "$release_note" = "" ]; then
-    release_note="Minor update"
-    echo "[INFO] No command line input provided. Set \$release_note to $release_note"
-fi
-
-# Initialize the local directory as a Git repository
-git init
-
-# Adds the files in the local repository and stages them for commit.
-git add .
-
-# Commits the tracked changes and prepares them to be pushed to a remote repository.
-git commit -m "$release_note"
-
-# Sets the new remote
-git_remote=$(git remote)
-if [ "$git_remote" = "" ]; then # git remote not defined
-
-    if [ "$GIT_TOKEN" = "" ]; then
-        echo "[INFO] \$GIT_TOKEN (environment variable) is not set. Using the git credential in your environment."
-        git remote add origin https://${git_host}/${git_user_id}/${git_repo_id}.git
-    else
-        git remote add origin https://${git_user_id}:"${GIT_TOKEN}"@${git_host}/${git_user_id}/${git_repo_id}.git
-    fi
-
-fi
-
-git pull origin master
-
-# Pushes (Forces) the changes in the local repository up to the remote repository
-echo "Git pushing to https://${git_host}/${git_user_id}/${git_repo_id}.git"
-git push origin master 2>&1 | grep -v 'To https'

data/spec/api/campaigns_api_spec.rb

@@ -1,165 +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::CampaignsApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'CampaignsApi' do
-  before do
-    # run before each test
-    @api_instance = Client::CampaignsApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of CampaignsApi' do
-    it 'should create an instance of CampaignsApi' do
-      expect(@api_instance).to be_instance_of(Client::CampaignsApi)
-    end
-  end
-
-  # unit tests for cancel_campaign
-  # Cancel a Campaign
-  # Cancels a campaign send. Marks a campaign as cancelled regardless of it's current status.
-  # @param campaign_id 
-  # @param [Hash] opts the optional parameters
-  # @return [Campaign]
-  describe 'cancel_campaign 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 clone_campaign
-  # Clone a Campaign
-  # Creates a copy of a campaign. The new campaign starts as a draft.
-  # @param campaign_id 
-  # @param name The name for the new campaign. All other properties of the campaign will remain the same. Note, the template for the new campaign will be cloned from the existing template so changes to the existing campaign's content will not alter the content of the new campaign.
-  # @param list_id The list you will send the campaign to.
-  # @param [Hash] opts the optional parameters
-  # @return [Campaign]
-  describe 'clone_campaign 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_campaign
-  # Create New Campaign
-  # Creates a new campaign. The created campaign is a draft and is not automatically sent.
-  # @param list_id The list you will send the campaign to.
-  # @param template_id  The template that will define the content of the page. Note: the Email Template is copied when creating this campaign, so future changes to that Email Template will not alter the content of this campaign. 
-  # @param from_email The email address your email will be sent from and will be used in the `reply-to` header.
-  # @param from_name The name or label associated with the email address you're sending from.
-  # @param subject The email subject of the campaign
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :name If not specified, this will default to the subject of the campaign.
-  # @option opts [Boolean] :use_smart_sending If set, limits the number of emails sent to an individual within a short period. Valid values are `true` and `false`. If not specified, defaults to `true`.
-  # @option opts [Boolean] :add_google_analytics If specified, adds Google Analytics tracking tags to links. Valid values are `true` and `false`. If not specified, defaults to `false`.
-  # @return [Campaign]
-  describe 'create_campaign 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_campaign_info
-  # Get Campaign Info
-  # Returns summary information for the campaign specified.
-  # @param campaign_id 
-  # @param [Hash] opts the optional parameters
-  # @return [Campaign]
-  describe 'get_campaign_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_campaign_recipients
-  # Get Campaign Recipients
-  # Returns summary information about email recipients for the campaign specified that includes each recipients email, customer ID, and status.
-  # @param campaign_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [Integer] :count For pagination, the number of results to return. Max = 25,000
-  # @option opts [String] :sort Sort order to apply to results, either ascending or descending. Valid values are `asc` or `desc`. Defaults to `asc`.
-  # @option opts [String] :offset For pagination, if a response to this endpoint includes a `next_offset`, use that value to get the next page of recipients.
-  # @return [Hash<String, Object>]
-  describe 'get_campaign_recipients 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_campaigns
-  # Get Campaigns
-  # Returns a list of all the campaigns you&#39;ve created. The campaigns are returned in reverse sorted order by the time they were created.
-  # @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_campaigns 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 schedule_campaign
-  # Schedule a Campaign
-  # Schedules a campaign for a time in the future
-  # @param campaign_id 
-  # @param send_time  A timestamp of the format &#x60;%Y-%m-%d %H:%M:%S&#x60; in the UTC timezone.  Ex:  &#x60;2022-01-13 00:00:00&#x60; 
-  # @param [Hash] opts the optional parameters
-  # @return [Hash<String, Object>]
-  describe 'schedule_campaign 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_campaign
-  # Send a Campaign Immediately
-  # Queues a campaign for immediate delivery
-  # @param campaign_id 
-  # @param [Hash] opts the optional parameters
-  # @return [Hash<String, Object>]
-  describe 'send_campaign 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_campaign
-  # Update Campaign
-  # Updates details of a campaign. You can update a campaign&#39;s name, subject, from email address, from name, template or list.
-  # @param campaign_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :list_id The list you will send the campaign to.
-  # @option opts [String] :template_id The ID of the Email Template object that will be the content of this campaign. Note the Email Template is copied when creating this campaign, so future changes to that Email Template will not alter the content of this campaign.
-  # @option opts [String] :from_email The email address your email will be sent from and will be used in the reply-to header.
-  # @option opts [String] :from_name The name or label associated with the email address you&#39;re sending from.
-  # @option opts [String] :subject The email subject of the campaign
-  # @option opts [String] :name A name for this campaign. If not specified, this will default to the subject of the campaign.
-  # @option opts [Boolean] :use_smart_sending If set, limits the number of emails sent to an individual within a short period. Campaigns initially default to &#x60;true&#x60;.
-  # @option opts [Boolean] :add_google_analytics If specified, adds Google Analytics tracking tags to links. Campaigns initially default to &#x60;false&#x60;.
-  # @return [Campaign]
-  describe 'update_campaign 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/data_privacy_api_spec.rb

@@ -1,47 +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::DataPrivacyApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'DataPrivacyApi' do
-  before do
-    # run before each test
-    @api_instance = Client::DataPrivacyApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of DataPrivacyApi' do
-    it 'should create an instance of DataPrivacyApi' do
-      expect(@api_instance).to be_instance_of(Client::DataPrivacyApi)
-    end
-  end
-
-  # unit tests for request_deletion
-  # Request a Deletion
-  # Request a data privacy-compliant deletion for the person record corresponding to an email address, phone number, or person identifier.   **If multiple person records exist for the provided identifier, only one of them will be deleted.**  The arguments should be sent as content type application/json.           Note that only **one** identifier (email, phone_number, or person_id) can be specified.  In addition to your API key, you need to set exactly one of the following parameters: `email`, `phone_number`, `or person_id`, along with the associated `string` value.   Examples:  Email:    `{\"email\":\"abraham.lincoln@klaviyo.com\"}`    Phone Number:      `{\"phone_number\":\"+13239169023\"}`    Person ID:      `{\"person_id\":\"PERSON_ID\"}` 
-  # @param [Hash] opts the optional parameters
-  # @option opts [String] :body 
-  # @return [String]
-  describe 'request_deletion test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end