ynab 1.28.0 → 1.31.0
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +3 -3
- data/lib/ynab/api/accounts_api.rb +7 -7
- data/lib/ynab/api/budgets_api.rb +5 -5
- data/lib/ynab/api/categories_api.rb +9 -9
- data/lib/ynab/api/deprecated_api.rb +3 -3
- data/lib/ynab/api/months_api.rb +5 -5
- data/lib/ynab/api/payee_locations_api.rb +7 -7
- data/lib/ynab/api/payees_api.rb +5 -5
- data/lib/ynab/api/scheduled_transactions_api.rb +5 -5
- data/lib/ynab/api/transactions_api.rb +21 -21
- data/lib/ynab/api/user_api.rb +1 -1
- data/lib/ynab/api_client.rb +1 -1
- data/lib/ynab/configuration.rb +2 -2
- data/lib/ynab/models/account.rb +1 -1
- data/lib/ynab/models/account_response.rb +1 -1
- data/lib/ynab/models/account_response_data.rb +1 -1
- data/lib/ynab/models/account_type.rb +1 -1
- data/lib/ynab/models/accounts_response.rb +1 -1
- data/lib/ynab/models/accounts_response_data.rb +1 -1
- data/lib/ynab/models/budget_detail.rb +1 -1
- data/lib/ynab/models/budget_detail_response.rb +1 -1
- data/lib/ynab/models/budget_detail_response_data.rb +1 -1
- data/lib/ynab/models/budget_settings.rb +1 -1
- data/lib/ynab/models/budget_settings_response.rb +1 -1
- data/lib/ynab/models/budget_settings_response_data.rb +1 -1
- data/lib/ynab/models/budget_summary.rb +1 -1
- data/lib/ynab/models/budget_summary_response.rb +1 -1
- data/lib/ynab/models/budget_summary_response_data.rb +1 -1
- data/lib/ynab/models/bulk_response.rb +1 -1
- data/lib/ynab/models/bulk_response_data.rb +1 -1
- data/lib/ynab/models/bulk_response_data_bulk.rb +1 -1
- data/lib/ynab/models/bulk_transactions.rb +1 -1
- data/lib/ynab/models/categories_response.rb +1 -1
- data/lib/ynab/models/categories_response_data.rb +1 -1
- data/lib/ynab/models/category.rb +1 -1
- data/lib/ynab/models/category_group.rb +1 -1
- data/lib/ynab/models/category_group_with_categories.rb +1 -1
- data/lib/ynab/models/category_response.rb +1 -1
- data/lib/ynab/models/category_response_data.rb +1 -1
- data/lib/ynab/models/currency_format.rb +1 -1
- data/lib/ynab/models/date_format.rb +1 -1
- data/lib/ynab/models/error_detail.rb +1 -1
- data/lib/ynab/models/error_response.rb +1 -1
- data/lib/ynab/models/hybrid_transaction.rb +2 -31
- data/lib/ynab/models/hybrid_transactions_response.rb +1 -1
- data/lib/ynab/models/hybrid_transactions_response_data.rb +1 -1
- data/lib/ynab/models/loan_account_periodic_value.rb +1 -1
- data/lib/ynab/models/month_detail.rb +1 -1
- data/lib/ynab/models/month_detail_response.rb +1 -1
- data/lib/ynab/models/month_detail_response_data.rb +1 -1
- data/lib/ynab/models/month_summaries_response.rb +1 -1
- data/lib/ynab/models/month_summaries_response_data.rb +1 -1
- data/lib/ynab/models/month_summary.rb +1 -1
- data/lib/ynab/models/patch_month_category_wrapper.rb +1 -1
- data/lib/ynab/models/patch_transactions_wrapper.rb +1 -1
- data/lib/ynab/models/payee.rb +1 -1
- data/lib/ynab/models/payee_location.rb +1 -1
- data/lib/ynab/models/payee_location_response.rb +1 -1
- data/lib/ynab/models/payee_location_response_data.rb +1 -1
- data/lib/ynab/models/payee_locations_response.rb +1 -1
- data/lib/ynab/models/payee_locations_response_data.rb +1 -1
- data/lib/ynab/models/payee_response.rb +1 -1
- data/lib/ynab/models/payee_response_data.rb +1 -1
- data/lib/ynab/models/payees_response.rb +1 -1
- data/lib/ynab/models/payees_response_data.rb +1 -1
- data/lib/ynab/models/post_account_wrapper.rb +1 -1
- data/lib/ynab/models/post_transactions_wrapper.rb +1 -1
- data/lib/ynab/models/put_transaction_wrapper.rb +1 -1
- data/lib/ynab/models/save_account.rb +1 -1
- data/lib/ynab/models/save_category_response.rb +1 -1
- data/lib/ynab/models/save_category_response_data.rb +1 -1
- data/lib/ynab/models/save_month_category.rb +1 -1
- data/lib/ynab/models/save_sub_transaction.rb +1 -1
- data/lib/ynab/models/save_transaction.rb +1 -1
- data/lib/ynab/models/save_transaction_with_id.rb +1 -1
- data/lib/ynab/models/save_transaction_with_optional_fields.rb +1 -1
- data/lib/ynab/models/save_transactions_response.rb +1 -1
- data/lib/ynab/models/save_transactions_response_data.rb +1 -1
- data/lib/ynab/models/scheduled_sub_transaction.rb +1 -1
- data/lib/ynab/models/scheduled_transaction_detail.rb +2 -1
- data/lib/ynab/models/scheduled_transaction_response.rb +1 -1
- data/lib/ynab/models/scheduled_transaction_response_data.rb +1 -1
- data/lib/ynab/models/scheduled_transaction_summary.rb +1 -1
- data/lib/ynab/models/scheduled_transactions_response.rb +1 -1
- data/lib/ynab/models/scheduled_transactions_response_data.rb +1 -1
- data/lib/ynab/models/sub_transaction.rb +1 -1
- data/lib/ynab/models/transaction_detail.rb +2 -31
- data/lib/ynab/models/transaction_response.rb +1 -1
- data/lib/ynab/models/transaction_response_data.rb +1 -1
- data/lib/ynab/models/transaction_summary.rb +1 -31
- data/lib/ynab/models/transactions_import_response.rb +1 -1
- data/lib/ynab/models/transactions_import_response_data.rb +1 -1
- data/lib/ynab/models/transactions_response.rb +1 -1
- data/lib/ynab/models/transactions_response_data.rb +1 -1
- data/lib/ynab/models/user.rb +1 -1
- data/lib/ynab/models/user_response.rb +1 -1
- data/lib/ynab/models/user_response_data.rb +1 -1
- data/lib/ynab/version.rb +1 -1
- data/lib/ynab.rb +2 -2
- metadata +37 -37
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
data/lib/ynab/models/payee.rb
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -48,6 +48,7 @@ module YNAB
|
|
|
48
48
|
|
|
49
49
|
attr_accessor :payee_name
|
|
50
50
|
|
|
51
|
+
# The name of the category. If a split scheduled transaction, this will be 'Split'.
|
|
51
52
|
attr_accessor :category_name
|
|
52
53
|
|
|
53
54
|
# If a split scheduled transaction, the subtransactions.
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -67,6 +67,7 @@ module YNAB
|
|
|
67
67
|
|
|
68
68
|
attr_accessor :payee_name
|
|
69
69
|
|
|
70
|
+
# The name of the category. If a split transaction, this will be 'Split'.
|
|
70
71
|
attr_accessor :category_name
|
|
71
72
|
|
|
72
73
|
# If a split transaction, the subtransactions.
|
|
@@ -277,14 +278,6 @@ module YNAB
|
|
|
277
278
|
invalid_properties.push('invalid value for "account_id", account_id cannot be nil.')
|
|
278
279
|
end
|
|
279
280
|
|
|
280
|
-
if !@import_payee_name.nil? && @import_payee_name.to_s.length > 200
|
|
281
|
-
invalid_properties.push('invalid value for "import_payee_name", the character length must be smaller than or equal to 200.')
|
|
282
|
-
end
|
|
283
|
-
|
|
284
|
-
if !@import_payee_name_original.nil? && @import_payee_name_original.to_s.length > 200
|
|
285
|
-
invalid_properties.push('invalid value for "import_payee_name_original", the character length must be smaller than or equal to 200.')
|
|
286
|
-
end
|
|
287
|
-
|
|
288
281
|
if @deleted.nil?
|
|
289
282
|
invalid_properties.push('invalid value for "deleted", deleted cannot be nil.')
|
|
290
283
|
end
|
|
@@ -313,8 +306,6 @@ module YNAB
|
|
|
313
306
|
flag_color_validator = EnumAttributeValidator.new('String', ['red', 'orange', 'yellow', 'green', 'blue', 'purple'])
|
|
314
307
|
return false unless flag_color_validator.valid?(@flag_color)
|
|
315
308
|
return false if @account_id.nil?
|
|
316
|
-
return false if !@import_payee_name.nil? && @import_payee_name.to_s.length > 200
|
|
317
|
-
return false if !@import_payee_name_original.nil? && @import_payee_name_original.to_s.length > 200
|
|
318
309
|
debt_transaction_type_validator = EnumAttributeValidator.new('String', ['payment', 'refund', 'fee', 'interest', 'escrow', 'balancedAdjustment', 'credit', 'charge'])
|
|
319
310
|
return false unless debt_transaction_type_validator.valid?(@debt_transaction_type)
|
|
320
311
|
return false if @deleted.nil?
|
|
@@ -335,26 +326,6 @@ module YNAB
|
|
|
335
326
|
@flag_color = flag_color
|
|
336
327
|
end
|
|
337
328
|
|
|
338
|
-
# Custom attribute writer method with validation
|
|
339
|
-
# @param [Object] import_payee_name Value to be assigned
|
|
340
|
-
def import_payee_name=(import_payee_name)
|
|
341
|
-
if !import_payee_name.nil? && import_payee_name.to_s.length > 200
|
|
342
|
-
fail ArgumentError, 'invalid value for "import_payee_name", the character length must be smaller than or equal to 200.'
|
|
343
|
-
end
|
|
344
|
-
|
|
345
|
-
@import_payee_name = import_payee_name
|
|
346
|
-
end
|
|
347
|
-
|
|
348
|
-
# Custom attribute writer method with validation
|
|
349
|
-
# @param [Object] import_payee_name_original Value to be assigned
|
|
350
|
-
def import_payee_name_original=(import_payee_name_original)
|
|
351
|
-
if !import_payee_name_original.nil? && import_payee_name_original.to_s.length > 200
|
|
352
|
-
fail ArgumentError, 'invalid value for "import_payee_name_original", the character length must be smaller than or equal to 200.'
|
|
353
|
-
end
|
|
354
|
-
|
|
355
|
-
@import_payee_name_original = import_payee_name_original
|
|
356
|
-
end
|
|
357
|
-
|
|
358
329
|
# Custom attribute writer method checking allowed values (enum).
|
|
359
330
|
# @param [Object] debt_transaction_type Object to be assigned
|
|
360
331
|
def debt_transaction_type=(debt_transaction_type)
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -242,14 +242,6 @@ module YNAB
|
|
|
242
242
|
invalid_properties.push('invalid value for "account_id", account_id cannot be nil.')
|
|
243
243
|
end
|
|
244
244
|
|
|
245
|
-
if !@import_payee_name.nil? && @import_payee_name.to_s.length > 200
|
|
246
|
-
invalid_properties.push('invalid value for "import_payee_name", the character length must be smaller than or equal to 200.')
|
|
247
|
-
end
|
|
248
|
-
|
|
249
|
-
if !@import_payee_name_original.nil? && @import_payee_name_original.to_s.length > 200
|
|
250
|
-
invalid_properties.push('invalid value for "import_payee_name_original", the character length must be smaller than or equal to 200.')
|
|
251
|
-
end
|
|
252
|
-
|
|
253
245
|
if @deleted.nil?
|
|
254
246
|
invalid_properties.push('invalid value for "deleted", deleted cannot be nil.')
|
|
255
247
|
end
|
|
@@ -270,8 +262,6 @@ module YNAB
|
|
|
270
262
|
flag_color_validator = EnumAttributeValidator.new('String', ['red', 'orange', 'yellow', 'green', 'blue', 'purple'])
|
|
271
263
|
return false unless flag_color_validator.valid?(@flag_color)
|
|
272
264
|
return false if @account_id.nil?
|
|
273
|
-
return false if !@import_payee_name.nil? && @import_payee_name.to_s.length > 200
|
|
274
|
-
return false if !@import_payee_name_original.nil? && @import_payee_name_original.to_s.length > 200
|
|
275
265
|
debt_transaction_type_validator = EnumAttributeValidator.new('String', ['payment', 'refund', 'fee', 'interest', 'escrow', 'balancedAdjustment', 'credit', 'charge'])
|
|
276
266
|
return false unless debt_transaction_type_validator.valid?(@debt_transaction_type)
|
|
277
267
|
return false if @deleted.nil?
|
|
@@ -290,26 +280,6 @@ module YNAB
|
|
|
290
280
|
@flag_color = flag_color
|
|
291
281
|
end
|
|
292
282
|
|
|
293
|
-
# Custom attribute writer method with validation
|
|
294
|
-
# @param [Object] import_payee_name Value to be assigned
|
|
295
|
-
def import_payee_name=(import_payee_name)
|
|
296
|
-
if !import_payee_name.nil? && import_payee_name.to_s.length > 200
|
|
297
|
-
fail ArgumentError, 'invalid value for "import_payee_name", the character length must be smaller than or equal to 200.'
|
|
298
|
-
end
|
|
299
|
-
|
|
300
|
-
@import_payee_name = import_payee_name
|
|
301
|
-
end
|
|
302
|
-
|
|
303
|
-
# Custom attribute writer method with validation
|
|
304
|
-
# @param [Object] import_payee_name_original Value to be assigned
|
|
305
|
-
def import_payee_name_original=(import_payee_name_original)
|
|
306
|
-
if !import_payee_name_original.nil? && import_payee_name_original.to_s.length > 200
|
|
307
|
-
fail ArgumentError, 'invalid value for "import_payee_name_original", the character length must be smaller than or equal to 200.'
|
|
308
|
-
end
|
|
309
|
-
|
|
310
|
-
@import_payee_name_original = import_payee_name_original
|
|
311
|
-
end
|
|
312
|
-
|
|
313
283
|
# Custom attribute writer method checking allowed values (enum).
|
|
314
284
|
# @param [Object] debt_transaction_type Object to be assigned
|
|
315
285
|
def debt_transaction_type=(debt_transaction_type)
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
=begin
|
|
2
2
|
#YNAB API Endpoints
|
|
3
3
|
|
|
4
|
-
#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.
|
|
4
|
+
#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
|
|
5
5
|
|
|
6
6
|
OpenAPI spec version: 1.0.0
|
|
7
7
|
|