talon_one 2.1.1 → 2.2.0

data/docs/NewCampaign.md

@@ -16,6 +16,7 @@ Name | Type | Description | Notes
 **coupon_settings** | [**CodeGeneratorSettings**](CodeGeneratorSettings.md) |  | [optional] 
 **referral_settings** | [**CodeGeneratorSettings**](CodeGeneratorSettings.md) |  | [optional] 
 **limits** | [**Array<LimitConfig>**](LimitConfig.md) | The set of limits that will operate for this campaign | 
+**campaign_groups** | **Array<Integer>** | The IDs of the campaign groups that own this entity. | [optional] 
 
 ## Code Sample
 
@@ -33,7 +34,8 @@ instance = TalonOne::NewCampaign.new(name: null,
                                  features: null,
                                  coupon_settings: null,
                                  referral_settings: null,
-                                 limits: null)
+                                 limits: null,
+                                 campaign_groups: null)
 ```
 
 

data/docs/NewCampaignGroup.md

@@ -0,0 +1,23 @@
+# TalonOne::NewCampaignGroup
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**name** | **String** | The name of this campaign group. | 
+**description** | **String** | A longer description of the campaign group. | [optional] 
+**subscribed_applications_ids** | **Array<Integer>** | A list of the IDs of the applications that this campaign group is enabled for | [optional] 
+**campaign_ids** | **Array<Integer>** | A list of the IDs of the campaigns that this campaign group owns | [optional] 
+
+## Code Sample
+
+```ruby
+require 'TalonOne'
+
+instance = TalonOne::NewCampaignGroup.new(name: null,
+                                 description: null,
+                                 subscribed_applications_ids: null,
+                                 campaign_ids: null)
+```
+
+

data/docs/NewLoyaltyProgram.md

@@ -8,7 +8,8 @@ Name | Type | Description | Notes
 **title** | **String** | The display title for the Loyalty Program. | 
 **description** | **String** | Description of our Loyalty Program. | [optional] 
 **subscribed_applications** | **Array<Integer>** | A list containing the IDs of all applications that are subscribed to this Loyalty Program. | [optional] 
-**default_validity** | **String** | Indicates the default duration after which new loyalty points should expire. The format is a number, followed by one letter indicating the unit; like '1h' or '40m' or '30d'. | 
+**default_validity** | **String** | Indicates the default duration after which new loyalty points should expire. The format is a number, followed by one letter indicating the unit; like '1h' or '40m'. | 
+**default_pending** | **String** | Indicates the default duration for the pending time, after which points will be valid. The format is a number followed by a duration unit, like '1h' or '40m'. | 
 **allow_subledger** | **Boolean** | Indicates if this program supports subledgers inside the program | 
 
 ## Code Sample
@@ -21,6 +22,7 @@ instance = TalonOne::NewLoyaltyProgram.new(name: null,
                                  description: null,
                                  subscribed_applications: null,
                                  default_validity: null,
+                                 default_pending: null,
                                  allow_subledger: null)
 ```
 

data/docs/Role.md

@@ -6,10 +6,11 @@ Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **id** | **Integer** | The ID of the role corresponding to the DB row | 
 **account_id** | **Integer** | The ID of the Talon.One account that owns this role. | 
+**campaign_group_id** | **Integer** | The ID of the Campaign Group this role was created for. | [optional] 
 **name** | **String** | Name of the role | [optional] 
 **description** | **String** | Description of the role | [optional] 
 **members** | **Array<Integer>** | A list of user identifiers assigned to this role | [optional] 
-**acl** | **String** | Role Policy this should be a stringified blob of json | [optional] 
+**acl** | [**Object**](.md) | Role ACL Policy | [optional] 
 
 ## Code Sample
 
@@ -18,6 +19,7 @@ require 'TalonOne'
 
 instance = TalonOne::Role.new(id: null,
                                  account_id: null,
+                                 campaign_group_id: null,
                                  name: null,
                                  description: null,
                                  members: null,

data/docs/SetDiscountEffectProps.md

@@ -6,6 +6,7 @@ Name | Type | Description | Notes
 ------------ | ------------- | ------------- | -------------
 **name** | **String** | The name/description of this discount | 
 **value** | **Float** | The total monetary value of the discount | 
+**scope** | **String** | The scope which the discount was applied on, can be one of (cartItems,additionalCosts,sessionTotal) | [optional] 
 
 ## Code Sample
 
@@ -13,7 +14,8 @@ Name | Type | Description | Notes
 require 'TalonOne'
 
 instance = TalonOne::SetDiscountEffectProps.new(name: null,
-                                 value: null)
+                                 value: null,
+                                 scope: null)
 ```
 
 

data/docs/SetDiscountPerItemEffectProps.md

@@ -7,6 +7,7 @@ Name | Type | Description | Notes
 **name** | **String** | The name/description of this discount | 
 **value** | **Float** | The total monetary value of the discount | 
 **position** | **Float** | The index of the item in the cart items list on which this discount should be applied | 
+**sub_position** | **Float** | The sub-index of the item in an item stack on which this discount should be applied | [optional] 
 
 ## Code Sample
 
@@ -15,7 +16,8 @@ require 'TalonOne'
 
 instance = TalonOne::SetDiscountPerItemEffectProps.new(name: null,
                                  value: null,
-                                 position: null)
+                                 position: null,
+                                 sub_position: null)
 ```
 
 

data/docs/UpdateApplication.md

@@ -11,8 +11,12 @@ Name | Type | Description | Notes
 **case_sensitivity** | **String** | A string indicating how should campaigns in this application deal with case sensitivity on coupon codes. | [optional] 
 **attributes** | [**Object**](.md) | Arbitrary properties associated with this campaign | [optional] 
 **limits** | [**Array<LimitConfig>**](LimitConfig.md) | Default limits for campaigns created in this application | [optional] 
-**campaign_priority** | **String** | Default priority for campaigns created in this application, can be one of (universal, stackable, exclusive) | [optional] 
+**campaign_priority** | **String** | Default priority for campaigns created in this application, can be one of (universal, stackable, exclusive). If no value is provided, this is set to \"universal\" | [optional] 
+**exclusive_campaigns_strategy** | **String** | The strategy used when choosing exclusive campaigns for evaluation, can be one of (listOrder, lowestDiscount, highestDiscount). If no value is provided, this is set to \"listOrder\" | [optional] 
+**enable_cascading_discounts** | **Boolean** | Flag indicating if discounts should cascade for this application | [optional] 
+**enable_flattened_cart_items** | **Boolean** | Flag indicating if cart items of quantity larger than one should be separated into different items of quantity one | [optional] 
 **attributes_settings** | [**AttributesSettings**](AttributesSettings.md) |  | [optional] 
+**sandbox** | **Boolean** | Flag indicating if this is a live or sandbox application | [optional] 
 
 ## Code Sample
 
@@ -27,7 +31,11 @@ instance = TalonOne::UpdateApplication.new(name: null,
                                  attributes: null,
                                  limits: null,
                                  campaign_priority: null,
-                                 attributes_settings: null)
+                                 exclusive_campaigns_strategy: null,
+                                 enable_cascading_discounts: null,
+                                 enable_flattened_cart_items: null,
+                                 attributes_settings: null,
+                                 sandbox: null)
 ```
 
 

data/docs/UpdateAudience.md

@@ -0,0 +1,17 @@
+# TalonOne::UpdateAudience
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**name** | **String** | The human-friendly display name for this Audience. | 
+
+## Code Sample
+
+```ruby
+require 'TalonOne'
+
+instance = TalonOne::UpdateAudience.new(name: null)
+```
+
+

data/docs/UpdateCampaign.md

@@ -16,6 +16,7 @@ Name | Type | Description | Notes
 **coupon_settings** | [**CodeGeneratorSettings**](CodeGeneratorSettings.md) |  | [optional] 
 **referral_settings** | [**CodeGeneratorSettings**](CodeGeneratorSettings.md) |  | [optional] 
 **limits** | [**Array<LimitConfig>**](LimitConfig.md) | The set of limits that will operate for this campaign | 
+**campaign_groups** | **Array<Integer>** | The IDs of the campaign groups that own this entity. | [optional] 
 
 ## Code Sample
 
@@ -33,7 +34,8 @@ instance = TalonOne::UpdateCampaign.new(name: null,
                                  features: null,
                                  coupon_settings: null,
                                  referral_settings: null,
-                                 limits: null)
+                                 limits: null,
+                                 campaign_groups: null)
 ```
 
 

data/docs/UpdateCampaignGroup.md

@@ -0,0 +1,23 @@
+# TalonOne::UpdateCampaignGroup
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**name** | **String** | The name of this campaign group. | 
+**description** | **String** | A longer description of the campaign group. | [optional] 
+**subscribed_applications_ids** | **Array<Integer>** | A list of the IDs of the applications that this campaign group is enabled for | [optional] 
+**campaign_ids** | **Array<Integer>** | A list of the IDs of the campaigns that this campaign group owns | [optional] 
+
+## Code Sample
+
+```ruby
+require 'TalonOne'
+
+instance = TalonOne::UpdateCampaignGroup.new(name: null,
+                                 description: null,
+                                 subscribed_applications_ids: null,
+                                 campaign_ids: null)
+```
+
+

data/docs/UpdateLoyaltyProgram.md

@@ -7,7 +7,8 @@ Name | Type | Description | Notes
 **title** | **String** | The display title for the Loyalty Program. | [optional] 
 **description** | **String** | Description of our Loyalty Program. | [optional] 
 **subscribed_applications** | **Array<Integer>** | A list containing the IDs of all applications that are subscribed to this Loyalty Program. | [optional] 
-**default_validity** | **String** | Indicates the default duration after which new loyalty points should expire. The format is a number, followed by one letter indicating the unit; like '1h' or '40m' or '30d'. | [optional] 
+**default_validity** | **String** | Indicates the default duration after which new loyalty points should expire. The format is a number, followed by one letter indicating the unit; like '1h' or '40m'. | [optional] 
+**default_pending** | **String** | Indicates the default duration for the pending time, after which points will be valid. The format is a number followed by a duration unit, like '1h' or '40m'. | [optional] 
 **allow_subledger** | **Boolean** | Indicates if this program supports subledgers inside the program | [optional] 
 
 ## Code Sample
@@ -19,6 +20,7 @@ instance = TalonOne::UpdateLoyaltyProgram.new(title: null,
                                  description: null,
                                  subscribed_applications: null,
                                  default_validity: null,
+                                 default_pending: null,
                                  allow_subledger: null)
 ```
 

data/docs/UpdateUser.md

@@ -7,8 +7,6 @@ Name | Type | Description | Notes
 **name** | **String** | Your name. | [optional] 
 **policy** | **String** | a blob of acl json | [optional] 
 **state** | **String** | New state (\"deactivated\" or \"active\") for the user. Only usable by admins for the user. | [optional] 
-**release_update** | **Boolean** | Update the user via email | [optional] 
-**latest_feature** | **String** | The latest feature you've been notified. | [optional] 
 **roles** | **Array<Integer>** | Update | [optional] 
 **application_notification_subscriptions** | [**Object**](.md) |  | [optional] 
 
@@ -20,8 +18,6 @@ require 'TalonOne'
 instance = TalonOne::UpdateUser.new(name: null,
                                  policy: null,
                                  state: null,
-                                 release_update: null,
-                                 latest_feature: null,
                                  roles: null,
                                  application_notification_subscriptions: null)
 ```

data/docs/UpdateUserLatestFeedTimestamp.md

@@ -0,0 +1,17 @@
+# TalonOne::UpdateUserLatestFeedTimestamp
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**new_latest_feed_timestamp** | **DateTime** | New timestamp to update for the current user | 
+
+## Code Sample
+
+```ruby
+require 'TalonOne'
+
+instance = TalonOne::UpdateUserLatestFeedTimestamp.new(new_latest_feed_timestamp: null)
+```
+
+

data/docs/User.md

@@ -12,9 +12,8 @@ Name | Type | Description | Notes
 **invite_token** | **String** | Invite token, empty if the user as already accepted their invite. | 
 **state** | **String** | Current user state. | 
 **name** | **String** | Full name | 
-**policy** | **String** | A blob of ACL JSON | 
-**release_update** | **Boolean** | Update the user via email | 
-**latest_feature** | **String** | Latest feature the user has been notified. | [optional] 
+**policy** | [**Object**](.md) | User ACL Policy | 
+**latest_feed_timestamp** | **DateTime** | Latest timestamp the user has been notified for feed. | [optional] 
 **roles** | **Array<Integer>** | Contains a list of all roles the user is a member of | [optional] 
 **application_notification_subscriptions** | [**Object**](.md) |  | [optional] 
 **auth_method** | **String** | The Authentication method for this user | [optional] 
@@ -33,8 +32,7 @@ instance = TalonOne::User.new(id: null,
                                  state: null,
                                  name: null,
                                  policy: null,
-                                 release_update: null,
-                                 latest_feature: null,
+                                 latest_feed_timestamp: null,
                                  roles: null,
                                  application_notification_subscriptions: null,
                                  auth_method: null)

data/docs/UserFeedNotifications.md

@@ -0,0 +1,19 @@
+# TalonOne::UserFeedNotifications
+
+## Properties
+
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**last_update** | **DateTime** | Timestamp of the last request for this list | 
+**notifications** | [**Array<FeedNotification>**](FeedNotification.md) | List of all notifications to notify the user about | 
+
+## Code Sample
+
+```ruby
+require 'TalonOne'
+
+instance = TalonOne::UserFeedNotifications.new(last_update: null,
+                                 notifications: null)
+```
+
+

data/lib/talon_one.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 4.2.3
+OpenAPI Generator version: 4.3.1
 
 =end
 
@@ -42,12 +42,16 @@ require 'talon_one/models/application_session_entity'
 require 'talon_one/models/attribute'
 require 'talon_one/models/attributes_mandatory'
 require 'talon_one/models/attributes_settings'
+require 'talon_one/models/audience'
+require 'talon_one/models/audience_membership'
 require 'talon_one/models/base_saml_connection'
 require 'talon_one/models/binding'
 require 'talon_one/models/campaign'
 require 'talon_one/models/campaign_analytics'
 require 'talon_one/models/campaign_copy'
 require 'talon_one/models/campaign_entity'
+require 'talon_one/models/campaign_group'
+require 'talon_one/models/campaign_group_entity'
 require 'talon_one/models/campaign_search'
 require 'talon_one/models/campaign_set'
 require 'talon_one/models/campaign_set_branch_node'
@@ -70,8 +74,10 @@ require 'talon_one/models/customer_activity_report'
 require 'talon_one/models/customer_analytics'
 require 'talon_one/models/customer_inventory'
 require 'talon_one/models/customer_profile'
+require 'talon_one/models/customer_profile_audience_request'
+require 'talon_one/models/customer_profile_audience_request_item'
+require 'talon_one/models/customer_profile_integration_request_v2'
 require 'talon_one/models/customer_profile_search_query'
-require 'talon_one/models/customer_profile_update'
 require 'talon_one/models/customer_session'
 require 'talon_one/models/customer_session_v2'
 require 'talon_one/models/deduct_loyalty_points_effect_props'
@@ -79,6 +85,7 @@ require 'talon_one/models/effect'
 require 'talon_one/models/effect_entity'
 require 'talon_one/models/email_entity'
 require 'talon_one/models/entity'
+require 'talon_one/models/entity_with_talang_visible_id'
 require 'talon_one/models/environment'
 require 'talon_one/models/error_effect_props'
 require 'talon_one/models/error_response'
@@ -89,6 +96,7 @@ require 'talon_one/models/export'
 require 'talon_one/models/feature_flag'
 require 'talon_one/models/feature_flags'
 require 'talon_one/models/features_feed'
+require 'talon_one/models/feed_notification'
 require 'talon_one/models/func_arg_def'
 require 'talon_one/models/function_def'
 require 'talon_one/models/import'
@@ -142,11 +150,14 @@ require 'talon_one/models/loyalty_points'
 require 'talon_one/models/loyalty_program'
 require 'talon_one/models/loyalty_program_balance'
 require 'talon_one/models/loyalty_program_ledgers'
+require 'talon_one/models/loyalty_statistics'
 require 'talon_one/models/loyalty_sub_ledger'
 require 'talon_one/models/manager_config'
 require 'talon_one/models/meta'
-require 'talon_one/models/misc_update_user_latest_feature'
 require 'talon_one/models/multi_application_entity'
+require 'talon_one/models/multiple_customer_profile_integration_request'
+require 'talon_one/models/multiple_customer_profile_integration_request_item'
+require 'talon_one/models/multiple_customer_profile_integration_response_v2'
 require 'talon_one/models/mutable_entity'
 require 'talon_one/models/new_account'
 require 'talon_one/models/new_account_sign_up'
@@ -154,7 +165,9 @@ require 'talon_one/models/new_additional_cost'
 require 'talon_one/models/new_application'
 require 'talon_one/models/new_application_api_key'
 require 'talon_one/models/new_attribute'
+require 'talon_one/models/new_audience'
 require 'talon_one/models/new_campaign'
+require 'talon_one/models/new_campaign_group'
 require 'talon_one/models/new_campaign_set'
 require 'talon_one/models/new_coupons'
 require 'talon_one/models/new_customer_profile'
@@ -205,14 +218,18 @@ require 'talon_one/models/trigger_webhook_effect_props'
 require 'talon_one/models/update_account'
 require 'talon_one/models/update_application'
 require 'talon_one/models/update_attribute_effect_props'
+require 'talon_one/models/update_audience'
 require 'talon_one/models/update_campaign'
+require 'talon_one/models/update_campaign_group'
 require 'talon_one/models/update_coupon'
 require 'talon_one/models/update_coupon_batch'
 require 'talon_one/models/update_loyalty_program'
 require 'talon_one/models/update_role'
 require 'talon_one/models/update_user'
+require 'talon_one/models/update_user_latest_feed_timestamp'
 require 'talon_one/models/user'
 require 'talon_one/models/user_entity'
+require 'talon_one/models/user_feed_notifications'
 require 'talon_one/models/webhook'
 require 'talon_one/models/webhook_activation_log_entry'
 require 'talon_one/models/webhook_log_entry'

data/lib/talon_one/api/integration_api.rb

@@ -6,7 +6,7 @@
 The version of the OpenAPI document: 1.0.0
 
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 4.2.3
+OpenAPI Generator version: 4.3.1
 
 =end
 
@@ -288,6 +288,7 @@ module TalonOne
     # @option opts [Boolean] :profile optional flag to decide if you would like customer profile information in the response
     # @option opts [Boolean] :referrals optional flag to decide if you would like referral information in the response
     # @option opts [Boolean] :coupons optional flag to decide if you would like coupon information in the response
+    # @option opts [Boolean] :loyalty optional flag to decide if you would like loyalty information in the response
     # @return [CustomerInventory]
     def get_customer_inventory(integration_id, opts = {})
       data, _status_code, _headers = get_customer_inventory_with_http_info(integration_id, opts)
@@ -301,6 +302,7 @@ module TalonOne
     # @option opts [Boolean] :profile optional flag to decide if you would like customer profile information in the response
     # @option opts [Boolean] :referrals optional flag to decide if you would like referral information in the response
     # @option opts [Boolean] :coupons optional flag to decide if you would like coupon information in the response
+    # @option opts [Boolean] :loyalty optional flag to decide if you would like loyalty information in the response
     # @return [Array<(CustomerInventory, Integer, Hash)>] CustomerInventory data, response status code and response headers
     def get_customer_inventory_with_http_info(integration_id, opts = {})
       if @api_client.config.debugging
@@ -318,6 +320,7 @@ module TalonOne
       query_params[:'profile'] = opts[:'profile'] if !opts[:'profile'].nil?
       query_params[:'referrals'] = opts[:'referrals'] if !opts[:'referrals'].nil?
       query_params[:'coupons'] = opts[:'coupons'] if !opts[:'coupons'].nil?
+      query_params[:'loyalty'] = opts[:'loyalty'] if !opts[:'loyalty'].nil?
 
       # header parameters
       header_params = opts[:header_params] || {}
@@ -481,8 +484,8 @@ module TalonOne
       return data, status_code, headers
     end
 
-    # Update a Customer Profile
-    # Update (or create) a [Customer Profile][]. This profile information can then be matched and/or updated by campaign [Rules][].  The `integrationId` may be any identifier that will remain stable for the customer. For example, you might use a database ID, an email, or a phone number as the `integrationId`. It is vital that this ID **not** change over time, so **don't** use any identifier that the customer can update themselves. E.g. if your application allows a customer to update their e-mail address, you should instead use a database ID.  Updating a customer profile will return a response with the full integration state. This includes the current state of the customer profile, the customer session, the event that was recorded, and an array of effects that took place.  [Customer Profile]: /Getting-Started/entities#customer-profile [Rules]: /Getting-Started/entities#campaigns-rulesets-and-coupons 
+    # Update a Customer Profile V1
+    # ⚠️ Deprecation Notice: Support for requests to this endpoint will end on 15.07.2021. We will not remove the endpoint, and it will still be accessible for you to use. For new features support, please migrate to [API V2.0](/Getting-Started/APIV2).  Update (or create) a [Customer Profile][]. This profile information can then be matched and/or updated by campaign [Rules][].  The `integrationId` may be any identifier that will remain stable for the customer. For example, you might use a database ID, an email, or a phone number as the `integrationId`. It is vital that this ID **not** change over time, so **don't** use any identifier that the customer can update themselves. E.g. if your application allows a customer to update their e-mail address, you should instead use a database ID.  Updating a customer profile will return a response with the full integration state. This includes the current state of the customer profile, the customer session, the event that was recorded, and an array of effects that took place.  [Customer Profile]: /Getting-Started/entities#customer-profile [Rules]: /Getting-Started/entities#campaigns-rulesets-and-coupons 
     # @param integration_id [String] The custom identifier for this profile, must be unique within the account.
     # @param body [NewCustomerProfile] 
     # @param [Hash] opts the optional parameters
@@ -493,8 +496,8 @@ module TalonOne
       data
     end
 
-    # Update a Customer Profile
-    # Update (or create) a [Customer Profile][]. This profile information can then be matched and/or updated by campaign [Rules][].  The &#x60;integrationId&#x60; may be any identifier that will remain stable for the customer. For example, you might use a database ID, an email, or a phone number as the &#x60;integrationId&#x60;. It is vital that this ID **not** change over time, so **don&#39;t** use any identifier that the customer can update themselves. E.g. if your application allows a customer to update their e-mail address, you should instead use a database ID.  Updating a customer profile will return a response with the full integration state. This includes the current state of the customer profile, the customer session, the event that was recorded, and an array of effects that took place.  [Customer Profile]: /Getting-Started/entities#customer-profile [Rules]: /Getting-Started/entities#campaigns-rulesets-and-coupons 
+    # Update a Customer Profile V1
+    # ⚠️ Deprecation Notice: Support for requests to this endpoint will end on 15.07.2021. We will not remove the endpoint, and it will still be accessible for you to use. For new features support, please migrate to [API V2.0](/Getting-Started/APIV2).  Update (or create) a [Customer Profile][]. This profile information can then be matched and/or updated by campaign [Rules][].  The &#x60;integrationId&#x60; may be any identifier that will remain stable for the customer. For example, you might use a database ID, an email, or a phone number as the &#x60;integrationId&#x60;. It is vital that this ID **not** change over time, so **don&#39;t** use any identifier that the customer can update themselves. E.g. if your application allows a customer to update their e-mail address, you should instead use a database ID.  Updating a customer profile will return a response with the full integration state. This includes the current state of the customer profile, the customer session, the event that was recorded, and an array of effects that took place.  [Customer Profile]: /Getting-Started/entities#customer-profile [Rules]: /Getting-Started/entities#campaigns-rulesets-and-coupons 
     # @param integration_id [String] The custom identifier for this profile, must be unique within the account.
     # @param body [NewCustomerProfile] 
     # @param [Hash] opts the optional parameters
@@ -554,40 +557,108 @@ module TalonOne
       return data, status_code, headers
     end
 
+    # Update a Customer Profile Audiences
+    # Update one ore multiple Customer Profiles with the specified Audiences 
+    # @param body [CustomerProfileAudienceRequest] 
+    # @param [Hash] opts the optional parameters
+    # @return [nil]
+    def update_customer_profile_audiences(body, opts = {})
+      update_customer_profile_audiences_with_http_info(body, opts)
+      nil
+    end
+
+    # Update a Customer Profile Audiences
+    # Update one ore multiple Customer Profiles with the specified Audiences 
+    # @param body [CustomerProfileAudienceRequest] 
+    # @param [Hash] opts the optional parameters
+    # @return [Array<(nil, Integer, Hash)>] nil, response status code and response headers
+    def update_customer_profile_audiences_with_http_info(body, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: IntegrationApi.update_customer_profile_audiences ...'
+      end
+      # verify the required parameter 'body' is set
+      if @api_client.config.client_side_validation && body.nil?
+        fail ArgumentError, "Missing the required parameter 'body' when calling IntegrationApi.update_customer_profile_audiences"
+      end
+      # resource path
+      local_var_path = '/v2/customer_audiences'
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Content-Type'
+      header_params['Content-Type'] = @api_client.select_header_content_type(['application/json'])
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:body] || @api_client.object_to_http_body(body) 
+
+      # return_type
+      return_type = opts[:return_type] 
+
+      # auth_names
+      auth_names = opts[:auth_names] || ['api_key_v1']
+
+      new_options = opts.merge(
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: IntegrationApi#update_customer_profile_audiences\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
     # Update a Customer Profile
-    # Update (or create) a [Customer Profile][].   The `integrationId` may be any identifier that will remain stable for the customer. For example, you might use a database ID, an email, or a phone number as the `integrationId`. It is vital that this ID **not** change over time, so **don't** use any identifier that the customer can update themselves. E.g. if your application allows a customer to update their e-mail address, you should instead use a database ID.  [Customer Profile]: /Getting-Started/entities#customer-profile 
-    # @param customer_profile_id [String] The custom identifier for this profile, must be unique within the account.
-    # @param body [NewCustomerProfile] 
+    # Update (or create) a [Customer Profile][].  The `integrationId` may be any identifier that will remain stable for the customer. For example, you might use a database ID, an email, or a phone number as the `integrationId`. It is vital that this ID **not** change over time, so **don't** use any identifier that the customer can update themselves. E.g. if your application allows a customer to update their e-mail address, you should instead use a database ID.  [Customer Profile]: /Getting-Started/entities#customer-profile 
+    # @param integration_id [String] The custom identifier for this profile, must be unique within the account.
+    # @param body [CustomerProfileIntegrationRequestV2] 
     # @param [Hash] opts the optional parameters
-    # @return [CustomerProfileUpdate]
-    def update_customer_profile_v2(customer_profile_id, body, opts = {})
-      data, _status_code, _headers = update_customer_profile_v2_with_http_info(customer_profile_id, body, opts)
+    # @option opts [Boolean] :run_rule_engine Flag to indicate whether to run the rule engine (Defaults to false).
+    # @option opts [Boolean] :dry Flag to indicate whether to skip persisting the changes or not (Will not persist if set to &#39;true&#39;. Only used when &#39;runRuleEngine&#39; is set to &#39;true&#39;).
+    # @return [IntegrationStateV2]
+    def update_customer_profile_v2(integration_id, body, opts = {})
+      data, _status_code, _headers = update_customer_profile_v2_with_http_info(integration_id, body, opts)
       data
     end
 
     # Update a Customer Profile
-    # Update (or create) a [Customer Profile][].   The &#x60;integrationId&#x60; may be any identifier that will remain stable for the customer. For example, you might use a database ID, an email, or a phone number as the &#x60;integrationId&#x60;. It is vital that this ID **not** change over time, so **don&#39;t** use any identifier that the customer can update themselves. E.g. if your application allows a customer to update their e-mail address, you should instead use a database ID.  [Customer Profile]: /Getting-Started/entities#customer-profile 
-    # @param customer_profile_id [String] The custom identifier for this profile, must be unique within the account.
-    # @param body [NewCustomerProfile] 
+    # Update (or create) a [Customer Profile][].  The &#x60;integrationId&#x60; may be any identifier that will remain stable for the customer. For example, you might use a database ID, an email, or a phone number as the &#x60;integrationId&#x60;. It is vital that this ID **not** change over time, so **don&#39;t** use any identifier that the customer can update themselves. E.g. if your application allows a customer to update their e-mail address, you should instead use a database ID.  [Customer Profile]: /Getting-Started/entities#customer-profile 
+    # @param integration_id [String] The custom identifier for this profile, must be unique within the account.
+    # @param body [CustomerProfileIntegrationRequestV2] 
     # @param [Hash] opts the optional parameters
-    # @return [Array<(CustomerProfileUpdate, Integer, Hash)>] CustomerProfileUpdate data, response status code and response headers
-    def update_customer_profile_v2_with_http_info(customer_profile_id, body, opts = {})
+    # @option opts [Boolean] :run_rule_engine Flag to indicate whether to run the rule engine (Defaults to false).
+    # @option opts [Boolean] :dry Flag to indicate whether to skip persisting the changes or not (Will not persist if set to &#39;true&#39;. Only used when &#39;runRuleEngine&#39; is set to &#39;true&#39;).
+    # @return [Array<(IntegrationStateV2, Integer, Hash)>] IntegrationStateV2 data, response status code and response headers
+    def update_customer_profile_v2_with_http_info(integration_id, body, opts = {})
       if @api_client.config.debugging
         @api_client.config.logger.debug 'Calling API: IntegrationApi.update_customer_profile_v2 ...'
       end
-      # verify the required parameter 'customer_profile_id' is set
-      if @api_client.config.client_side_validation && customer_profile_id.nil?
-        fail ArgumentError, "Missing the required parameter 'customer_profile_id' when calling IntegrationApi.update_customer_profile_v2"
+      # verify the required parameter 'integration_id' is set
+      if @api_client.config.client_side_validation && integration_id.nil?
+        fail ArgumentError, "Missing the required parameter 'integration_id' when calling IntegrationApi.update_customer_profile_v2"
       end
       # verify the required parameter 'body' is set
       if @api_client.config.client_side_validation && body.nil?
         fail ArgumentError, "Missing the required parameter 'body' when calling IntegrationApi.update_customer_profile_v2"
       end
       # resource path
-      local_var_path = '/v2/customer_profiles/{customerProfileId}'.sub('{' + 'customerProfileId' + '}', CGI.escape(customer_profile_id.to_s))
+      local_var_path = '/v2/customer_profiles/{integrationId}'.sub('{' + 'integrationId' + '}', CGI.escape(integration_id.to_s))
 
       # query parameters
       query_params = opts[:query_params] || {}
+      query_params[:'runRuleEngine'] = opts[:'run_rule_engine'] if !opts[:'run_rule_engine'].nil?
+      query_params[:'dry'] = opts[:'dry'] if !opts[:'dry'].nil?
 
       # header parameters
       header_params = opts[:header_params] || {}
@@ -603,7 +674,7 @@ module TalonOne
       post_body = opts[:body] || @api_client.object_to_http_body(body) 
 
       # return_type
-      return_type = opts[:return_type] || 'CustomerProfileUpdate' 
+      return_type = opts[:return_type] || 'IntegrationStateV2' 
 
       # auth_names
       auth_names = opts[:auth_names] || ['api_key_v1']
@@ -624,8 +695,75 @@ module TalonOne
       return data, status_code, headers
     end
 
-    # Update a Customer Session
-    # Update (or create) a [Customer Session][]. For example, the items in a customers cart are part of a session.  The Talon.One platform supports multiple simultaneous sessions for the same profile, so if you have multiple ways of accessing the same application you have the option of either tracking multiple independent sessions or using the same session across all of them. You should share sessions when application access points share other state, such as the users cart. If two points of access to the application have independent state (e.g. a user can have different items in their cart across the two) they should use independent customer session ID's.  The `profileId` parameter in the request body should correspond to an `integrationId` for a customer profile, to track an anonymous session use the empty string (`\"\"`) as the `profileId`. Note that you do **not** need to create a customer profile first: if the specified profile does not yet exist, an empty profile will be created automatically.  Updating a customer profile will return a response with the full integration state. This includes the current state of the customer profile, the customer session, the event that was recorded, and an array of effects that took place.  The currency for the session and the cart items in the session is the same as that of the application with which the session is associated.  [Customer Session]: /Getting-Started/entities#customer-session 
+    # Update multiple Customer Profiles
+    # Update (or create) up to 1000 [Customer Profiles][] in 1 request.  The `integrationId` may be any identifier that will remain stable for the customer. For example, you might use a database ID, an email, or a phone number as the `integrationId`. It is vital that this ID **not** change over time, so **don't** use any identifier that the customer can update themselves. E.g. if your application allows a customer to update their e-mail address, you should instead use a database ID.  [Customer Profiles]: /Getting-Started/entities#customer-profile 
+    # @param body [MultipleCustomerProfileIntegrationRequest] 
+    # @param [Hash] opts the optional parameters
+    # @option opts [String] :silent If set to &#39;yes&#39;, response will be an empty 204, otherwise a list of the IntegrationStateV2  generated.
+    # @return [MultipleCustomerProfileIntegrationResponseV2]
+    def update_customer_profiles_v2(body, opts = {})
+      data, _status_code, _headers = update_customer_profiles_v2_with_http_info(body, opts)
+      data
+    end
+
+    # Update multiple Customer Profiles
+    # Update (or create) up to 1000 [Customer Profiles][] in 1 request.  The &#x60;integrationId&#x60; may be any identifier that will remain stable for the customer. For example, you might use a database ID, an email, or a phone number as the &#x60;integrationId&#x60;. It is vital that this ID **not** change over time, so **don&#39;t** use any identifier that the customer can update themselves. E.g. if your application allows a customer to update their e-mail address, you should instead use a database ID.  [Customer Profiles]: /Getting-Started/entities#customer-profile 
+    # @param body [MultipleCustomerProfileIntegrationRequest] 
+    # @param [Hash] opts the optional parameters
+    # @option opts [String] :silent If set to &#39;yes&#39;, response will be an empty 204, otherwise a list of the IntegrationStateV2  generated.
+    # @return [Array<(MultipleCustomerProfileIntegrationResponseV2, Integer, Hash)>] MultipleCustomerProfileIntegrationResponseV2 data, response status code and response headers
+    def update_customer_profiles_v2_with_http_info(body, opts = {})
+      if @api_client.config.debugging
+        @api_client.config.logger.debug 'Calling API: IntegrationApi.update_customer_profiles_v2 ...'
+      end
+      # verify the required parameter 'body' is set
+      if @api_client.config.client_side_validation && body.nil?
+        fail ArgumentError, "Missing the required parameter 'body' when calling IntegrationApi.update_customer_profiles_v2"
+      end
+      # resource path
+      local_var_path = '/v2/customer_profiles'
+
+      # query parameters
+      query_params = opts[:query_params] || {}
+      query_params[:'silent'] = opts[:'silent'] if !opts[:'silent'].nil?
+
+      # header parameters
+      header_params = opts[:header_params] || {}
+      # HTTP header 'Accept' (if needed)
+      header_params['Accept'] = @api_client.select_header_accept(['application/json'])
+      # HTTP header 'Content-Type'
+      header_params['Content-Type'] = @api_client.select_header_content_type(['application/json'])
+
+      # form parameters
+      form_params = opts[:form_params] || {}
+
+      # http body (model)
+      post_body = opts[:body] || @api_client.object_to_http_body(body) 
+
+      # return_type
+      return_type = opts[:return_type] || 'MultipleCustomerProfileIntegrationResponseV2' 
+
+      # auth_names
+      auth_names = opts[:auth_names] || ['api_key_v1']
+
+      new_options = opts.merge(
+        :header_params => header_params,
+        :query_params => query_params,
+        :form_params => form_params,
+        :body => post_body,
+        :auth_names => auth_names,
+        :return_type => return_type
+      )
+
+      data, status_code, headers = @api_client.call_api(:PUT, local_var_path, new_options)
+      if @api_client.config.debugging
+        @api_client.config.logger.debug "API called: IntegrationApi#update_customer_profiles_v2\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
+      end
+      return data, status_code, headers
+    end
+
+    # Update a Customer Session V1
+    # ⚠️ Deprecation Notice: Support for requests to this endpoint will end on 15.07.2021. We will not remove the endpoint, and it will still be accessible for you to use. For new features support, please migrate to [API V2.0](/Getting-Started/APIV2).  Update (or create) a [Customer Session][]. For example, the items in a customers cart are part of a session.  The Talon.One platform supports multiple simultaneous sessions for the same profile, so if you have multiple ways of accessing the same application you have the option of either tracking multiple independent sessions or using the same session across all of them. You should share sessions when application access points share other state, such as the users cart. If two points of access to the application have independent state (e.g. a user can have different items in their cart across the two) they should use independent customer session ID's.  The `profileId` parameter in the request body should correspond to an `integrationId` for a customer profile, to track an anonymous session use the empty string (`\"\"`) as the `profileId`. Note that you do **not** need to create a customer profile first: if the specified profile does not yet exist, an empty profile will be created automatically.  Updating a customer profile will return a response with the full integration state. This includes the current state of the customer profile, the customer session, the event that was recorded, and an array of effects that took place.  The currency for the session and the cart items in the session is the same as that of the application with which the session is associated.  [Customer Session]: /Getting-Started/entities#customer-session 
     # @param customer_session_id [String] The custom identifier for this session, must be unique within the account.
     # @param body [NewCustomerSession] 
     # @param [Hash] opts the optional parameters
@@ -636,8 +774,8 @@ module TalonOne
       data
     end
 
-    # Update a Customer Session
-    # Update (or create) a [Customer Session][]. For example, the items in a customers cart are part of a session.  The Talon.One platform supports multiple simultaneous sessions for the same profile, so if you have multiple ways of accessing the same application you have the option of either tracking multiple independent sessions or using the same session across all of them. You should share sessions when application access points share other state, such as the users cart. If two points of access to the application have independent state (e.g. a user can have different items in their cart across the two) they should use independent customer session ID&#39;s.  The &#x60;profileId&#x60; parameter in the request body should correspond to an &#x60;integrationId&#x60; for a customer profile, to track an anonymous session use the empty string (&#x60;\&quot;\&quot;&#x60;) as the &#x60;profileId&#x60;. Note that you do **not** need to create a customer profile first: if the specified profile does not yet exist, an empty profile will be created automatically.  Updating a customer profile will return a response with the full integration state. This includes the current state of the customer profile, the customer session, the event that was recorded, and an array of effects that took place.  The currency for the session and the cart items in the session is the same as that of the application with which the session is associated.  [Customer Session]: /Getting-Started/entities#customer-session 
+    # Update a Customer Session V1
+    # ⚠️ Deprecation Notice: Support for requests to this endpoint will end on 15.07.2021. We will not remove the endpoint, and it will still be accessible for you to use. For new features support, please migrate to [API V2.0](/Getting-Started/APIV2).  Update (or create) a [Customer Session][]. For example, the items in a customers cart are part of a session.  The Talon.One platform supports multiple simultaneous sessions for the same profile, so if you have multiple ways of accessing the same application you have the option of either tracking multiple independent sessions or using the same session across all of them. You should share sessions when application access points share other state, such as the users cart. If two points of access to the application have independent state (e.g. a user can have different items in their cart across the two) they should use independent customer session ID&#39;s.  The &#x60;profileId&#x60; parameter in the request body should correspond to an &#x60;integrationId&#x60; for a customer profile, to track an anonymous session use the empty string (&#x60;\&quot;\&quot;&#x60;) as the &#x60;profileId&#x60;. Note that you do **not** need to create a customer profile first: if the specified profile does not yet exist, an empty profile will be created automatically.  Updating a customer profile will return a response with the full integration state. This includes the current state of the customer profile, the customer session, the event that was recorded, and an array of effects that took place.  The currency for the session and the cart items in the session is the same as that of the application with which the session is associated.  [Customer Session]: /Getting-Started/entities#customer-session 
     # @param customer_session_id [String] The custom identifier for this session, must be unique within the account.
     # @param body [NewCustomerSession] 
     # @param [Hash] opts the optional parameters