ynab 5.2.0 → 5.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 8f8eb3003dda34ba7c9269b35452dd0d0bec02ddee8bef688f8e52e2503943b2
-  data.tar.gz: '0197df1eeddea055b045788c268801986ea6887c31d657e8c85c852dd5ccdf90'
+  metadata.gz: 9c519478ec4054d5871fc144b246fc1c7307de1c61d2b2220c0dce9a9ff0879e
+  data.tar.gz: 959cf4ba89fdbccc05488eef03f0f16c6892bce297a65addb26955940c212404
 SHA512:
-  metadata.gz: ed5479594b0ddd569194cfe466a8dd8c66d28dfee79a949a5e2706f1ebb38aefb9801bc2629cc36ac6129105a05733592c624759e49e80dc4b60cc9331d497ee
-  data.tar.gz: 020c79b873bff0825173718cebab3025fcb22f06e19e0456cc3444c80e7944a0e77a96b659146411980f7fd3a4c4cb1e96ffc81ad1e955d66ee6abca5f77aaa2
+  metadata.gz: 18f35e85a46e13c5ecc8e3d852523faa17a29f1629a8c3bee087fb2876bfbe504bde3325e68fedd2131291e0d0688f32e7d77a24bad503a33f0828628e12ed33
+  data.tar.gz: 55295030f22d58f95383d178b268416d8ee5232900279c835d3c7fae38a602bba6a5f9e1de74ee21681cffcb0e30feae261d5e85c4fcba2a8c15602d46b88008

data/DEVELOPMENT.md

@@ -8,10 +8,13 @@
 
 ## Generating
 
-Run `bundle exec rake generate`.  This will generate the API client from the latest OpenAPI spec.  Once generated, you should open a PR and merge the changes.
+Run `bundle exec rake generate`.  This will generate the API client from the latest OpenAPI spec and bump the version.  The bump defaults to `minor`; pass `major` or `patch` to change it (`bundle exec rake "generate[patch]"`).  Once generated, you should open a PR and merge the changes.
 
 ## Publishing
 
-Run the "Publish" GitHub Actions workflow
+The version that gets published is whatever `lib/ynab/version.rb` on the `main` branch says, so publishing is two steps.
 
-Note: Use the Publish workflow to bump the version number in `lib/ynab/version.rb`
+1. Merge a PR that sets the new version.  `bundle exec rake generate` does this for you.  For a release that does not involve re-generating the client, run `bundle exec rake "bump_version_number[minor]"` (or `major` / `patch`), which updates `lib/ynab/version.rb` and `Gemfile.lock` without creating a commit or tag.
+2. Run the "Publish" GitHub Actions workflow.  This runs the specs and publishes that version to RubyGems, then tags the commit and creates a GitHub release.
+
+The workflow never changes the version itself.  If the version in `lib/ynab/version.rb` has already been released, the workflow fails before publishing anything.

data/Gemfile.lock

@@ -1,34 +1,36 @@
 PATH
   remote: .
   specs:
-    ynab (5.1.0)
+    ynab (5.3.0)
       typhoeus (~> 1.0, >= 1.0.1)
 
 GEM
   remote: https://rubygems.org/
   specs:
     base64 (0.3.0)
-    diff-lcs (1.3)
-    ethon (0.16.0)
+    diff-lcs (1.6.2)
+    ethon (0.18.0)
       ffi (>= 1.15.0)
-    ffi (1.17.3)
-    rake (13.0.1)
-    rspec (3.8.0)
-      rspec-core (~> 3.8.0)
-      rspec-expectations (~> 3.8.0)
-      rspec-mocks (~> 3.8.0)
-    rspec-core (3.8.0)
-      rspec-support (~> 3.8.0)
-    rspec-expectations (3.8.2)
+      logger
+    ffi (1.17.4)
+    logger (1.7.0)
+    rake (13.4.2)
+    rspec (3.13.2)
+      rspec-core (~> 3.13.0)
+      rspec-expectations (~> 3.13.0)
+      rspec-mocks (~> 3.13.0)
+    rspec-core (3.13.6)
+      rspec-support (~> 3.13.0)
+    rspec-expectations (3.13.5)
       diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.8.0)
-    rspec-mocks (3.8.0)
+      rspec-support (~> 3.13.0)
+    rspec-mocks (3.13.8)
       diff-lcs (>= 1.2.0, < 2.0)
-      rspec-support (~> 3.8.0)
-    rspec-support (3.8.0)
-    typhoeus (1.4.0)
-      ethon (>= 0.9.0)
-    vcr (6.2.0)
+      rspec-support (~> 3.13.0)
+    rspec-support (3.13.7)
+    typhoeus (1.6.0)
+      ethon (>= 0.18.0)
+    vcr (6.4.0)
 
 PLATFORMS
   ruby

data/Rakefile

@@ -12,8 +12,8 @@ end
 
 task :default => [:spec]
 
-desc "Run OpenAPI Generator to update the client from the spec"
-task :generate do
+desc "Run OpenAPI Generator to update the client from the spec and bump the version"
+task :generate, [:version_type] do |t, args|
   spec_filename = 'open_api_spec.yaml'
   # Download latest spec
   sh "wget https://api.ynab.com/papi/#{spec_filename} -O ./#{spec_filename}"
@@ -21,6 +21,8 @@ task :generate do
   sh "rm -r docs/ lib/ynab/models/"
   # Generate the client
   sh "openapi-generator generate -i ./#{spec_filename} -g ruby -c openapi-generator-config.yaml -o ./"
+
+  Rake::Task[:bump_version_number].invoke(args[:version_type] || 'minor')
 end
 
 task :get_current_version do
@@ -49,13 +51,12 @@ task :bump_version_number, [:version_type] do |t, args|
   new_version_file_text = current_version_file_text.gsub(current_version, new_version)
   File.open(version_file_path, "w") {|file| file.puts new_version_file_text }
 
-  puts new_version
-end
+  # Gemfile.lock pins this gem's own version, so it has to be re-resolved
+  sh "bundle lock"
 
-task :commit_version_bump do
-  sh "git add lib/ynab/version.rb Gemfile.lock && git diff-index --quiet HEAD || git commit -m 'Bumping version for release'"
+  puts new_version
 end
 
-desc "Bump version, run specs build a gem and release on RubyGems"
-task :publish => ['spec', 'commit_version_bump', 'clobber', 'release']
+desc "Run specs, build a gem and release it on RubyGems"
+task :publish => ['spec', 'clobber', 'release:rubygem_push']
 

data/docs/ExistingCategory.md

@@ -7,7 +7,8 @@
 | **name** | **String** |  | [optional] |
 | **note** | **String** |  | [optional] |
 | **category_group_id** | **String** | The id of the category group to which this category belongs.  An internal category group may not be specified. | [optional] |
-| **goal_target** | **Integer** | The goal target amount in milliunits format.  If value is specified and goal has not already been configured for category, a monthly goal will be created for the category with this target amount.  If goal_type is not specified, it will default to 'NEED' or 'MF' for Credit Card Payment categories. | [optional] |
-| **goal_target_date** | **Date** | The goal target date in ISO format (e.g. 2016-12-01). | [optional] |
-| **goal_needs_whole_amount** | **Boolean** | Whether the goal requires the full target amount each period. Only supported for 'NEED' goals. When true, the goal is configured as 'Set aside another...'. When false, the goal is configured as 'Refill up to...'. | [optional] |
+| **goal_target** | **Integer** | The goal target amount in milliunits format.  If value is specified and goal has not already been configured for category, a monthly goal will be created for the category with this target amount.  If goal_type is not specified, it will default to 'NEED', or to 'MF' for Credit Card Payment categories and 'DEBT' for categories paired to a loan account. When updating a category, passing null removes any existing target. | [optional] |
+| **goal_target_date** | **Date** | The goal target date in ISO format (e.g. 2016-12-01). Not supported for categories paired to a loan account. | [optional] |
+| **goal_needs_whole_amount** | **Boolean** | Whether the goal requires the full target amount each period. Only supported for 'NEED' goals, and not supported for Credit Card Payment categories or categories paired to a loan account. When true, the goal is configured as 'Set aside another...'. When false, the goal is configured as 'Refill up to...'. | [optional] |
+| **goal_frequency** | **String** | When specified, configures a recurring 'NEED' target of goal_target that repeats at this frequency, replacing any existing target. Requires goal_target. Cannot be combined with goal_target_date and is not supported for Credit Card Payment categories or categories paired to a loan account. Omit to leave an existing target's cadence unchanged. | [optional] |
 

data/docs/ExistingTransaction.md

@@ -14,5 +14,5 @@
 | **cleared** | [**TransactionClearedStatus**](TransactionClearedStatus.md) |  | [optional] |
 | **approved** | **Boolean** | Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default. | [optional] |
 | **flag_color** | [**TransactionFlagColor**](TransactionFlagColor.md) |  | [optional] |
-| **subtransactions** | [**Array<SaveSubTransaction>**](SaveSubTransaction.md) | An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported. | [optional] |
+| **subtransactions** | [**Array<SaveSubTransaction>**](SaveSubTransaction.md) | An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported and will return an error.  Splits are not allowed on tracking accounts or on transfers between on-budget accounts; a transfer to a tracking account can be a split. | [optional] |
 

data/docs/NewCategory.md

@@ -7,7 +7,8 @@
 | **name** | **String** |  | [optional] |
 | **note** | **String** |  | [optional] |
 | **category_group_id** | **String** | The id of the category group to which this category belongs.  An internal category group may not be specified. | [optional] |
-| **goal_target** | **Integer** | The goal target amount in milliunits format.  If value is specified and goal has not already been configured for category, a monthly goal will be created for the category with this target amount.  If goal_type is not specified, it will default to 'NEED' or 'MF' for Credit Card Payment categories. | [optional] |
-| **goal_target_date** | **Date** | The goal target date in ISO format (e.g. 2016-12-01). | [optional] |
-| **goal_needs_whole_amount** | **Boolean** | Whether the goal requires the full target amount each period. Only supported for 'NEED' goals. When true, the goal is configured as 'Set aside another...'. When false, the goal is configured as 'Refill up to...'. | [optional] |
+| **goal_target** | **Integer** | The goal target amount in milliunits format.  If value is specified and goal has not already been configured for category, a monthly goal will be created for the category with this target amount.  If goal_type is not specified, it will default to 'NEED', or to 'MF' for Credit Card Payment categories and 'DEBT' for categories paired to a loan account. When updating a category, passing null removes any existing target. | [optional] |
+| **goal_target_date** | **Date** | The goal target date in ISO format (e.g. 2016-12-01). Not supported for categories paired to a loan account. | [optional] |
+| **goal_needs_whole_amount** | **Boolean** | Whether the goal requires the full target amount each period. Only supported for 'NEED' goals, and not supported for Credit Card Payment categories or categories paired to a loan account. When true, the goal is configured as 'Set aside another...'. When false, the goal is configured as 'Refill up to...'. | [optional] |
+| **goal_frequency** | **String** | When specified, configures a recurring 'NEED' target of goal_target that repeats at this frequency, replacing any existing target. Requires goal_target. Cannot be combined with goal_target_date and is not supported for Credit Card Payment categories or categories paired to a loan account. Omit to leave an existing target's cadence unchanged. | [optional] |
 

data/docs/NewTransaction.md

@@ -14,6 +14,6 @@
 | **cleared** | [**TransactionClearedStatus**](TransactionClearedStatus.md) |  | [optional] |
 | **approved** | **Boolean** | Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default. | [optional] |
 | **flag_color** | [**TransactionFlagColor**](TransactionFlagColor.md) |  | [optional] |
-| **subtransactions** | [**Array<SaveSubTransaction>**](SaveSubTransaction.md) | An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported. | [optional] |
+| **subtransactions** | [**Array<SaveSubTransaction>**](SaveSubTransaction.md) | An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported and will return an error.  Splits are not allowed on tracking accounts or on transfers between on-budget accounts; a transfer to a tracking account can be a split. | [optional] |
 | **import_id** | **String** | If specified, a new transaction will be assigned this `import_id` and considered \"imported\".  We will also attempt to match this imported transaction to an existing \"user-entered\" transaction on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'.  If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'.  Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API). | [optional] |
 

data/docs/SaveCategory.md

@@ -7,7 +7,8 @@
 | **name** | **String** |  | [optional] |
 | **note** | **String** |  | [optional] |
 | **category_group_id** | **String** | The id of the category group to which this category belongs.  An internal category group may not be specified. | [optional] |
-| **goal_target** | **Integer** | The goal target amount in milliunits format.  If value is specified and goal has not already been configured for category, a monthly goal will be created for the category with this target amount.  If goal_type is not specified, it will default to 'NEED' or 'MF' for Credit Card Payment categories. | [optional] |
-| **goal_target_date** | **Date** | The goal target date in ISO format (e.g. 2016-12-01). | [optional] |
-| **goal_needs_whole_amount** | **Boolean** | Whether the goal requires the full target amount each period. Only supported for 'NEED' goals. When true, the goal is configured as 'Set aside another...'. When false, the goal is configured as 'Refill up to...'. | [optional] |
+| **goal_target** | **Integer** | The goal target amount in milliunits format.  If value is specified and goal has not already been configured for category, a monthly goal will be created for the category with this target amount.  If goal_type is not specified, it will default to 'NEED', or to 'MF' for Credit Card Payment categories and 'DEBT' for categories paired to a loan account. When updating a category, passing null removes any existing target. | [optional] |
+| **goal_target_date** | **Date** | The goal target date in ISO format (e.g. 2016-12-01). Not supported for categories paired to a loan account. | [optional] |
+| **goal_needs_whole_amount** | **Boolean** | Whether the goal requires the full target amount each period. Only supported for 'NEED' goals, and not supported for Credit Card Payment categories or categories paired to a loan account. When true, the goal is configured as 'Set aside another...'. When false, the goal is configured as 'Refill up to...'. | [optional] |
+| **goal_frequency** | **String** | When specified, configures a recurring 'NEED' target of goal_target that repeats at this frequency, replacing any existing target. Requires goal_target. Cannot be combined with goal_target_date and is not supported for Credit Card Payment categories or categories paired to a loan account. Omit to leave an existing target's cadence unchanged. | [optional] |
 

data/docs/SaveTransactionWithIdOrImportId.md

@@ -14,7 +14,7 @@
 | **cleared** | [**TransactionClearedStatus**](TransactionClearedStatus.md) |  | [optional] |
 | **approved** | **Boolean** | Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default. | [optional] |
 | **flag_color** | [**TransactionFlagColor**](TransactionFlagColor.md) |  | [optional] |
-| **subtransactions** | [**Array<SaveSubTransaction>**](SaveSubTransaction.md) | An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported. | [optional] |
+| **subtransactions** | [**Array<SaveSubTransaction>**](SaveSubTransaction.md) | An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported and will return an error.  Splits are not allowed on tracking accounts or on transfers between on-budget accounts; a transfer to a tracking account can be a split. | [optional] |
 | **id** | **String** | If specified, this id will be used to lookup a transaction by its `id` for the purpose of updating the transaction itself. If not specified, an `import_id` should be supplied. | [optional] |
 | **import_id** | **String** | If specified, this id will be used to lookup a transaction by its `import_id` for the purpose of updating the transaction itself. If not specified, an `id` should be supplied.  You may not provide both an `id` and an `import_id` and updating an `import_id` on an existing transaction is not allowed. | [optional] |
 

data/docs/SaveTransactionWithOptionalFields.md

@@ -14,5 +14,5 @@
 | **cleared** | [**TransactionClearedStatus**](TransactionClearedStatus.md) |  | [optional] |
 | **approved** | **Boolean** | Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default. | [optional] |
 | **flag_color** | [**TransactionFlagColor**](TransactionFlagColor.md) |  | [optional] |
-| **subtransactions** | [**Array<SaveSubTransaction>**](SaveSubTransaction.md) | An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported. | [optional] |
+| **subtransactions** | [**Array<SaveSubTransaction>**](SaveSubTransaction.md) | An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported and will return an error.  Splits are not allowed on tracking accounts or on transfers between on-budget accounts; a transfer to a tracking account can be a split. | [optional] |
 

data/docs/TransactionsApi.md

@@ -202,7 +202,7 @@ Returns all transactions for a specified payee, excluding any pending transactio
 
 Import transactions
 
-Imports available transactions on all linked accounts for the given plan.  Linked accounts allow transactions to be imported directly from a specified financial institution and this endpoint initiates that import.  Sending a request to this endpoint is the equivalent of clicking \"Import\" on each account in the web application or tapping the \"New Transactions\" banner in the mobile applications.  The response for this endpoint contains the transaction ids that have been imported.
+DEPRECATED: This endpoint is no longer needed because YNAB now automatically imports transactions on linked accounts.  Requests are still accepted for backwards compatibility but no import is performed and the response will always contain an empty list of transaction ids.
 
 ### Parameters
 

data/lib/ynab/api/accounts_api.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 =end

data/lib/ynab/api/categories_api.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 =end

data/lib/ynab/api/money_movements_api.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 =end

data/lib/ynab/api/months_api.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 =end

data/lib/ynab/api/payee_locations_api.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 =end

data/lib/ynab/api/payees_api.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 =end

data/lib/ynab/api/plans_api.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 =end

data/lib/ynab/api/scheduled_transactions_api.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 =end

data/lib/ynab/api/transactions_api.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 =end
@@ -627,7 +627,7 @@ module YNAB
     end
 
     # Import transactions
-    # Imports available transactions on all linked accounts for the given plan.  Linked accounts allow transactions to be imported directly from a specified financial institution and this endpoint initiates that import.  Sending a request to this endpoint is the equivalent of clicking \"Import\" on each account in the web application or tapping the \"New Transactions\" banner in the mobile applications.  The response for this endpoint contains the transaction ids that have been imported.
+    # DEPRECATED: This endpoint is no longer needed because YNAB now automatically imports transactions on linked accounts.  Requests are still accepted for backwards compatibility but no import is performed and the response will always contain an empty list of transaction ids.
     # @param plan_id [String] The id of the plan. \"last-used\" can be used to specify the last used plan and \"default\" can be used if default plan selection is enabled (see: https://api.ynab.com/#oauth-default-plan).
     # @param [Hash] opts the optional parameters
     # @return [TransactionsImportResponse]
@@ -637,7 +637,7 @@ module YNAB
     end
 
     # Import transactions
-    # Imports available transactions on all linked accounts for the given plan.  Linked accounts allow transactions to be imported directly from a specified financial institution and this endpoint initiates that import.  Sending a request to this endpoint is the equivalent of clicking \"Import\" on each account in the web application or tapping the \"New Transactions\" banner in the mobile applications.  The response for this endpoint contains the transaction ids that have been imported.
+    # DEPRECATED: This endpoint is no longer needed because YNAB now automatically imports transactions on linked accounts.  Requests are still accepted for backwards compatibility but no import is performed and the response will always contain an empty list of transaction ids.
     # @param plan_id [String] The id of the plan. \"last-used\" can be used to specify the last used plan and \"default\" can be used if default plan selection is enabled (see: https://api.ynab.com/#oauth-default-plan).
     # @param [Hash] opts the optional parameters
     # @return [Array<(TransactionsImportResponse, Integer, Hash)>] TransactionsImportResponse data, response status code and response headers

data/lib/ynab/api/user_api.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 =end

data/lib/ynab/api_client.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 =end

data/lib/ynab/api_model_base.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 

data/lib/ynab/configuration.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 

data/lib/ynab/models/account.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 
@@ -129,9 +129,14 @@ module YNAB
       }
     end
 
+    # Returns attribute mapping this model knows about
+    def self.acceptable_attribute_map
+      attribute_map
+    end
+
     # Returns all the JSON keys this model knows about
     def self.acceptable_attributes
-      attribute_map.values
+      acceptable_attribute_map.values
     end
 
     # Attribute type mapping.
@@ -167,9 +172,26 @@ module YNAB
     # List of attributes with nullable: true
     def self.openapi_nullable
       Set.new([
+        :'note',
+        :'transfer_payee_id',
+        :'last_reconciled_at',
+        :'debt_original_balance',
+        :'debt_interest_rates',
+        :'debt_minimum_payments',
+        :'debt_escrow_amounts',
       ])
     end
 
+    # Returns attribute type mapping
+    def self.acceptable_openapi_types
+      openapi_types
+    end
+
+    # Returns the nullable attributes
+    def self.acceptable_openapi_nullable
+      openapi_nullable
+    end
+
     # List of class defined in allOf (OpenAPI v3)
     def self.openapi_all_of
       [
@@ -185,9 +207,10 @@ module YNAB
       end
 
       # check to see if the attribute exists and convert string to symbol for hash key
+      acceptable_attribute_map = self.class.acceptable_attribute_map
       attributes = attributes.each_with_object({}) { |(k, v), h|
-        if (!self.class.attribute_map.key?(k.to_sym))
-          fail ArgumentError, "`#{k}` is not a valid attribute in `YNAB::Account`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
+        if (!acceptable_attribute_map.key?(k.to_sym))
+          fail ArgumentError, "`#{k}` is not a valid attribute in `YNAB::Account`. Please check the name to make sure it's valid. List of attributes: " + acceptable_attribute_map.keys.inspect
         end
         h[k.to_sym] = v
       }
@@ -313,7 +336,6 @@ module YNAB
       return false if @balance.nil?
       return false if @cleared_balance.nil?
       return false if @uncleared_balance.nil?
-      return false if @transfer_payee_id.nil?
       return false if @deleted.nil?
       true
     end
@@ -367,18 +389,20 @@ module YNAB
     def self.build_from_hash(attributes)
       return nil unless attributes.is_a?(Hash)
       attributes = attributes.transform_keys(&:to_sym)
+      # include attributes inherited from allOf parents (the nearest declaration wins)
+      map = acceptable_attribute_map
       transformed_hash = {}
-      openapi_types.each_pair do |key, type|
-        if attributes.key?(attribute_map[key]) && attributes[attribute_map[key]].nil?
+      acceptable_openapi_types.each_pair do |key, type|
+        if attributes.key?(map[key]) && attributes[map[key]].nil?
           transformed_hash["#{key}"] = nil
         elsif type =~ /\AArray<(.*)>/i
           # check to ensure the input is an array given that the attribute
           # is documented as an array but the input is not
-          if attributes[attribute_map[key]].is_a?(Array)
-            transformed_hash["#{key}"] = attributes[attribute_map[key]].map { |v| _deserialize($1, v) }
+          if attributes[map[key]].is_a?(Array)
+            transformed_hash["#{key}"] = attributes[map[key]].map { |v| _deserialize($1, v) }
           end
-        elsif !attributes[attribute_map[key]].nil?
-          transformed_hash["#{key}"] = _deserialize(type, attributes[attribute_map[key]])
+        elsif !attributes[map[key]].nil?
+          transformed_hash["#{key}"] = _deserialize(type, attributes[map[key]])
         end
       end
       new(transformed_hash)
@@ -388,10 +412,11 @@ module YNAB
     # @return [Hash] Returns the object in the form of hash
     def to_hash
       hash = {}
-      self.class.attribute_map.each_pair do |attr, param|
+      # include attributes inherited from allOf parents (the nearest declaration wins)
+      self.class.acceptable_attribute_map.each_pair do |attr, param|
         value = self.send(attr)
         if value.nil?
-          is_nullable = self.class.openapi_nullable.include?(attr)
+          is_nullable = self.class.acceptable_openapi_nullable.include?(attr)
           next if !is_nullable || (is_nullable && !instance_variable_defined?(:"@#{attr}"))
         end
 

data/lib/ynab/models/account_base.rb

@@ -1,7 +1,7 @@
 =begin
 #YNAB API Endpoints
 
-#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
+#Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  Read the [API Documentation](https://api.ynab.com) for more information about the API, including how to obtain an access token and how to use it to make requests.
 
 Generated by: OpenAPI Generator (https://openapi-generator.tech)
 
@@ -105,9 +105,14 @@ module YNAB
       }
     end
 
+    # Returns attribute mapping this model knows about
+    def self.acceptable_attribute_map
+      attribute_map
+    end
+
     # Returns all the JSON keys this model knows about
     def self.acceptable_attributes
-      attribute_map.values
+      acceptable_attribute_map.values
     end
 
     # Attribute type mapping.
@@ -141,9 +146,22 @@ module YNAB
         :'transfer_payee_id',
         :'last_reconciled_at',
         :'debt_original_balance',
+        :'debt_interest_rates',
+        :'debt_minimum_payments',
+        :'debt_escrow_amounts',
       ])
     end
 
+    # Returns attribute type mapping
+    def self.acceptable_openapi_types
+      openapi_types
+    end
+
+    # Returns the nullable attributes
+    def self.acceptable_openapi_nullable
+      openapi_nullable
+    end
+
     # Initializes the object
     # @param [Hash] attributes Model attributes in the form of hash
     def initialize(attributes = {})
@@ -152,9 +170,10 @@ module YNAB
       end
 
       # check to see if the attribute exists and convert string to symbol for hash key
+      acceptable_attribute_map = self.class.acceptable_attribute_map
       attributes = attributes.each_with_object({}) { |(k, v), h|
-        if (!self.class.attribute_map.key?(k.to_sym))
-          fail ArgumentError, "`#{k}` is not a valid attribute in `YNAB::AccountBase`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
+        if (!acceptable_attribute_map.key?(k.to_sym))
+          fail ArgumentError, "`#{k}` is not a valid attribute in `YNAB::AccountBase`. Please check the name to make sure it's valid. List of attributes: " + acceptable_attribute_map.keys.inspect
         end
         h[k.to_sym] = v
       }
@@ -303,18 +322,20 @@ module YNAB
     def self.build_from_hash(attributes)
       return nil unless attributes.is_a?(Hash)
       attributes = attributes.transform_keys(&:to_sym)
+      # include attributes inherited from allOf parents (the nearest declaration wins)
+      map = acceptable_attribute_map
       transformed_hash = {}
-      openapi_types.each_pair do |key, type|
-        if attributes.key?(attribute_map[key]) && attributes[attribute_map[key]].nil?
+      acceptable_openapi_types.each_pair do |key, type|
+        if attributes.key?(map[key]) && attributes[map[key]].nil?
           transformed_hash["#{key}"] = nil
         elsif type =~ /\AArray<(.*)>/i
           # check to ensure the input is an array given that the attribute
           # is documented as an array but the input is not
-          if attributes[attribute_map[key]].is_a?(Array)
-            transformed_hash["#{key}"] = attributes[attribute_map[key]].map { |v| _deserialize($1, v) }
+          if attributes[map[key]].is_a?(Array)
+            transformed_hash["#{key}"] = attributes[map[key]].map { |v| _deserialize($1, v) }
           end
-        elsif !attributes[attribute_map[key]].nil?
-          transformed_hash["#{key}"] = _deserialize(type, attributes[attribute_map[key]])
+        elsif !attributes[map[key]].nil?
+          transformed_hash["#{key}"] = _deserialize(type, attributes[map[key]])
         end
       end
       new(transformed_hash)
@@ -324,10 +345,11 @@ module YNAB
     # @return [Hash] Returns the object in the form of hash
     def to_hash
       hash = {}
-      self.class.attribute_map.each_pair do |attr, param|
+      # include attributes inherited from allOf parents (the nearest declaration wins)
+      self.class.acceptable_attribute_map.each_pair do |attr, param|
         value = self.send(attr)
         if value.nil?
-          is_nullable = self.class.openapi_nullable.include?(attr)
+          is_nullable = self.class.acceptable_openapi_nullable.include?(attr)
           next if !is_nullable || (is_nullable && !instance_variable_defined?(:"@#{attr}"))
         end