talon_one 2.4.0 → 2.5.1

data/lib/talon_one/models/customer_session_v2.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
 
@@ -15,37 +15,43 @@ require 'date'
 module TalonOne
   # 
   class CustomerSessionV2
-    # The integration ID for this entity sent to and used in the Talon.One system.
-    attr_accessor :integration_id
+    # Unique ID for this entity.
+    attr_accessor :id
 
-    # The exact moment this entity was created.
+    # The exact moment this entity was created. The exact moment this entity was created.
     attr_accessor :created
 
+    # The integration ID for this entity sent to and used in the Talon.One system.
+    attr_accessor :integration_id
+
     # The ID of the application that owns this entity.
     attr_accessor :application_id
 
-    # ID of the customers profile as used within this Talon.One account. May be omitted or set to the empty string if the customer does not yet have a known profile ID.
+    # ID of the customers profile as used within this Talon.One account.  **Note:** If the customer does not yet have a known profileId, we recommend you use a guest profileId. 
     attr_accessor :profile_id
 
-    # Any coupon codes entered.
+    # Any coupon codes entered.  **Important**: If you [create a coupon budget](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets/#budget-types) for your campaign, ensure the session contains a coupon code by the time you close it. 
     attr_accessor :coupon_codes
 
-    # Any referral code entered.
+    # Any referral code entered.  **Important**: If you [create a referral budget](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets/#budget-types) for your campaign, ensure the session contains a referral code by the time you close it. 
     attr_accessor :referral_code
 
-    # Indicates the current state of the session. All sessions must start in the \"open\" state, after which valid transitions are...  1. open -> closed 2. open -> cancelled 3. closed -> cancelled 
+    # Any loyalty cards used.
+    attr_accessor :loyalty_cards
+
+    # Indicates the current state of the session. Sessions can be created as `open` or `closed`, after which valid transitions are:  1. `open` → `closed` 2. `open` → `cancelled` 3. `closed` → `cancelled`  For more information, see [Entites](/docs/dev/concepts/entities#customer-session). 
     attr_accessor :state
 
-    # All items the customer will be purchasing in this session
+    # The items to add to this sessions. - If cart item flattening is disabled: **Do not exceed 1000 items** (regardless of their `quantity`) per request. - If cart item flattening is enabled: **Do not exceed 1000 items** and ensure the sum of all cart item's `quantity` **does not exceed 10.000** per request. 
     attr_accessor :cart_items
 
-    # Any costs associated with the session that can not be explicitly attributed to cart items. Examples include shipping costs and service fees.
+    # Any costs associated with the session that can not be explicitly attributed to cart items. Examples include shipping costs and service fees. [Create them in the Campaign Manager](https://docs.talon.one/docs/product/account/dev-tools/managing-additional-costs/#creating-additional-costs) before setting them with this property. 
     attr_accessor :additional_costs
 
-    # Identifiers for the customer, this can be used for limits on values such as device ID.
+    # Session custom identifiers that you can set limits on or use inside your rules.  For example, you can use IP addresses as identifiers to potentially identify devices and limit discounts abuse in case of customers creating multiple accounts. See the [tutorial](https://docs.talon.one/docs/dev/tutorials/using-identifiers/).  **Important**: If you [create a unique identifier budget](https://docs.talon.one/docs/product/campaigns/settings/managing-campaign-budgets/#budget-types) for your campaign, ensure the session contains an identifier by the time you close it. 
     attr_accessor :identifiers
 
-    # A key-value map of the sessions attributes. The potentially valid attributes are configured in your accounts developer settings. 
+    # A key-value map of the sessions attributes. If you use custom attributes, they must be created in the Campaign Manager before you set them with this property. For more information, see [Attributes](https://docs.talon.one/docs/dev/concepts/attributes). 
     attr_accessor :attributes
 
     # Indicates whether this is the first session for the customer's profile. Will always be true for anonymous sessions.
@@ -60,6 +66,9 @@ module TalonOne
     # The total sum of additional costs before any discounts applied
     attr_accessor :additional_cost_total
 
+    # Timestamp of the most recent event received on this session
+    attr_accessor :updated
+
     class EnumAttributeValidator
       attr_reader :datatype
       attr_reader :allowable_values
@@ -85,12 +94,14 @@ module TalonOne
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
       {
-        :'integration_id' => :'integrationId',
+        :'id' => :'id',
         :'created' => :'created',
+        :'integration_id' => :'integrationId',
         :'application_id' => :'applicationId',
         :'profile_id' => :'profileId',
         :'coupon_codes' => :'couponCodes',
         :'referral_code' => :'referralCode',
+        :'loyalty_cards' => :'loyaltyCards',
         :'state' => :'state',
         :'cart_items' => :'cartItems',
         :'additional_costs' => :'additionalCosts',
@@ -99,19 +110,22 @@ module TalonOne
         :'first_session' => :'firstSession',
         :'total' => :'total',
         :'cart_item_total' => :'cartItemTotal',
-        :'additional_cost_total' => :'additionalCostTotal'
+        :'additional_cost_total' => :'additionalCostTotal',
+        :'updated' => :'updated'
       }
     end
 
     # Attribute type mapping.
     def self.openapi_types
       {
-        :'integration_id' => :'String',
+        :'id' => :'Integer',
         :'created' => :'DateTime',
+        :'integration_id' => :'String',
         :'application_id' => :'Integer',
         :'profile_id' => :'String',
         :'coupon_codes' => :'Array<String>',
         :'referral_code' => :'String',
+        :'loyalty_cards' => :'Array<String>',
         :'state' => :'String',
         :'cart_items' => :'Array<CartItem>',
         :'additional_costs' => :'Hash<String, AdditionalCost>',
@@ -120,7 +134,8 @@ module TalonOne
         :'first_session' => :'Boolean',
         :'total' => :'Float',
         :'cart_item_total' => :'Float',
-        :'additional_cost_total' => :'Float'
+        :'additional_cost_total' => :'Float',
+        :'updated' => :'DateTime'
       }
     end
 
@@ -145,14 +160,18 @@ module TalonOne
         h[k.to_sym] = v
       }
 
-      if attributes.key?(:'integration_id')
-        self.integration_id = attributes[:'integration_id']
+      if attributes.key?(:'id')
+        self.id = attributes[:'id']
       end
 
       if attributes.key?(:'created')
         self.created = attributes[:'created']
       end
 
+      if attributes.key?(:'integration_id')
+        self.integration_id = attributes[:'integration_id']
+      end
+
       if attributes.key?(:'application_id')
         self.application_id = attributes[:'application_id']
       end
@@ -171,6 +190,12 @@ module TalonOne
         self.referral_code = attributes[:'referral_code']
       end
 
+      if attributes.key?(:'loyalty_cards')
+        if (value = attributes[:'loyalty_cards']).is_a?(Array)
+          self.loyalty_cards = value
+        end
+      end
+
       if attributes.key?(:'state')
         self.state = attributes[:'state']
       else
@@ -214,20 +239,32 @@ module TalonOne
       if attributes.key?(:'additional_cost_total')
         self.additional_cost_total = attributes[:'additional_cost_total']
       end
+
+      if attributes.key?(:'updated')
+        self.updated = attributes[:'updated']
+      end
     end
 
     # Show invalid properties with the reasons. Usually used together with valid?
     # @return Array for valid properties with the reasons
     def list_invalid_properties
       invalid_properties = Array.new
-      if @integration_id.nil?
-        invalid_properties.push('invalid value for "integration_id", integration_id cannot be nil.')
+      if @id.nil?
+        invalid_properties.push('invalid value for "id", id cannot be nil.')
       end
 
       if @created.nil?
         invalid_properties.push('invalid value for "created", created cannot be nil.')
       end
 
+      if @integration_id.nil?
+        invalid_properties.push('invalid value for "integration_id", integration_id cannot be nil.')
+      end
+
+      if @integration_id.to_s.length > 1000
+        invalid_properties.push('invalid value for "integration_id", the character length must be smaller than or equal to 1000.')
+      end
+
       if @application_id.nil?
         invalid_properties.push('invalid value for "application_id", application_id cannot be nil.')
       end
@@ -268,19 +305,25 @@ module TalonOne
         invalid_properties.push('invalid value for "additional_cost_total", additional_cost_total cannot be nil.')
       end
 
+      if @updated.nil?
+        invalid_properties.push('invalid value for "updated", updated cannot be nil.')
+      end
+
       invalid_properties
     end
 
     # Check to see if the all the properties in the model are valid
     # @return true if the model is valid
     def valid?
-      return false if @integration_id.nil?
+      return false if @id.nil?
       return false if @created.nil?
+      return false if @integration_id.nil?
+      return false if @integration_id.to_s.length > 1000
       return false if @application_id.nil?
       return false if @profile_id.nil?
       return false if !@referral_code.nil? && @referral_code.to_s.length > 100
       return false if @state.nil?
-      state_validator = EnumAttributeValidator.new('String', ["open", "closed", "cancelled"])
+      state_validator = EnumAttributeValidator.new('String', ["open", "closed", "partially_returned", "cancelled"])
       return false unless state_validator.valid?(@state)
       return false if @cart_items.nil?
       return false if @attributes.nil?
@@ -288,9 +331,24 @@ module TalonOne
       return false if @total.nil?
       return false if @cart_item_total.nil?
       return false if @additional_cost_total.nil?
+      return false if @updated.nil?
       true
     end
 
+    # Custom attribute writer method with validation
+    # @param [Object] integration_id Value to be assigned
+    def integration_id=(integration_id)
+      if integration_id.nil?
+        fail ArgumentError, 'integration_id cannot be nil'
+      end
+
+      if integration_id.to_s.length > 1000
+        fail ArgumentError, 'invalid value for "integration_id", the character length must be smaller than or equal to 1000.'
+      end
+
+      @integration_id = integration_id
+    end
+
     # Custom attribute writer method with validation
     # @param [Object] referral_code Value to be assigned
     def referral_code=(referral_code)
@@ -304,7 +362,7 @@ module TalonOne
     # Custom attribute writer method checking allowed values (enum).
     # @param [Object] state Object to be assigned
     def state=(state)
-      validator = EnumAttributeValidator.new('String', ["open", "closed", "cancelled"])
+      validator = EnumAttributeValidator.new('String', ["open", "closed", "partially_returned", "cancelled"])
       unless validator.valid?(state)
         fail ArgumentError, "invalid value for \"state\", must be one of #{validator.allowable_values}."
       end
@@ -316,12 +374,14 @@ module TalonOne
     def ==(o)
       return true if self.equal?(o)
       self.class == o.class &&
-          integration_id == o.integration_id &&
+          id == o.id &&
           created == o.created &&
+          integration_id == o.integration_id &&
           application_id == o.application_id &&
           profile_id == o.profile_id &&
           coupon_codes == o.coupon_codes &&
           referral_code == o.referral_code &&
+          loyalty_cards == o.loyalty_cards &&
           state == o.state &&
           cart_items == o.cart_items &&
           additional_costs == o.additional_costs &&
@@ -330,7 +390,8 @@ module TalonOne
           first_session == o.first_session &&
           total == o.total &&
           cart_item_total == o.cart_item_total &&
-          additional_cost_total == o.additional_cost_total
+          additional_cost_total == o.additional_cost_total &&
+          updated == o.updated
     end
 
     # @see the `==` method
@@ -342,7 +403,7 @@ module TalonOne
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [integration_id, created, application_id, profile_id, coupon_codes, referral_code, state, cart_items, additional_costs, identifiers, attributes, first_session, total, cart_item_total, additional_cost_total].hash
+      [id, created, integration_id, application_id, profile_id, coupon_codes, referral_code, loyalty_cards, state, cart_items, additional_costs, identifiers, attributes, first_session, total, cart_item_total, additional_cost_total, updated].hash
     end
 
     # Builds the object from hash

data/lib/talon_one/models/deduct_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
 
@@ -30,6 +30,12 @@ module TalonOne
     # The identifier of this deduction in the loyalty ledger
     attr_accessor :transaction_uuid
 
+    # The name property gets one of the following two values. It can be the loyalty program name or it can represent a reason for the respective deduction of loyalty points. The latter is an optional value defined in a deduction rule. 
+    attr_accessor :name
+
+    # 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
       {
@@ -37,7 +43,9 @@ module TalonOne
         :'program_id' => :'programId',
         :'sub_ledger_id' => :'subLedgerId',
         :'value' => :'value',
-        :'transaction_uuid' => :'transactionUUID'
+        :'transaction_uuid' => :'transactionUUID',
+        :'name' => :'name',
+        :'card_identifier' => :'cardIdentifier'
       }
     end
 
@@ -48,7 +56,9 @@ module TalonOne
         :'program_id' => :'Integer',
         :'sub_ledger_id' => :'String',
         :'value' => :'Float',
-        :'transaction_uuid' => :'String'
+        :'transaction_uuid' => :'String',
+        :'name' => :'String',
+        :'card_identifier' => :'String'
       }
     end
 
@@ -92,6 +102,14 @@ module TalonOne
       if attributes.key?(:'transaction_uuid')
         self.transaction_uuid = attributes[:'transaction_uuid']
       end
+
+      if attributes.key?(:'name')
+        self.name = attributes[:'name']
+      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?
@@ -118,6 +136,10 @@ module TalonOne
         invalid_properties.push('invalid value for "transaction_uuid", transaction_uuid cannot be nil.')
       end
 
+      if @name.nil?
+        invalid_properties.push('invalid value for "name", name cannot be nil.')
+      end
+
       invalid_properties
     end
 
@@ -129,6 +151,7 @@ module TalonOne
       return false if @sub_ledger_id.nil?
       return false if @value.nil?
       return false if @transaction_uuid.nil?
+      return false if @name.nil?
       true
     end
 
@@ -141,7 +164,9 @@ module TalonOne
           program_id == o.program_id &&
           sub_ledger_id == o.sub_ledger_id &&
           value == o.value &&
-          transaction_uuid == o.transaction_uuid
+          transaction_uuid == o.transaction_uuid &&
+          name == o.name &&
+          card_identifier == o.card_identifier
     end
 
     # @see the `==` method
@@ -153,7 +178,7 @@ module TalonOne
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [rule_title, program_id, sub_ledger_id, value, transaction_uuid].hash
+      [rule_title, program_id, sub_ledger_id, value, transaction_uuid, name, card_identifier].hash
     end
 
     # Builds the object from hash

data/lib/talon_one/models/effect.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/effect_entity.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/email_entity.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/entity.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/entity_with_talang_visible_id.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/environment.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
 
@@ -33,6 +33,9 @@ module TalonOne
     # The templates defined for this application.
     attr_accessor :templates
 
+    # A stringified version of the environment's Talang variables scope
+    attr_accessor :variables
+
     # The giveaways pools that the application is subscribed to.
     attr_accessor :giveaways_pools
 
@@ -48,7 +51,8 @@ module TalonOne
     # The audiences contained in the account which the application belongs to.
     attr_accessor :audiences
 
-    attr_accessor :variables
+    # The account-level collections that the application is subscribed to.
+    attr_accessor :collections
 
     # Attribute mapping from ruby-style variable name to JSON key.
     def self.attribute_map
@@ -59,12 +63,13 @@ module TalonOne
         :'slots' => :'slots',
         :'functions' => :'functions',
         :'templates' => :'templates',
+        :'variables' => :'variables',
         :'giveaways_pools' => :'giveawaysPools',
         :'loyalty_programs' => :'loyaltyPrograms',
         :'attributes' => :'attributes',
         :'additional_costs' => :'additionalCosts',
         :'audiences' => :'audiences',
-        :'variables' => :'variables'
+        :'collections' => :'collections'
       }
     end
 
@@ -77,12 +82,13 @@ module TalonOne
         :'slots' => :'Array<SlotDef>',
         :'functions' => :'Array<FunctionDef>',
         :'templates' => :'Array<TemplateDef>',
+        :'variables' => :'String',
         :'giveaways_pools' => :'Array<GiveawaysPool>',
         :'loyalty_programs' => :'Array<LoyaltyProgram>',
         :'attributes' => :'Array<Attribute>',
         :'additional_costs' => :'Array<AccountAdditionalCost>',
         :'audiences' => :'Array<Audience>',
-        :'variables' => :'String'
+        :'collections' => :'Array<Collection>'
       }
     end
 
@@ -137,6 +143,10 @@ module TalonOne
         end
       end
 
+      if attributes.key?(:'variables')
+        self.variables = attributes[:'variables']
+      end
+
       if attributes.key?(:'giveaways_pools')
         if (value = attributes[:'giveaways_pools']).is_a?(Array)
           self.giveaways_pools = value
@@ -167,8 +177,10 @@ module TalonOne
         end
       end
 
-      if attributes.key?(:'variables')
-        self.variables = attributes[:'variables']
+      if attributes.key?(:'collections')
+        if (value = attributes[:'collections']).is_a?(Array)
+          self.collections = value
+        end
       end
     end
 
@@ -231,12 +243,13 @@ module TalonOne
           slots == o.slots &&
           functions == o.functions &&
           templates == o.templates &&
+          variables == o.variables &&
           giveaways_pools == o.giveaways_pools &&
           loyalty_programs == o.loyalty_programs &&
           attributes == o.attributes &&
           additional_costs == o.additional_costs &&
           audiences == o.audiences &&
-          variables == o.variables
+          collections == o.collections
     end
 
     # @see the `==` method
@@ -248,7 +261,7 @@ module TalonOne
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [id, created, application_id, slots, functions, templates, giveaways_pools, loyalty_programs, attributes, additional_costs, audiences, variables].hash
+      [id, created, application_id, slots, functions, templates, variables, giveaways_pools, loyalty_programs, attributes, additional_costs, audiences, collections].hash
     end
 
     # Builds the object from hash

data/lib/talon_one/models/error_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/error_response.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