hubspot-api-client 17.2.0 → 18.0.0

data/lib/hubspot/codegen/cms/domains/models/error_detail.rb

@@ -1,5 +1,5 @@
 =begin
-#Domains
+#CMS Domains
 
 #No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 
@@ -17,29 +17,29 @@ module Hubspot
   module Cms
     module Domains
       class ErrorDetail
-        # A human readable message describing the error along with remediation steps where appropriate
-        attr_accessor :message
-
-        # The name of the field or parameter in which the error was found.
-        attr_accessor :_in
+        # A specific category that contains more specific detail about the error
+        attr_accessor :sub_category
 
         # The status code associated with the error detail
         attr_accessor :code
 
-        # A specific category that contains more specific detail about the error
-        attr_accessor :sub_category
+        # The name of the field or parameter in which the error was found.
+        attr_accessor :_in
 
         # Context about the error condition
         attr_accessor :context
 
+        # A human readable message describing the error along with remediation steps where appropriate
+        attr_accessor :message
+
         # Attribute mapping from ruby-style variable name to JSON key.
         def self.attribute_map
           {
-            :'message' => :'message',
-            :'_in' => :'in',
-            :'code' => :'code',
             :'sub_category' => :'subCategory',
-            :'context' => :'context'
+            :'code' => :'code',
+            :'_in' => :'in',
+            :'context' => :'context',
+            :'message' => :'message'
           }
         end
 
@@ -51,11 +51,11 @@ module Hubspot
         # Attribute type mapping.
         def self.openapi_types
           {
-            :'message' => :'String',
-            :'_in' => :'String',
-            :'code' => :'String',
             :'sub_category' => :'String',
-            :'context' => :'Hash<String, Array<String>>'
+            :'code' => :'String',
+            :'_in' => :'String',
+            :'context' => :'Hash<String, Array<String>>',
+            :'message' => :'String'
           }
         end
 
@@ -80,20 +80,16 @@ module Hubspot
             h[k.to_sym] = v
           }
 
-          if attributes.key?(:'message')
-            self.message = attributes[:'message']
-          end
-
-          if attributes.key?(:'_in')
-            self._in = attributes[:'_in']
+          if attributes.key?(:'sub_category')
+            self.sub_category = attributes[:'sub_category']
           end
 
           if attributes.key?(:'code')
             self.code = attributes[:'code']
           end
 
-          if attributes.key?(:'sub_category')
-            self.sub_category = attributes[:'sub_category']
+          if attributes.key?(:'_in')
+            self._in = attributes[:'_in']
           end
 
           if attributes.key?(:'context')
@@ -101,6 +97,10 @@ module Hubspot
               self.context = value
             end
           end
+
+          if attributes.key?(:'message')
+            self.message = attributes[:'message']
+          end
         end
 
         # Show invalid properties with the reasons. Usually used together with valid?
@@ -126,11 +126,11 @@ module Hubspot
         def ==(o)
           return true if self.equal?(o)
           self.class == o.class &&
-              message == o.message &&
-              _in == o._in &&
-              code == o.code &&
               sub_category == o.sub_category &&
-              context == o.context
+              code == o.code &&
+              _in == o._in &&
+              context == o.context &&
+              message == o.message
         end
 
         # @see the `==` method
@@ -142,7 +142,7 @@ module Hubspot
         # Calculates hash code according to all attributes.
         # @return [Integer] Hash code
         def hash
-          [message, _in, code, sub_category, context].hash
+          [sub_category, code, _in, context, message].hash
         end
 
         # Builds the object from hash

data/lib/hubspot/codegen/cms/domains/models/forward_paging.rb

@@ -1,5 +1,5 @@
 =begin
-#Domains
+#CMS Domains
 
 #No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 

data/lib/hubspot/codegen/cms/domains/models/next_page.rb

@@ -1,5 +1,5 @@
 =begin
-#Domains
+#CMS Domains
 
 #No description provided (generated by Openapi Generator https://github.com/openapitools/openapi-generator)
 
@@ -17,15 +17,15 @@ module Hubspot
   module Cms
     module Domains
       class NextPage
-        attr_accessor :after
-
         attr_accessor :link
 
+        attr_accessor :after
+
         # Attribute mapping from ruby-style variable name to JSON key.
         def self.attribute_map
           {
-            :'after' => :'after',
-            :'link' => :'link'
+            :'link' => :'link',
+            :'after' => :'after'
           }
         end
 
@@ -37,8 +37,8 @@ module Hubspot
         # Attribute type mapping.
         def self.openapi_types
           {
-            :'after' => :'String',
-            :'link' => :'String'
+            :'link' => :'String',
+            :'after' => :'String'
           }
         end
 
@@ -63,13 +63,13 @@ module Hubspot
             h[k.to_sym] = v
           }
 
-          if attributes.key?(:'after')
-            self.after = attributes[:'after']
-          end
-
           if attributes.key?(:'link')
             self.link = attributes[:'link']
           end
+
+          if attributes.key?(:'after')
+            self.after = attributes[:'after']
+          end
         end
 
         # Show invalid properties with the reasons. Usually used together with valid?
@@ -95,8 +95,8 @@ module Hubspot
         def ==(o)
           return true if self.equal?(o)
           self.class == o.class &&
-              after == o.after &&
-              link == o.link
+              link == o.link &&
+              after == o.after
         end
 
         # @see the `==` method
@@ -108,7 +108,7 @@ module Hubspot
         # Calculates hash code according to all attributes.
         # @return [Integer] Hash code
         def hash
-          [after, link].hash
+          [link, after].hash
         end
 
         # Builds the object from hash

data/lib/hubspot/codegen/cms/hubdb/api/rows_api.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 

data/lib/hubspot/codegen/cms/hubdb/api/rows_batch_api.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 

data/lib/hubspot/codegen/cms/hubdb/api/tables_api.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 

data/lib/hubspot/codegen/cms/hubdb/api_client.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 

data/lib/hubspot/codegen/cms/hubdb/api_error.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 

data/lib/hubspot/codegen/cms/hubdb/configuration.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 

data/lib/hubspot/codegen/cms/hubdb/models/batch_input_hub_db_table_row_v3_batch_update_request.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 

data/lib/hubspot/codegen/cms/hubdb/models/batch_input_hub_db_table_row_v3_request.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
@@ -17,6 +17,7 @@ module Hubspot
   module Cms
     module Hubdb
       class BatchInputHubDbTableRowV3Request
+        # 
         attr_accessor :inputs
 
         # Attribute mapping from ruby-style variable name to JSON key.

data/lib/hubspot/codegen/cms/hubdb/models/batch_input_string.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
@@ -17,6 +17,7 @@ module Hubspot
   module Cms
     module Hubdb
       class BatchInputString
+        # 
         attr_accessor :inputs
 
         # Attribute mapping from ruby-style variable name to JSON key.

data/lib/hubspot/codegen/cms/hubdb/models/batch_response_hub_db_table_row_v3.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
@@ -17,18 +17,18 @@ module Hubspot
   module Cms
     module Hubdb
       class BatchResponseHubDbTableRowV3
-        attr_accessor :status
-
-        attr_accessor :results
+        attr_accessor :completed_at
 
         attr_accessor :requested_at
 
         attr_accessor :started_at
 
-        attr_accessor :completed_at
-
         attr_accessor :links
 
+        attr_accessor :results
+
+        attr_accessor :status
+
         class EnumAttributeValidator
           attr_reader :datatype
           attr_reader :allowable_values
@@ -54,12 +54,12 @@ module Hubspot
         # Attribute mapping from ruby-style variable name to JSON key.
         def self.attribute_map
           {
-            :'status' => :'status',
-            :'results' => :'results',
+            :'completed_at' => :'completedAt',
             :'requested_at' => :'requestedAt',
             :'started_at' => :'startedAt',
-            :'completed_at' => :'completedAt',
-            :'links' => :'links'
+            :'links' => :'links',
+            :'results' => :'results',
+            :'status' => :'status'
           }
         end
 
@@ -71,12 +71,12 @@ module Hubspot
         # Attribute type mapping.
         def self.openapi_types
           {
-            :'status' => :'String',
-            :'results' => :'Array<HubDbTableRowV3>',
+            :'completed_at' => :'Time',
             :'requested_at' => :'Time',
             :'started_at' => :'Time',
-            :'completed_at' => :'Time',
-            :'links' => :'Hash<String, String>'
+            :'links' => :'Hash<String, String>',
+            :'results' => :'Array<HubDbTableRowV3>',
+            :'status' => :'String'
           }
         end
 
@@ -101,14 +101,8 @@ module Hubspot
             h[k.to_sym] = v
           }
 
-          if attributes.key?(:'status')
-            self.status = attributes[:'status']
-          end
-
-          if attributes.key?(:'results')
-            if (value = attributes[:'results']).is_a?(Array)
-              self.results = value
-            end
+          if attributes.key?(:'completed_at')
+            self.completed_at = attributes[:'completed_at']
           end
 
           if attributes.key?(:'requested_at')
@@ -119,15 +113,21 @@ module Hubspot
             self.started_at = attributes[:'started_at']
           end
 
-          if attributes.key?(:'completed_at')
-            self.completed_at = attributes[:'completed_at']
-          end
-
           if attributes.key?(:'links')
             if (value = attributes[:'links']).is_a?(Hash)
               self.links = value
             end
           end
+
+          if attributes.key?(:'results')
+            if (value = attributes[:'results']).is_a?(Array)
+              self.results = value
+            end
+          end
+
+          if attributes.key?(:'status')
+            self.status = attributes[:'status']
+          end
         end
 
         # Show invalid properties with the reasons. Usually used together with valid?
@@ -160,12 +160,12 @@ module Hubspot
         def ==(o)
           return true if self.equal?(o)
           self.class == o.class &&
-              status == o.status &&
-              results == o.results &&
+              completed_at == o.completed_at &&
               requested_at == o.requested_at &&
               started_at == o.started_at &&
-              completed_at == o.completed_at &&
-              links == o.links
+              links == o.links &&
+              results == o.results &&
+              status == o.status
         end
 
         # @see the `==` method
@@ -177,7 +177,7 @@ module Hubspot
         # Calculates hash code according to all attributes.
         # @return [Integer] Hash code
         def hash
-          [status, results, requested_at, started_at, completed_at, links].hash
+          [completed_at, requested_at, started_at, links, results, status].hash
         end
 
         # Builds the object from hash

data/lib/hubspot/codegen/cms/hubdb/models/batch_response_hub_db_table_row_v3_with_errors.rb

@@ -1,5 +1,5 @@
 =begin
-#HubDB endpoints
+#Hubdb
 
 #HubDB is a relational data store that presents data as rows, columns, and cells in a table, much like a spreadsheet. HubDB tables can be added or modified [in the HubSpot CMS](https://knowledge.hubspot.com/cos-general/how-to-edit-hubdb-tables), but you can also use the API endpoints documented here. For more information on HubDB tables and using their data on a HubSpot site, see the [CMS developers site](https://designers.hubspot.com/docs/tools/hubdb). You can also see the [documentation for dynamic pages](https://designers.hubspot.com/docs/tutorials/how-to-build-dynamic-pages-with-hubdb) for more details about the `useForPages` field.  HubDB tables support `draft` and `published` versions. This allows you to update data in the table, either for testing or to allow for a manual approval process, without affecting any live pages using the existing data. Draft data can be reviewed, and published by a user working in HubSpot or published via the API. Draft data can also be discarded, allowing users to go back to the published version of the data without disrupting it. If a table is set to be `allowed for public access`, you can access the published version of the table and rows without any authentication by specifying the portal id via the query parameter `portalId`.
 
@@ -17,22 +17,30 @@ module Hubspot
   module Cms
     module Hubdb
       class BatchResponseHubDbTableRowV3WithErrors
-        attr_accessor :status
-
-        attr_accessor :results
+        # 
+        attr_accessor :completed_at
 
+        # 
         attr_accessor :num_errors
 
-        attr_accessor :errors
-
+        # 
         attr_accessor :requested_at
 
+        # 
         attr_accessor :started_at
 
-        attr_accessor :completed_at
-
+        # 
         attr_accessor :links
 
+        # 
+        attr_accessor :results
+
+        # 
+        attr_accessor :errors
+
+        # 
+        attr_accessor :status
+
         class EnumAttributeValidator
           attr_reader :datatype
           attr_reader :allowable_values
@@ -58,14 +66,14 @@ module Hubspot
         # Attribute mapping from ruby-style variable name to JSON key.
         def self.attribute_map
           {
-            :'status' => :'status',
-            :'results' => :'results',
+            :'completed_at' => :'completedAt',
             :'num_errors' => :'numErrors',
-            :'errors' => :'errors',
             :'requested_at' => :'requestedAt',
             :'started_at' => :'startedAt',
-            :'completed_at' => :'completedAt',
-            :'links' => :'links'
+            :'links' => :'links',
+            :'results' => :'results',
+            :'errors' => :'errors',
+            :'status' => :'status'
           }
         end
 
@@ -77,14 +85,14 @@ module Hubspot
         # Attribute type mapping.
         def self.openapi_types
           {
-            :'status' => :'String',
-            :'results' => :'Array<HubDbTableRowV3>',
+            :'completed_at' => :'Time',
             :'num_errors' => :'Integer',
-            :'errors' => :'Array<StandardError>',
             :'requested_at' => :'Time',
             :'started_at' => :'Time',
-            :'completed_at' => :'Time',
-            :'links' => :'Hash<String, String>'
+            :'links' => :'Hash<String, String>',
+            :'results' => :'Array<HubDbTableRowV3>',
+            :'errors' => :'Array<StandardError>',
+            :'status' => :'String'
           }
         end
 
@@ -109,26 +117,14 @@ module Hubspot
             h[k.to_sym] = v
           }
 
-          if attributes.key?(:'status')
-            self.status = attributes[:'status']
-          end
-
-          if attributes.key?(:'results')
-            if (value = attributes[:'results']).is_a?(Array)
-              self.results = value
-            end
+          if attributes.key?(:'completed_at')
+            self.completed_at = attributes[:'completed_at']
           end
 
           if attributes.key?(:'num_errors')
             self.num_errors = attributes[:'num_errors']
           end
 
-          if attributes.key?(:'errors')
-            if (value = attributes[:'errors']).is_a?(Array)
-              self.errors = value
-            end
-          end
-
           if attributes.key?(:'requested_at')
             self.requested_at = attributes[:'requested_at']
           end
@@ -137,35 +133,47 @@ module Hubspot
             self.started_at = attributes[:'started_at']
           end
 
-          if attributes.key?(:'completed_at')
-            self.completed_at = attributes[:'completed_at']
-          end
-
           if attributes.key?(:'links')
             if (value = attributes[:'links']).is_a?(Hash)
               self.links = value
             end
           end
+
+          if attributes.key?(:'results')
+            if (value = attributes[:'results']).is_a?(Array)
+              self.results = value
+            end
+          end
+
+          if attributes.key?(:'errors')
+            if (value = attributes[:'errors']).is_a?(Array)
+              self.errors = value
+            end
+          end
+
+          if attributes.key?(:'status')
+            self.status = attributes[:'status']
+          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 @status.nil?
-            invalid_properties.push('invalid value for "status", status cannot be nil.')
-          end
-
-          if @results.nil?
-            invalid_properties.push('invalid value for "results", results cannot be nil.')
+          if @completed_at.nil?
+            invalid_properties.push('invalid value for "completed_at", completed_at cannot be nil.')
           end
 
           if @started_at.nil?
             invalid_properties.push('invalid value for "started_at", started_at cannot be nil.')
           end
 
-          if @completed_at.nil?
-            invalid_properties.push('invalid value for "completed_at", completed_at cannot be nil.')
+          if @results.nil?
+            invalid_properties.push('invalid value for "results", results cannot be nil.')
+          end
+
+          if @status.nil?
+            invalid_properties.push('invalid value for "status", status cannot be nil.')
           end
 
           invalid_properties
@@ -174,12 +182,12 @@ module Hubspot
         # 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 @completed_at.nil?
+          return false if @started_at.nil?
+          return false if @results.nil?
           return false if @status.nil?
           status_validator = EnumAttributeValidator.new('String', ["PENDING", "PROCESSING", "CANCELED", "COMPLETE"])
           return false unless status_validator.valid?(@status)
-          return false if @results.nil?
-          return false if @started_at.nil?
-          return false if @completed_at.nil?
           true
         end
 
@@ -198,14 +206,14 @@ module Hubspot
         def ==(o)
           return true if self.equal?(o)
           self.class == o.class &&
-              status == o.status &&
-              results == o.results &&
+              completed_at == o.completed_at &&
               num_errors == o.num_errors &&
-              errors == o.errors &&
               requested_at == o.requested_at &&
               started_at == o.started_at &&
-              completed_at == o.completed_at &&
-              links == o.links
+              links == o.links &&
+              results == o.results &&
+              errors == o.errors &&
+              status == o.status
         end
 
         # @see the `==` method
@@ -217,7 +225,7 @@ module Hubspot
         # Calculates hash code according to all attributes.
         # @return [Integer] Hash code
         def hash
-          [status, results, num_errors, errors, requested_at, started_at, completed_at, links].hash
+          [completed_at, num_errors, requested_at, started_at, links, results, errors, status].hash
         end
 
         # Builds the object from hash