talon_one 2.4.0 → 2.5.1

data/lib/talon_one/models/rollback_deducted_loyalty_points_effect_props.rb

@@ -1,7 +1,7 @@
 =begin
 #Talon.One API
 
-#The Talon.One API is used to manage applications and campaigns, as well as to integrate with your application. The operations in the _Integration API_ section are used to integrate with our platform, while the other operations are used to manage applications and campaigns.  ### Where is the API?  The API is available at the same hostname as these docs. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerProfile][] operation is `https://mycompany.talon.one/v1/customer_profiles/id`  [updateCustomerProfile]: #operation--v1-customer_profiles--integrationId--put 
+#Use the Talon.One API to integrate with your application and to manage applications and campaigns:  - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns.  ## Determining the base URL of the endpoints  The API is available at the same hostname as your Campaign Manager deployment. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerSession](https://docs.talon.one/integration-api/#operation/updateCustomerSessionV2) endpoint is `https://mycompany.talon.one/v2/customer_sessions/{Id}` 
 
 The version of the OpenAPI document: 1.0.0
 
@@ -36,6 +36,9 @@ module TalonOne
     # The identifier of 'addition' entries added to the ledger as the `deductLoyaltyPoints` effect is rolled back
     attr_accessor :transaction_uuid
 
+    # The card on which these points were added.
+    attr_accessor :card_identifier
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
@@ -45,7 +48,8 @@ module TalonOne
         :'recipient_integration_id' => :'recipientIntegrationId',
         :'start_date' => :'startDate',
         :'expiry_date' => :'expiryDate',
-        :'transaction_uuid' => :'transactionUUID'
+        :'transaction_uuid' => :'transactionUUID',
+        :'card_identifier' => :'cardIdentifier'
       }
     end
 
@@ -58,7 +62,8 @@ module TalonOne
         :'recipient_integration_id' => :'String',
         :'start_date' => :'DateTime',
         :'expiry_date' => :'DateTime',
-        :'transaction_uuid' => :'String'
+        :'transaction_uuid' => :'String',
+        :'card_identifier' => :'String'
       }
     end
 
@@ -110,6 +115,10 @@ module TalonOne
       if attributes.key?(:'transaction_uuid')
         self.transaction_uuid = attributes[:'transaction_uuid']
       end
+
+      if attributes.key?(:'card_identifier')
+        self.card_identifier = attributes[:'card_identifier']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -132,6 +141,10 @@ module TalonOne
         invalid_properties.push('invalid value for "recipient_integration_id", recipient_integration_id cannot be nil.')
       end
 
+      if @recipient_integration_id.to_s.length > 1000
+        invalid_properties.push('invalid value for "recipient_integration_id", the character length must be smaller than or equal to 1000.')
+      end
+
       if @transaction_uuid.nil?
         invalid_properties.push('invalid value for "transaction_uuid", transaction_uuid cannot be nil.')
       end
@@ -146,10 +159,25 @@ module TalonOne
       return false if @sub_ledger_id.nil?
       return false if @value.nil?
       return false if @recipient_integration_id.nil?
+      return false if @recipient_integration_id.to_s.length > 1000
       return false if @transaction_uuid.nil?
       true
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] recipient_integration_id Value to be assigned
+    def recipient_integration_id=(recipient_integration_id)
+      if recipient_integration_id.nil?
+        fail ArgumentError, 'recipient_integration_id cannot be nil'
+      end
+
+      if recipient_integration_id.to_s.length > 1000
+        fail ArgumentError, 'invalid value for "recipient_integration_id", the character length must be smaller than or equal to 1000.'
+      end
+
+      @recipient_integration_id = recipient_integration_id
+    end
+
     # Checks equality by comparing each attribute.
     # @param [Object] Object to be compared
     def ==(o)
@@ -161,7 +189,8 @@ module TalonOne
           recipient_integration_id == o.recipient_integration_id &&
           start_date == o.start_date &&
           expiry_date == o.expiry_date &&
-          transaction_uuid == o.transaction_uuid
+          transaction_uuid == o.transaction_uuid &&
+          card_identifier == o.card_identifier
     end
 
     # @see the `==` method
@@ -173,7 +202,7 @@ module TalonOne
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [program_id, sub_ledger_id, value, recipient_integration_id, start_date, expiry_date, transaction_uuid].hash
+      [program_id, sub_ledger_id, value, recipient_integration_id, start_date, expiry_date, transaction_uuid, card_identifier].hash
     end
 
     # Builds the object from hash

data/lib/talon_one/models/rollback_discount_effect_props.rb

@@ -1,7 +1,7 @@
 =begin
 #Talon.One API
 
-#The Talon.One API is used to manage applications and campaigns, as well as to integrate with your application. The operations in the _Integration API_ section are used to integrate with our platform, while the other operations are used to manage applications and campaigns.  ### Where is the API?  The API is available at the same hostname as these docs. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerProfile][] operation is `https://mycompany.talon.one/v1/customer_profiles/id`  [updateCustomerProfile]: #operation--v1-customer_profiles--integrationId--put 
+#Use the Talon.One API to integrate with your application and to manage applications and campaigns:  - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns.  ## Determining the base URL of the endpoints  The API is available at the same hostname as your Campaign Manager deployment. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerSession](https://docs.talon.one/integration-api/#operation/updateCustomerSessionV2) endpoint is `https://mycompany.talon.one/v2/customer_sessions/{Id}` 
 
 The version of the OpenAPI document: 1.0.0
 
@@ -13,19 +13,39 @@ OpenAPI Generator version: 4.3.1
 require 'date'
 
 module TalonOne
-  # The properties specific to the \"rollbackDiscount\" effect. This gets triggered whenever previously closed session is now cancelled and a setDiscount effect was cancelled on our internal discount limit counters.
+  # The properties specific to the \"rollbackDiscount\" effect. This gets triggered whenever previously closed session is now cancelled or partially returned and a setDiscount effect was cancelled on our internal discount limit counters.
   class RollbackDiscountEffectProps
     # The name of the \"setDiscount\" effect that was rolled back
     attr_accessor :name
 
-    # The value of the discount that was rolled back
+    # The value of the discount that was rolled back.
     attr_accessor :value
 
+    # The index of the item in the cart items for which the discount was rolled back.
+    attr_accessor :cart_item_position
+
+    # The index of the item unit in its line item. It is only used for cart items with `quantity` > 1 and is only returned when cart item flattening is enabled. 
+    attr_accessor :cart_item_sub_position
+
+    # The ID of the additional cost that was rolled back
+    attr_accessor :additional_cost_id
+
+    # The name of the additional cost that was rolled back
+    attr_accessor :additional_cost
+
+    # The scope of the rolled back discount - For a discount per session, it can be one of `cartItems`, `additionalCosts` or `sessionTotal` - For a discount per item, it can be one of `price`, `additionalCosts` or `itemTotal` 
+    attr_accessor :scope
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
         :'name' => :'name',
-        :'value' => :'value'
+        :'value' => :'value',
+        :'cart_item_position' => :'cartItemPosition',
+        :'cart_item_sub_position' => :'cartItemSubPosition',
+        :'additional_cost_id' => :'additionalCostId',
+        :'additional_cost' => :'additionalCost',
+        :'scope' => :'scope'
       }
     end
 
@@ -33,7 +53,12 @@ module TalonOne
     def self.openapi_types
       {
         :'name' => :'String',
-        :'value' => :'Float'
+        :'value' => :'Float',
+        :'cart_item_position' => :'Float',
+        :'cart_item_sub_position' => :'Float',
+        :'additional_cost_id' => :'Integer',
+        :'additional_cost' => :'String',
+        :'scope' => :'String'
       }
     end
 
@@ -65,6 +90,26 @@ module TalonOne
       if attributes.key?(:'value')
         self.value = attributes[:'value']
       end
+
+      if attributes.key?(:'cart_item_position')
+        self.cart_item_position = attributes[:'cart_item_position']
+      end
+
+      if attributes.key?(:'cart_item_sub_position')
+        self.cart_item_sub_position = attributes[:'cart_item_sub_position']
+      end
+
+      if attributes.key?(:'additional_cost_id')
+        self.additional_cost_id = attributes[:'additional_cost_id']
+      end
+
+      if attributes.key?(:'additional_cost')
+        self.additional_cost = attributes[:'additional_cost']
+      end
+
+      if attributes.key?(:'scope')
+        self.scope = attributes[:'scope']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -96,7 +141,12 @@ module TalonOne
       return true if self.equal?(o)
       self.class == o.class &&
           name == o.name &&
-          value == o.value
+          value == o.value &&
+          cart_item_position == o.cart_item_position &&
+          cart_item_sub_position == o.cart_item_sub_position &&
+          additional_cost_id == o.additional_cost_id &&
+          additional_cost == o.additional_cost &&
+          scope == o.scope
     end
 
     # @see the `==` method
@@ -108,7 +158,7 @@ module TalonOne
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [name, value].hash
+      [name, value, cart_item_position, cart_item_sub_position, additional_cost_id, additional_cost, scope].hash
     end
 
     # Builds the object from hash

data/lib/talon_one/models/rollback_referral_effect_props.rb

@@ -1,7 +1,7 @@
 =begin
 #Talon.One API
 
-#The Talon.One API is used to manage applications and campaigns, as well as to integrate with your application. The operations in the _Integration API_ section are used to integrate with our platform, while the other operations are used to manage applications and campaigns.  ### Where is the API?  The API is available at the same hostname as these docs. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerProfile][] operation is `https://mycompany.talon.one/v1/customer_profiles/id`  [updateCustomerProfile]: #operation--v1-customer_profiles--integrationId--put 
+#Use the Talon.One API to integrate with your application and to manage applications and campaigns:  - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns.  ## Determining the base URL of the endpoints  The API is available at the same hostname as your Campaign Manager deployment. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerSession](https://docs.talon.one/integration-api/#operation/updateCustomerSessionV2) endpoint is `https://mycompany.talon.one/v2/customer_sessions/{Id}` 
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/talon_one/models/rule.rb

@@ -1,7 +1,7 @@
 =begin
 #Talon.One API
 
-#The Talon.One API is used to manage applications and campaigns, as well as to integrate with your application. The operations in the _Integration API_ section are used to integrate with our platform, while the other operations are used to manage applications and campaigns.  ### Where is the API?  The API is available at the same hostname as these docs. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerProfile][] operation is `https://mycompany.talon.one/v1/customer_profiles/id`  [updateCustomerProfile]: #operation--v1-customer_profiles--integrationId--put 
+#Use the Talon.One API to integrate with your application and to manage applications and campaigns:  - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns.  ## Determining the base URL of the endpoints  The API is available at the same hostname as your Campaign Manager deployment. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerSession](https://docs.talon.one/integration-api/#operation/updateCustomerSessionV2) endpoint is `https://mycompany.talon.one/v2/customer_sessions/{Id}` 
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/talon_one/models/rule_failure_reason.rb

@@ -1,7 +1,7 @@
 =begin
 #Talon.One API
 
-#The Talon.One API is used to manage applications and campaigns, as well as to integrate with your application. The operations in the _Integration API_ section are used to integrate with our platform, while the other operations are used to manage applications and campaigns.  ### Where is the API?  The API is available at the same hostname as these docs. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerProfile][] operation is `https://mycompany.talon.one/v1/customer_profiles/id`  [updateCustomerProfile]: #operation--v1-customer_profiles--integrationId--put 
+#Use the Talon.One API to integrate with your application and to manage applications and campaigns:  - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns.  ## Determining the base URL of the endpoints  The API is available at the same hostname as your Campaign Manager deployment. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerSession](https://docs.talon.one/integration-api/#operation/updateCustomerSessionV2) endpoint is `https://mycompany.talon.one/v2/customer_sessions/{Id}` 
 
 The version of the OpenAPI document: 1.0.0
 
@@ -13,7 +13,7 @@ OpenAPI Generator version: 4.3.1
 require 'date'
 
 module TalonOne
-  # Details about why a rule failed
+  # Details about why a rule failed.
   class RuleFailureReason
     # The ID of the campaign that contains the rule that failed
     attr_accessor :campaign_id

data/lib/talon_one/models/ruleset.rb

@@ -1,7 +1,7 @@
 =begin
 #Talon.One API
 
-#The Talon.One API is used to manage applications and campaigns, as well as to integrate with your application. The operations in the _Integration API_ section are used to integrate with our platform, while the other operations are used to manage applications and campaigns.  ### Where is the API?  The API is available at the same hostname as these docs. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerProfile][] operation is `https://mycompany.talon.one/v1/customer_profiles/id`  [updateCustomerProfile]: #operation--v1-customer_profiles--integrationId--put 
+#Use the Talon.One API to integrate with your application and to manage applications and campaigns:  - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns.  ## Determining the base URL of the endpoints  The API is available at the same hostname as your Campaign Manager deployment. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerSession](https://docs.talon.one/integration-api/#operation/updateCustomerSessionV2) endpoint is `https://mycompany.talon.one/v2/customer_sessions/{Id}` 
 
 The version of the OpenAPI document: 1.0.0
 
@@ -21,9 +21,6 @@ module TalonOne
     # The exact moment this entity was created.
     attr_accessor :created
 
-    # The ID of the campaign that owns this entity.
-    attr_accessor :campaign_id
-
     # The ID of the account that owns this entity.
     attr_accessor :user_id
 
@@ -33,12 +30,18 @@ module TalonOne
     # An array that provides objects with variable names (name) and talang expressions to whose result they are bound (expression) during rule evaluation. The order of the evaluation is decided by the position in the array.
     attr_accessor :bindings
 
-    # A string indicating which version of the rulebuilder was used to create this ruleset.
+    # The version of the rulebuilder used to create this ruleset.
     attr_accessor :rb_version
 
-    # A boolean indicating whether this newly created ruleset should also be activated for the campaign owns it
+    # Indicates whether this created ruleset should be activated for the campaign that owns it.
     attr_accessor :activate
 
+    # The ID of the campaign that owns this entity.
+    attr_accessor :campaign_id
+
+    # The ID of the campaign template that owns this entity.
+    attr_accessor :template_id
+
     # Timestamp indicating when this Ruleset was activated.
     attr_accessor :activated_at
 
@@ -47,12 +50,13 @@ module TalonOne
       {
         :'id' => :'id',
         :'created' => :'created',
-        :'campaign_id' => :'campaignId',
         :'user_id' => :'userId',
         :'rules' => :'rules',
         :'bindings' => :'bindings',
         :'rb_version' => :'rbVersion',
         :'activate' => :'activate',
+        :'campaign_id' => :'campaignId',
+        :'template_id' => :'templateId',
         :'activated_at' => :'activatedAt'
       }
     end
@@ -62,12 +66,13 @@ module TalonOne
       {
         :'id' => :'Integer',
         :'created' => :'DateTime',
-        :'campaign_id' => :'Integer',
         :'user_id' => :'Integer',
         :'rules' => :'Array<Rule>',
         :'bindings' => :'Array<Binding>',
         :'rb_version' => :'String',
         :'activate' => :'Boolean',
+        :'campaign_id' => :'Integer',
+        :'template_id' => :'Integer',
         :'activated_at' => :'DateTime'
       }
     end
@@ -101,10 +106,6 @@ module TalonOne
         self.created = attributes[:'created']
       end
 
-      if attributes.key?(:'campaign_id')
-        self.campaign_id = attributes[:'campaign_id']
-      end
-
       if attributes.key?(:'user_id')
         self.user_id = attributes[:'user_id']
       end
@@ -129,6 +130,14 @@ module TalonOne
         self.activate = attributes[:'activate']
       end
 
+      if attributes.key?(:'campaign_id')
+        self.campaign_id = attributes[:'campaign_id']
+      end
+
+      if attributes.key?(:'template_id')
+        self.template_id = attributes[:'template_id']
+      end
+
       if attributes.key?(:'activated_at')
         self.activated_at = attributes[:'activated_at']
       end
@@ -146,10 +155,6 @@ module TalonOne
         invalid_properties.push('invalid value for "created", created cannot be nil.')
       end
 
-      if @campaign_id.nil?
-        invalid_properties.push('invalid value for "campaign_id", campaign_id cannot be nil.')
-      end
-
       if @user_id.nil?
         invalid_properties.push('invalid value for "user_id", user_id cannot be nil.')
       end
@@ -170,7 +175,6 @@ module TalonOne
     def valid?
       return false if @id.nil?
       return false if @created.nil?
-      return false if @campaign_id.nil?
       return false if @user_id.nil?
       return false if @rules.nil?
       return false if @bindings.nil?
@@ -184,12 +188,13 @@ module TalonOne
       self.class == o.class &&
           id == o.id &&
           created == o.created &&
-          campaign_id == o.campaign_id &&
           user_id == o.user_id &&
           rules == o.rules &&
           bindings == o.bindings &&
           rb_version == o.rb_version &&
           activate == o.activate &&
+          campaign_id == o.campaign_id &&
+          template_id == o.template_id &&
           activated_at == o.activated_at
     end
 
@@ -202,7 +207,7 @@ module TalonOne
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [id, created, campaign_id, user_id, rules, bindings, rb_version, activate, activated_at].hash
+      [id, created, user_id, rules, bindings, rb_version, activate, campaign_id, template_id, activated_at].hash
     end
 
     # Builds the object from hash

data/lib/talon_one/models/saml_connection.rb

@@ -1,7 +1,7 @@
 =begin
 #Talon.One API
 
-#The Talon.One API is used to manage applications and campaigns, as well as to integrate with your application. The operations in the _Integration API_ section are used to integrate with our platform, while the other operations are used to manage applications and campaigns.  ### Where is the API?  The API is available at the same hostname as these docs. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerProfile][] operation is `https://mycompany.talon.one/v1/customer_profiles/id`  [updateCustomerProfile]: #operation--v1-customer_profiles--integrationId--put 
+#Use the Talon.One API to integrate with your application and to manage applications and campaigns:  - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns.  ## Determining the base URL of the endpoints  The API is available at the same hostname as your Campaign Manager deployment. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerSession](https://docs.talon.one/integration-api/#operation/updateCustomerSessionV2) endpoint is `https://mycompany.talon.one/v2/customer_sessions/{Id}` 
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/talon_one/models/saml_connection_metadata.rb

@@ -1,7 +1,7 @@
 =begin
 #Talon.One API
 
-#The Talon.One API is used to manage applications and campaigns, as well as to integrate with your application. The operations in the _Integration API_ section are used to integrate with our platform, while the other operations are used to manage applications and campaigns.  ### Where is the API?  The API is available at the same hostname as these docs. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerProfile][] operation is `https://mycompany.talon.one/v1/customer_profiles/id`  [updateCustomerProfile]: #operation--v1-customer_profiles--integrationId--put 
+#Use the Talon.One API to integrate with your application and to manage applications and campaigns:  - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns.  ## Determining the base URL of the endpoints  The API is available at the same hostname as your Campaign Manager deployment. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerSession](https://docs.talon.one/integration-api/#operation/updateCustomerSessionV2) endpoint is `https://mycompany.talon.one/v2/customer_sessions/{Id}` 
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/talon_one/models/saml_login_endpoint.rb

@@ -1,7 +1,7 @@
 =begin
 #Talon.One API
 
-#The Talon.One API is used to manage applications and campaigns, as well as to integrate with your application. The operations in the _Integration API_ section are used to integrate with our platform, while the other operations are used to manage applications and campaigns.  ### Where is the API?  The API is available at the same hostname as these docs. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerProfile][] operation is `https://mycompany.talon.one/v1/customer_profiles/id`  [updateCustomerProfile]: #operation--v1-customer_profiles--integrationId--put 
+#Use the Talon.One API to integrate with your application and to manage applications and campaigns:  - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns.  ## Determining the base URL of the endpoints  The API is available at the same hostname as your Campaign Manager deployment. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerSession](https://docs.talon.one/integration-api/#operation/updateCustomerSessionV2) endpoint is `https://mycompany.talon.one/v2/customer_sessions/{Id}` 
 
 The version of the OpenAPI document: 1.0.0
 

data/lib/talon_one/models/session.rb

@@ -1,7 +1,7 @@
 =begin
 #Talon.One API
 
-#The Talon.One API is used to manage applications and campaigns, as well as to integrate with your application. The operations in the _Integration API_ section are used to integrate with our platform, while the other operations are used to manage applications and campaigns.  ### Where is the API?  The API is available at the same hostname as these docs. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerProfile][] operation is `https://mycompany.talon.one/v1/customer_profiles/id`  [updateCustomerProfile]: #operation--v1-customer_profiles--integrationId--put 
+#Use the Talon.One API to integrate with your application and to manage applications and campaigns:  - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns.  ## Determining the base URL of the endpoints  The API is available at the same hostname as your Campaign Manager deployment. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerSession](https://docs.talon.one/integration-api/#operation/updateCustomerSessionV2) endpoint is `https://mycompany.talon.one/v2/customer_sessions/{Id}` 
 
 The version of the OpenAPI document: 1.0.0
 
@@ -17,7 +17,7 @@ module TalonOne
     # The ID of the user of this session
     attr_accessor :user_id
 
-    # An opaque session identifier
+    # The token to use as a bearer token to query Management API endpoints.
     attr_accessor :token
 
     # Unix timestamp indicating when the session was first created.

data/lib/talon_one/models/set_discount_effect_props.rb

@@ -1,7 +1,7 @@
 =begin
 #Talon.One API
 
-#The Talon.One API is used to manage applications and campaigns, as well as to integrate with your application. The operations in the _Integration API_ section are used to integrate with our platform, while the other operations are used to manage applications and campaigns.  ### Where is the API?  The API is available at the same hostname as these docs. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerProfile][] operation is `https://mycompany.talon.one/v1/customer_profiles/id`  [updateCustomerProfile]: #operation--v1-customer_profiles--integrationId--put 
+#Use the Talon.One API to integrate with your application and to manage applications and campaigns:  - Use the operations in the [Integration API section](#integration-api) are used to integrate with our platform - Use the operation in the [Management API section](#management-api) to manage applications and campaigns.  ## Determining the base URL of the endpoints  The API is available at the same hostname as your Campaign Manager deployment. For example, if you are reading this page at `https://mycompany.talon.one/docs/api/`, the URL for the [updateCustomerSession](https://docs.talon.one/integration-api/#operation/updateCustomerSessionV2) endpoint is `https://mycompany.talon.one/v2/customer_sessions/{Id}` 
 
 The version of the OpenAPI document: 1.0.0
 
@@ -24,12 +24,16 @@ module TalonOne
     # The scope which the discount was applied on, can be one of (cartItems,additionalCosts,sessionTotal)
     attr_accessor :scope
 
+    # The original value of the discount
+    attr_accessor :desired_value
+
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
         :'name' => :'name',
         :'value' => :'value',
-        :'scope' => :'scope'
+        :'scope' => :'scope',
+        :'desired_value' => :'desiredValue'
       }
     end
 
@@ -38,7 +42,8 @@ module TalonOne
       {
         :'name' => :'String',
         :'value' => :'Float',
-        :'scope' => :'String'
+        :'scope' => :'String',
+        :'desired_value' => :'Float'
       }
     end
 
@@ -74,6 +79,10 @@ module TalonOne
       if attributes.key?(:'scope')
         self.scope = attributes[:'scope']
       end
+
+      if attributes.key?(:'desired_value')
+        self.desired_value = attributes[:'desired_value']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
@@ -106,7 +115,8 @@ module TalonOne
       self.class == o.class &&
           name == o.name &&
           value == o.value &&
-          scope == o.scope
+          scope == o.scope &&
+          desired_value == o.desired_value
     end
 
     # @see the `==` method
@@ -118,7 +128,7 @@ module TalonOne
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [name, value, scope].hash
+      [name, value, scope, desired_value].hash
     end
 
     # Builds the object from hash