From 4b3cb845b89a8c671f70cf2153240795ccb58cd7 Mon Sep 17 00:00:00 2001 From: Brady Holt Date: Wed, 15 Jul 2026 08:15:02 -0500 Subject: [PATCH 1/4] Regenerate SDK from server specification version 1.86.0 Regenerated the client from the YNAB API spec 1.86.0 (previously 1.85.0). --- .gitignore | 2 - docs/ExistingCategory.md | 3 +- docs/NewCategory.md | 3 +- docs/SaveCategory.md | 3 +- open_api_spec.yaml | 55 +++++++++++++++---- pyproject.toml | 2 +- ynab/__init__.py | 6 +- ynab/api/accounts_api.py | 4 +- ynab/api/categories_api.py | 4 +- ynab/api/money_movements_api.py | 4 +- ynab/api/months_api.py | 4 +- ynab/api/payee_locations_api.py | 4 +- ynab/api/payees_api.py | 4 +- ynab/api/plans_api.py | 4 +- ynab/api/scheduled_transactions_api.py | 4 +- ynab/api/transactions_api.py | 4 +- ynab/api/user_api.py | 4 +- ynab/api_client.py | 6 +- ynab/configuration.py | 8 +-- ynab/exceptions.py | 4 +- ynab/models/__init__.py | 4 +- ynab/models/account.py | 4 +- ynab/models/account_base.py | 4 +- ynab/models/account_response.py | 4 +- ynab/models/account_response_data.py | 4 +- ynab/models/account_type.py | 4 +- ynab/models/accounts_response.py | 4 +- ynab/models/accounts_response_data.py | 4 +- ynab/models/bulk_response.py | 4 +- ynab/models/bulk_response_data.py | 4 +- ynab/models/bulk_response_data_bulk.py | 4 +- ynab/models/bulk_transactions.py | 4 +- ynab/models/categories_response.py | 4 +- ynab/models/categories_response_data.py | 4 +- ynab/models/category.py | 4 +- ynab/models/category_base.py | 4 +- ynab/models/category_group.py | 4 +- ynab/models/category_group_with_categories.py | 4 +- ynab/models/category_response.py | 4 +- ynab/models/category_response_data.py | 4 +- ynab/models/currency_format.py | 4 +- ynab/models/date_format.py | 4 +- ynab/models/error_detail.py | 4 +- ynab/models/error_response.py | 4 +- ynab/models/existing_category.py | 24 ++++++-- ynab/models/existing_transaction.py | 4 +- ynab/models/hybrid_transaction.py | 4 +- ynab/models/hybrid_transactions_response.py | 4 +- .../hybrid_transactions_response_data.py | 4 +- ynab/models/money_movement.py | 4 +- ynab/models/money_movement_base.py | 4 +- ynab/models/money_movement_group.py | 4 +- ynab/models/money_movement_groups_response.py | 4 +- .../money_movement_groups_response_data.py | 4 +- ynab/models/money_movements_response.py | 4 +- ynab/models/money_movements_response_data.py | 4 +- ynab/models/month_detail.py | 4 +- ynab/models/month_detail_base.py | 4 +- ynab/models/month_detail_response.py | 4 +- ynab/models/month_detail_response_data.py | 4 +- ynab/models/month_summaries_response.py | 4 +- ynab/models/month_summaries_response_data.py | 4 +- ynab/models/month_summary.py | 4 +- ynab/models/month_summary_base.py | 4 +- ynab/models/new_category.py | 24 ++++++-- ynab/models/new_transaction.py | 4 +- ynab/models/patch_category_group_wrapper.py | 4 +- ynab/models/patch_category_wrapper.py | 4 +- ynab/models/patch_month_category_wrapper.py | 4 +- ynab/models/patch_payee_wrapper.py | 4 +- ynab/models/patch_transactions_wrapper.py | 4 +- ynab/models/payee.py | 4 +- ynab/models/payee_location.py | 4 +- ynab/models/payee_location_response.py | 4 +- ynab/models/payee_location_response_data.py | 4 +- ynab/models/payee_locations_response.py | 4 +- ynab/models/payee_locations_response_data.py | 4 +- ynab/models/payee_response.py | 4 +- ynab/models/payee_response_data.py | 4 +- ynab/models/payees_response.py | 4 +- ynab/models/payees_response_data.py | 4 +- ynab/models/plan_detail.py | 4 +- ynab/models/plan_detail_response.py | 4 +- ynab/models/plan_detail_response_data.py | 4 +- ynab/models/plan_settings.py | 4 +- ynab/models/plan_settings_response.py | 4 +- ynab/models/plan_settings_response_data.py | 4 +- ynab/models/plan_summary.py | 4 +- ynab/models/plan_summary_response.py | 4 +- ynab/models/plan_summary_response_data.py | 4 +- ynab/models/post_account_wrapper.py | 4 +- ynab/models/post_category_group_wrapper.py | 4 +- ynab/models/post_category_wrapper.py | 4 +- ynab/models/post_payee.py | 4 +- ynab/models/post_payee_wrapper.py | 4 +- .../post_scheduled_transaction_wrapper.py | 4 +- ynab/models/post_transactions_wrapper.py | 4 +- .../put_scheduled_transaction_wrapper.py | 4 +- ynab/models/put_transaction_wrapper.py | 4 +- ynab/models/save_account.py | 4 +- ynab/models/save_account_type.py | 4 +- ynab/models/save_category.py | 24 ++++++-- ynab/models/save_category_group.py | 4 +- ynab/models/save_category_group_response.py | 4 +- .../save_category_group_response_data.py | 4 +- ynab/models/save_category_response.py | 4 +- ynab/models/save_category_response_data.py | 4 +- ynab/models/save_month_category.py | 4 +- ynab/models/save_payee.py | 4 +- ynab/models/save_payee_response.py | 4 +- ynab/models/save_payee_response_data.py | 4 +- ynab/models/save_scheduled_transaction.py | 4 +- ynab/models/save_sub_transaction.py | 4 +- .../save_transaction_with_id_or_import_id.py | 4 +- .../save_transaction_with_optional_fields.py | 4 +- ynab/models/save_transactions_response.py | 4 +- .../models/save_transactions_response_data.py | 4 +- ynab/models/scheduled_sub_transaction.py | 4 +- ynab/models/scheduled_sub_transaction_base.py | 4 +- ynab/models/scheduled_transaction_detail.py | 4 +- .../models/scheduled_transaction_frequency.py | 4 +- ynab/models/scheduled_transaction_response.py | 4 +- .../scheduled_transaction_response_data.py | 4 +- ynab/models/scheduled_transaction_summary.py | 4 +- .../scheduled_transaction_summary_base.py | 4 +- .../models/scheduled_transactions_response.py | 4 +- .../scheduled_transactions_response_data.py | 4 +- ynab/models/sub_transaction.py | 4 +- ynab/models/sub_transaction_base.py | 4 +- ynab/models/transaction_cleared_status.py | 4 +- ynab/models/transaction_detail.py | 4 +- ynab/models/transaction_flag_color.py | 4 +- ynab/models/transaction_response.py | 4 +- ynab/models/transaction_response_data.py | 4 +- ynab/models/transaction_summary.py | 4 +- ynab/models/transaction_summary_base.py | 4 +- ynab/models/transactions_import_response.py | 4 +- .../transactions_import_response_data.py | 4 +- ynab/models/transactions_response.py | 4 +- ynab/models/transactions_response_data.py | 4 +- ynab/models/user.py | 4 +- ynab/models/user_response.py | 4 +- ynab/models/user_response_data.py | 4 +- ynab/rest.py | 4 +- 144 files changed, 379 insertions(+), 309 deletions(-) diff --git a/.gitignore b/.gitignore index fc75583..65b06b9 100644 --- a/.gitignore +++ b/.gitignore @@ -64,5 +64,3 @@ target/ # Ipython Notebook .ipynb_checkpoints -.socket-scans/ -.socket.facts.json diff --git a/docs/ExistingCategory.md b/docs/ExistingCategory.md index b0b20f5..93e12b3 100644 --- a/docs/ExistingCategory.md +++ b/docs/ExistingCategory.md @@ -8,9 +8,10 @@ Name | Type | Description | Notes **name** | **str** | | [optional] **note** | **str** | | [optional] **category_group_id** | **UUID** | The id of the category group to which this category belongs. An internal category group may not be specified. | [optional] -**goal_target** | **int** | 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** | **int** | 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. 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). | [optional] **goal_needs_whole_amount** | **bool** | 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_frequency** | **str** | 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. Omit to leave an existing target's cadence unchanged. | [optional] ## Example diff --git a/docs/NewCategory.md b/docs/NewCategory.md index 25866f3..d970d5a 100644 --- a/docs/NewCategory.md +++ b/docs/NewCategory.md @@ -8,9 +8,10 @@ Name | Type | Description | Notes **name** | **str** | | [optional] **note** | **str** | | [optional] **category_group_id** | **UUID** | The id of the category group to which this category belongs. An internal category group may not be specified. | [optional] -**goal_target** | **int** | 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** | **int** | 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. 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). | [optional] **goal_needs_whole_amount** | **bool** | 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_frequency** | **str** | 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. Omit to leave an existing target's cadence unchanged. | [optional] ## Example diff --git a/docs/SaveCategory.md b/docs/SaveCategory.md index 428be64..08f1462 100644 --- a/docs/SaveCategory.md +++ b/docs/SaveCategory.md @@ -8,9 +8,10 @@ Name | Type | Description | Notes **name** | **str** | | [optional] **note** | **str** | | [optional] **category_group_id** | **UUID** | The id of the category group to which this category belongs. An internal category group may not be specified. | [optional] -**goal_target** | **int** | 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** | **int** | 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. 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). | [optional] **goal_needs_whole_amount** | **bool** | 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_frequency** | **str** | 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. Omit to leave an existing target's cadence unchanged. | [optional] ## Example diff --git a/open_api_spec.yaml b/open_api_spec.yaml index 4d4633d..e666b52 100644 --- a/open_api_spec.yaml +++ b/open_api_spec.yaml @@ -1,24 +1,38 @@ openapi: 3.1.1 info: title: YNAB API Endpoints - description: 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 - version: 1.85.0 + description: |- + 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. + version: 1.86.0 servers: - url: https://api.ynab.com/v1 security: - bearer: [] tags: - name: User + description: The currently authenticated user - name: Plans + description: Plans are the top-level container for your YNAB data; accounts, + categories, payees, and transactions all belong to a plan. Most endpoints + require a plan_id, which can be obtained from "Get all plans". + Alternatively, "last-used" can be used in place of a plan_id to specify + the most recently used plan, and "default" can be used if [default plan + selection](https://api.ynab.com/#oauth-default-plan) is enabled. - name: Accounts - description: The accounts for a plan + description: The accounts for a plan. Every transaction belongs to an account, + and an account is either "on budget", where its activity is categorized + and planned, or a tracking account, where only its balance is tracked + (see the on_budget flag). - name: Categories - description: The categories for a plan + description: The categories for a plan, organized into category groups. + Category amounts (assigned, activity, available) are specific to a month, + and can be read and updated through the month-scoped category endpoints. - name: Payees - description: The payees for a plan + description: The payees for a plan. Transfers between accounts are represented + with special transfer payees; a payee with transfer_account_id set is the + transfer payee for that account. - name: Payee Locations description: When you enter a transaction and specify a payee on the YNAB mobile apps, the GPS coordinates for that location are stored, with your @@ -31,11 +45,20 @@ tags: Assign, Age of Money and category (assigned / activity / available) amounts are available. - name: Money Movements - description: The money movements for a plan + description: Money movements record money moved between two categories, or + between a category and Ready to Assign, within a plan month. Movements + performed together as a single action are linked by a money movement + group. - name: Transactions - description: The transactions for a plan + description: The transactions for a plan. Transaction amounts are specified in + [milliunits format](https://api.ynab.com/#formats). Split transactions + are represented with subtransactions, and transfers between accounts are + represented with transfer payees. - name: Scheduled Transactions - description: The scheduled transactions for a plan + description: The scheduled transactions for a plan; upcoming and recurring + transactions that have not yet been entered into an account. Each has a + frequency along with the first and next dates it will occur (date_first + and date_next). paths: /user: get: @@ -3247,6 +3270,7 @@ components: 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. + When updating a category, passing null removes any existing target. format: int64 goal_target_date: type: @@ -3261,6 +3285,15 @@ components: description: 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...'. + goal_frequency: + type: string + enum: + - monthly + - weekly + - yearly + description: 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. Omit to leave an existing target's cadence unchanged. ExistingCategory: allOf: - $ref: "#/components/schemas/SaveCategory" diff --git a/pyproject.toml b/pyproject.toml index a07976c..091517e 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -1,7 +1,7 @@ [tool.poetry] name = "ynab" version = "4.2.0" -description = "Official Python client for the YNAB API. API documentation available at https://api.ynab.com. Generated from server specification version 1.85.0" +description = "Official Python client for the YNAB API. API documentation available at https://api.ynab.com. Generated from server specification version 1.86.0" authors = ["YNAB"] license = "Apache-2.0" readme = "README.md" diff --git a/ynab/__init__.py b/ynab/__init__.py index 4387350..8836c94 100644 --- a/ynab/__init__.py +++ b/ynab/__init__.py @@ -5,16 +5,16 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. """ # noqa: E501 -__version__ = "4.1.0" +__version__ = "4.2.0" # Define package exports __all__ = [ diff --git a/ynab/api/accounts_api.py b/ynab/api/accounts_api.py index f0ffcd2..d44d9e0 100644 --- a/ynab/api/accounts_api.py +++ b/ynab/api/accounts_api.py @@ -1,9 +1,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/api/categories_api.py b/ynab/api/categories_api.py index c8268e5..a502a29 100644 --- a/ynab/api/categories_api.py +++ b/ynab/api/categories_api.py @@ -1,9 +1,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/api/money_movements_api.py b/ynab/api/money_movements_api.py index 554c8a5..eb3a11a 100644 --- a/ynab/api/money_movements_api.py +++ b/ynab/api/money_movements_api.py @@ -1,9 +1,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/api/months_api.py b/ynab/api/months_api.py index 0e2c3d4..fb2717a 100644 --- a/ynab/api/months_api.py +++ b/ynab/api/months_api.py @@ -1,9 +1,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/api/payee_locations_api.py b/ynab/api/payee_locations_api.py index e09c7aa..2277326 100644 --- a/ynab/api/payee_locations_api.py +++ b/ynab/api/payee_locations_api.py @@ -1,9 +1,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/api/payees_api.py b/ynab/api/payees_api.py index 6a8a51f..99f6189 100644 --- a/ynab/api/payees_api.py +++ b/ynab/api/payees_api.py @@ -1,9 +1,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/api/plans_api.py b/ynab/api/plans_api.py index 4ae2bea..e8e62c3 100644 --- a/ynab/api/plans_api.py +++ b/ynab/api/plans_api.py @@ -1,9 +1,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/api/scheduled_transactions_api.py b/ynab/api/scheduled_transactions_api.py index c635326..051349a 100644 --- a/ynab/api/scheduled_transactions_api.py +++ b/ynab/api/scheduled_transactions_api.py @@ -1,9 +1,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/api/transactions_api.py b/ynab/api/transactions_api.py index bfe497a..01366d3 100644 --- a/ynab/api/transactions_api.py +++ b/ynab/api/transactions_api.py @@ -1,9 +1,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/api/user_api.py b/ynab/api/user_api.py index a8da17d..5623b90 100644 --- a/ynab/api/user_api.py +++ b/ynab/api/user_api.py @@ -1,9 +1,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/api_client.py b/ynab/api_client.py index 06e3e93..dd23f2e 100644 --- a/ynab/api_client.py +++ b/ynab/api_client.py @@ -1,9 +1,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. @@ -91,7 +91,7 @@ def __init__( self.default_headers[header_name] = header_value self.cookie = cookie # Set default User-Agent. - self.user_agent = 'OpenAPI-Generator/4.1.0/python' + self.user_agent = 'OpenAPI-Generator/4.2.0/python' self.client_side_validation = configuration.client_side_validation def __enter__(self): diff --git a/ynab/configuration.py b/ynab/configuration.py index 637bec7..ec85ec6 100644 --- a/ynab/configuration.py +++ b/ynab/configuration.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. @@ -504,8 +504,8 @@ def to_debug_report(self) -> str: return "Python SDK Debug Report:\n"\ "OS: {env}\n"\ "Python Version: {pyversion}\n"\ - "Version of the API: 1.85.0\n"\ - "SDK Package Version: 4.1.0".\ + "Version of the API: 1.86.0\n"\ + "SDK Package Version: 4.2.0".\ format(env=sys.platform, pyversion=sys.version) def get_host_settings(self) -> List[HostSetting]: diff --git a/ynab/exceptions.py b/ynab/exceptions.py index 84afb65..f052beb 100644 --- a/ynab/exceptions.py +++ b/ynab/exceptions.py @@ -1,9 +1,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/__init__.py b/ynab/models/__init__.py index 42666a6..ddef04d 100644 --- a/ynab/models/__init__.py +++ b/ynab/models/__init__.py @@ -4,9 +4,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/account.py b/ynab/models/account.py index 7319ab4..4291a8c 100644 --- a/ynab/models/account.py +++ b/ynab/models/account.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/account_base.py b/ynab/models/account_base.py index 463f2ac..36ff1c4 100644 --- a/ynab/models/account_base.py +++ b/ynab/models/account_base.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/account_response.py b/ynab/models/account_response.py index dcb5f7f..d466de7 100644 --- a/ynab/models/account_response.py +++ b/ynab/models/account_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/account_response_data.py b/ynab/models/account_response_data.py index fefbf35..97f2e71 100644 --- a/ynab/models/account_response_data.py +++ b/ynab/models/account_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/account_type.py b/ynab/models/account_type.py index b8e8e95..4412232 100644 --- a/ynab/models/account_type.py +++ b/ynab/models/account_type.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/accounts_response.py b/ynab/models/accounts_response.py index e378be5..dcb2a7b 100644 --- a/ynab/models/accounts_response.py +++ b/ynab/models/accounts_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/accounts_response_data.py b/ynab/models/accounts_response_data.py index 169982e..c547428 100644 --- a/ynab/models/accounts_response_data.py +++ b/ynab/models/accounts_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/bulk_response.py b/ynab/models/bulk_response.py index 5cf7a33..ddf5f6b 100644 --- a/ynab/models/bulk_response.py +++ b/ynab/models/bulk_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/bulk_response_data.py b/ynab/models/bulk_response_data.py index 7b214bc..8cf14d1 100644 --- a/ynab/models/bulk_response_data.py +++ b/ynab/models/bulk_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/bulk_response_data_bulk.py b/ynab/models/bulk_response_data_bulk.py index 650e63b..45de9b2 100644 --- a/ynab/models/bulk_response_data_bulk.py +++ b/ynab/models/bulk_response_data_bulk.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/bulk_transactions.py b/ynab/models/bulk_transactions.py index e6334cb..8926e09 100644 --- a/ynab/models/bulk_transactions.py +++ b/ynab/models/bulk_transactions.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/categories_response.py b/ynab/models/categories_response.py index 0f6f85e..311621c 100644 --- a/ynab/models/categories_response.py +++ b/ynab/models/categories_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/categories_response_data.py b/ynab/models/categories_response_data.py index 916d9b5..a8252ca 100644 --- a/ynab/models/categories_response_data.py +++ b/ynab/models/categories_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/category.py b/ynab/models/category.py index 08cf231..8053968 100644 --- a/ynab/models/category.py +++ b/ynab/models/category.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/category_base.py b/ynab/models/category_base.py index 797d04b..4685eb3 100644 --- a/ynab/models/category_base.py +++ b/ynab/models/category_base.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/category_group.py b/ynab/models/category_group.py index c7e43fd..54f8bb2 100644 --- a/ynab/models/category_group.py +++ b/ynab/models/category_group.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/category_group_with_categories.py b/ynab/models/category_group_with_categories.py index 171bc6e..67c1ef5 100644 --- a/ynab/models/category_group_with_categories.py +++ b/ynab/models/category_group_with_categories.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/category_response.py b/ynab/models/category_response.py index c40e72b..8311148 100644 --- a/ynab/models/category_response.py +++ b/ynab/models/category_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/category_response_data.py b/ynab/models/category_response_data.py index b581a12..6d4fc1e 100644 --- a/ynab/models/category_response_data.py +++ b/ynab/models/category_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/currency_format.py b/ynab/models/currency_format.py index 892377b..327670b 100644 --- a/ynab/models/currency_format.py +++ b/ynab/models/currency_format.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/date_format.py b/ynab/models/date_format.py index 6e6492e..8481b1e 100644 --- a/ynab/models/date_format.py +++ b/ynab/models/date_format.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/error_detail.py b/ynab/models/error_detail.py index d3f09e9..7242496 100644 --- a/ynab/models/error_detail.py +++ b/ynab/models/error_detail.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/error_response.py b/ynab/models/error_response.py index e83f5ac..ba405ad 100644 --- a/ynab/models/error_response.py +++ b/ynab/models/error_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/existing_category.py b/ynab/models/existing_category.py index 04bdd41..f827ea8 100644 --- a/ynab/models/existing_category.py +++ b/ynab/models/existing_category.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. @@ -18,7 +18,7 @@ import json from datetime import date -from pydantic import BaseModel, ConfigDict, Field, StrictBool, StrictInt, StrictStr +from pydantic import BaseModel, ConfigDict, Field, StrictBool, StrictInt, StrictStr, field_validator from typing import Any, ClassVar, Dict, List, Optional from uuid import UUID from typing import Optional, Set @@ -32,10 +32,21 @@ class ExistingCategory(BaseModel): name: Optional[StrictStr] = None note: Optional[StrictStr] = None category_group_id: Optional[UUID] = Field(default=None, description="The id of the category group to which this category belongs. An internal category group may not be specified.") - goal_target: Optional[StrictInt] = Field(default=None, description="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.") + goal_target: Optional[StrictInt] = Field(default=None, description="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. When updating a category, passing null removes any existing target.") goal_target_date: Optional[date] = Field(default=None, description="The goal target date in ISO format (e.g. 2016-12-01).") goal_needs_whole_amount: Optional[StrictBool] = Field(default=None, description="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...'.") - __properties: ClassVar[List[str]] = ["name", "note", "category_group_id", "goal_target", "goal_target_date", "goal_needs_whole_amount"] + goal_frequency: Optional[StrictStr] = Field(default=None, description="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. Omit to leave an existing target's cadence unchanged.") + __properties: ClassVar[List[str]] = ["name", "note", "category_group_id", "goal_target", "goal_target_date", "goal_needs_whole_amount", "goal_frequency"] + + @field_validator('goal_frequency') + def goal_frequency_validate_enum(cls, value): + """Validates the enum""" + if value is None: + return value + + if value not in set(['monthly', 'weekly', 'yearly']): + raise ValueError("must be one of enum values ('monthly', 'weekly', 'yearly')") + return value model_config = ConfigDict( validate_by_name=True, @@ -93,7 +104,8 @@ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]: "category_group_id": obj.get("category_group_id"), "goal_target": obj.get("goal_target"), "goal_target_date": obj.get("goal_target_date"), - "goal_needs_whole_amount": obj.get("goal_needs_whole_amount") + "goal_needs_whole_amount": obj.get("goal_needs_whole_amount"), + "goal_frequency": obj.get("goal_frequency") }) return _obj diff --git a/ynab/models/existing_transaction.py b/ynab/models/existing_transaction.py index 03b89ad..527f955 100644 --- a/ynab/models/existing_transaction.py +++ b/ynab/models/existing_transaction.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/hybrid_transaction.py b/ynab/models/hybrid_transaction.py index 86d74cf..32a0938 100644 --- a/ynab/models/hybrid_transaction.py +++ b/ynab/models/hybrid_transaction.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/hybrid_transactions_response.py b/ynab/models/hybrid_transactions_response.py index b27023c..1aa230d 100644 --- a/ynab/models/hybrid_transactions_response.py +++ b/ynab/models/hybrid_transactions_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/hybrid_transactions_response_data.py b/ynab/models/hybrid_transactions_response_data.py index 99c090c..042ca50 100644 --- a/ynab/models/hybrid_transactions_response_data.py +++ b/ynab/models/hybrid_transactions_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/money_movement.py b/ynab/models/money_movement.py index 688aaa0..5c44ae7 100644 --- a/ynab/models/money_movement.py +++ b/ynab/models/money_movement.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/money_movement_base.py b/ynab/models/money_movement_base.py index 789adaa..046ecd6 100644 --- a/ynab/models/money_movement_base.py +++ b/ynab/models/money_movement_base.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/money_movement_group.py b/ynab/models/money_movement_group.py index f3c5ba4..2faf129 100644 --- a/ynab/models/money_movement_group.py +++ b/ynab/models/money_movement_group.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/money_movement_groups_response.py b/ynab/models/money_movement_groups_response.py index 62a0ea9..7a9368c 100644 --- a/ynab/models/money_movement_groups_response.py +++ b/ynab/models/money_movement_groups_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/money_movement_groups_response_data.py b/ynab/models/money_movement_groups_response_data.py index 54e4faa..bd30d91 100644 --- a/ynab/models/money_movement_groups_response_data.py +++ b/ynab/models/money_movement_groups_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/money_movements_response.py b/ynab/models/money_movements_response.py index 33bdf88..5580118 100644 --- a/ynab/models/money_movements_response.py +++ b/ynab/models/money_movements_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/money_movements_response_data.py b/ynab/models/money_movements_response_data.py index e5b9bcb..2002567 100644 --- a/ynab/models/money_movements_response_data.py +++ b/ynab/models/money_movements_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/month_detail.py b/ynab/models/month_detail.py index 0652c87..33eb8de 100644 --- a/ynab/models/month_detail.py +++ b/ynab/models/month_detail.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/month_detail_base.py b/ynab/models/month_detail_base.py index 56477e8..3ed0779 100644 --- a/ynab/models/month_detail_base.py +++ b/ynab/models/month_detail_base.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/month_detail_response.py b/ynab/models/month_detail_response.py index 8a40e01..0641dc3 100644 --- a/ynab/models/month_detail_response.py +++ b/ynab/models/month_detail_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/month_detail_response_data.py b/ynab/models/month_detail_response_data.py index 59d70be..3234ba1 100644 --- a/ynab/models/month_detail_response_data.py +++ b/ynab/models/month_detail_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/month_summaries_response.py b/ynab/models/month_summaries_response.py index d31b3d8..25eba9f 100644 --- a/ynab/models/month_summaries_response.py +++ b/ynab/models/month_summaries_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/month_summaries_response_data.py b/ynab/models/month_summaries_response_data.py index c3a714a..91f9b52 100644 --- a/ynab/models/month_summaries_response_data.py +++ b/ynab/models/month_summaries_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/month_summary.py b/ynab/models/month_summary.py index b0130dc..44bd5ee 100644 --- a/ynab/models/month_summary.py +++ b/ynab/models/month_summary.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/month_summary_base.py b/ynab/models/month_summary_base.py index 2c1d40a..f71bc3c 100644 --- a/ynab/models/month_summary_base.py +++ b/ynab/models/month_summary_base.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/new_category.py b/ynab/models/new_category.py index 50398f8..cb9d9d7 100644 --- a/ynab/models/new_category.py +++ b/ynab/models/new_category.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. @@ -18,7 +18,7 @@ import json from datetime import date -from pydantic import BaseModel, ConfigDict, Field, StrictBool, StrictInt, StrictStr +from pydantic import BaseModel, ConfigDict, Field, StrictBool, StrictInt, StrictStr, field_validator from typing import Any, ClassVar, Dict, List, Optional from uuid import UUID from typing import Optional, Set @@ -32,10 +32,21 @@ class NewCategory(BaseModel): name: Optional[StrictStr] = None note: Optional[StrictStr] = None category_group_id: Optional[UUID] = Field(default=None, description="The id of the category group to which this category belongs. An internal category group may not be specified.") - goal_target: Optional[StrictInt] = Field(default=None, description="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.") + goal_target: Optional[StrictInt] = Field(default=None, description="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. When updating a category, passing null removes any existing target.") goal_target_date: Optional[date] = Field(default=None, description="The goal target date in ISO format (e.g. 2016-12-01).") goal_needs_whole_amount: Optional[StrictBool] = Field(default=None, description="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...'.") - __properties: ClassVar[List[str]] = ["name", "note", "category_group_id", "goal_target", "goal_target_date", "goal_needs_whole_amount"] + goal_frequency: Optional[StrictStr] = Field(default=None, description="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. Omit to leave an existing target's cadence unchanged.") + __properties: ClassVar[List[str]] = ["name", "note", "category_group_id", "goal_target", "goal_target_date", "goal_needs_whole_amount", "goal_frequency"] + + @field_validator('goal_frequency') + def goal_frequency_validate_enum(cls, value): + """Validates the enum""" + if value is None: + return value + + if value not in set(['monthly', 'weekly', 'yearly']): + raise ValueError("must be one of enum values ('monthly', 'weekly', 'yearly')") + return value model_config = ConfigDict( validate_by_name=True, @@ -93,7 +104,8 @@ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]: "category_group_id": obj.get("category_group_id"), "goal_target": obj.get("goal_target"), "goal_target_date": obj.get("goal_target_date"), - "goal_needs_whole_amount": obj.get("goal_needs_whole_amount") + "goal_needs_whole_amount": obj.get("goal_needs_whole_amount"), + "goal_frequency": obj.get("goal_frequency") }) return _obj diff --git a/ynab/models/new_transaction.py b/ynab/models/new_transaction.py index 92adb20..be3215c 100644 --- a/ynab/models/new_transaction.py +++ b/ynab/models/new_transaction.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/patch_category_group_wrapper.py b/ynab/models/patch_category_group_wrapper.py index 49e0948..89f5e8d 100644 --- a/ynab/models/patch_category_group_wrapper.py +++ b/ynab/models/patch_category_group_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/patch_category_wrapper.py b/ynab/models/patch_category_wrapper.py index afdd345..f542096 100644 --- a/ynab/models/patch_category_wrapper.py +++ b/ynab/models/patch_category_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/patch_month_category_wrapper.py b/ynab/models/patch_month_category_wrapper.py index 2f64979..1d96b13 100644 --- a/ynab/models/patch_month_category_wrapper.py +++ b/ynab/models/patch_month_category_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/patch_payee_wrapper.py b/ynab/models/patch_payee_wrapper.py index 8fe09e4..a700253 100644 --- a/ynab/models/patch_payee_wrapper.py +++ b/ynab/models/patch_payee_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/patch_transactions_wrapper.py b/ynab/models/patch_transactions_wrapper.py index e889afc..3dc00cb 100644 --- a/ynab/models/patch_transactions_wrapper.py +++ b/ynab/models/patch_transactions_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/payee.py b/ynab/models/payee.py index b695144..3013e20 100644 --- a/ynab/models/payee.py +++ b/ynab/models/payee.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/payee_location.py b/ynab/models/payee_location.py index 044a68f..3f154de 100644 --- a/ynab/models/payee_location.py +++ b/ynab/models/payee_location.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/payee_location_response.py b/ynab/models/payee_location_response.py index 417c456..2189ad5 100644 --- a/ynab/models/payee_location_response.py +++ b/ynab/models/payee_location_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/payee_location_response_data.py b/ynab/models/payee_location_response_data.py index 91a1851..2da575b 100644 --- a/ynab/models/payee_location_response_data.py +++ b/ynab/models/payee_location_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/payee_locations_response.py b/ynab/models/payee_locations_response.py index 4bc93bf..be6525c 100644 --- a/ynab/models/payee_locations_response.py +++ b/ynab/models/payee_locations_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/payee_locations_response_data.py b/ynab/models/payee_locations_response_data.py index 142eaa0..dc2e42f 100644 --- a/ynab/models/payee_locations_response_data.py +++ b/ynab/models/payee_locations_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/payee_response.py b/ynab/models/payee_response.py index cacc47f..f058c4e 100644 --- a/ynab/models/payee_response.py +++ b/ynab/models/payee_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/payee_response_data.py b/ynab/models/payee_response_data.py index 85a080a..62aabb9 100644 --- a/ynab/models/payee_response_data.py +++ b/ynab/models/payee_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/payees_response.py b/ynab/models/payees_response.py index 714559c..71b203a 100644 --- a/ynab/models/payees_response.py +++ b/ynab/models/payees_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/payees_response_data.py b/ynab/models/payees_response_data.py index da396f5..776e887 100644 --- a/ynab/models/payees_response_data.py +++ b/ynab/models/payees_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/plan_detail.py b/ynab/models/plan_detail.py index 88541cc..51a9273 100644 --- a/ynab/models/plan_detail.py +++ b/ynab/models/plan_detail.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/plan_detail_response.py b/ynab/models/plan_detail_response.py index 65763b6..e2b4f58 100644 --- a/ynab/models/plan_detail_response.py +++ b/ynab/models/plan_detail_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/plan_detail_response_data.py b/ynab/models/plan_detail_response_data.py index 4edce76..958df3f 100644 --- a/ynab/models/plan_detail_response_data.py +++ b/ynab/models/plan_detail_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/plan_settings.py b/ynab/models/plan_settings.py index bdf6df4..818e232 100644 --- a/ynab/models/plan_settings.py +++ b/ynab/models/plan_settings.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/plan_settings_response.py b/ynab/models/plan_settings_response.py index c38158c..761593c 100644 --- a/ynab/models/plan_settings_response.py +++ b/ynab/models/plan_settings_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/plan_settings_response_data.py b/ynab/models/plan_settings_response_data.py index 5e3d120..219c10c 100644 --- a/ynab/models/plan_settings_response_data.py +++ b/ynab/models/plan_settings_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/plan_summary.py b/ynab/models/plan_summary.py index 0fb6355..9d5e7e3 100644 --- a/ynab/models/plan_summary.py +++ b/ynab/models/plan_summary.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/plan_summary_response.py b/ynab/models/plan_summary_response.py index 9557813..80184ab 100644 --- a/ynab/models/plan_summary_response.py +++ b/ynab/models/plan_summary_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/plan_summary_response_data.py b/ynab/models/plan_summary_response_data.py index 6fc45fc..4612bca 100644 --- a/ynab/models/plan_summary_response_data.py +++ b/ynab/models/plan_summary_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/post_account_wrapper.py b/ynab/models/post_account_wrapper.py index b88554e..a5d2d9b 100644 --- a/ynab/models/post_account_wrapper.py +++ b/ynab/models/post_account_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/post_category_group_wrapper.py b/ynab/models/post_category_group_wrapper.py index c160971..e583466 100644 --- a/ynab/models/post_category_group_wrapper.py +++ b/ynab/models/post_category_group_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/post_category_wrapper.py b/ynab/models/post_category_wrapper.py index 579a1ef..b11eaf2 100644 --- a/ynab/models/post_category_wrapper.py +++ b/ynab/models/post_category_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/post_payee.py b/ynab/models/post_payee.py index 75a7716..a168288 100644 --- a/ynab/models/post_payee.py +++ b/ynab/models/post_payee.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/post_payee_wrapper.py b/ynab/models/post_payee_wrapper.py index 69a6d93..266f121 100644 --- a/ynab/models/post_payee_wrapper.py +++ b/ynab/models/post_payee_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/post_scheduled_transaction_wrapper.py b/ynab/models/post_scheduled_transaction_wrapper.py index e704e2a..2c9657d 100644 --- a/ynab/models/post_scheduled_transaction_wrapper.py +++ b/ynab/models/post_scheduled_transaction_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/post_transactions_wrapper.py b/ynab/models/post_transactions_wrapper.py index 3e6cf7f..3c7b6d5 100644 --- a/ynab/models/post_transactions_wrapper.py +++ b/ynab/models/post_transactions_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/put_scheduled_transaction_wrapper.py b/ynab/models/put_scheduled_transaction_wrapper.py index b4be344..7ebbe4a 100644 --- a/ynab/models/put_scheduled_transaction_wrapper.py +++ b/ynab/models/put_scheduled_transaction_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/put_transaction_wrapper.py b/ynab/models/put_transaction_wrapper.py index b416b72..6e5c629 100644 --- a/ynab/models/put_transaction_wrapper.py +++ b/ynab/models/put_transaction_wrapper.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_account.py b/ynab/models/save_account.py index b2efbc7..95249f7 100644 --- a/ynab/models/save_account.py +++ b/ynab/models/save_account.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_account_type.py b/ynab/models/save_account_type.py index 3cfed86..0ef51ae 100644 --- a/ynab/models/save_account_type.py +++ b/ynab/models/save_account_type.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_category.py b/ynab/models/save_category.py index c116a99..1762f6e 100644 --- a/ynab/models/save_category.py +++ b/ynab/models/save_category.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. @@ -18,7 +18,7 @@ import json from datetime import date -from pydantic import BaseModel, ConfigDict, Field, StrictBool, StrictInt, StrictStr +from pydantic import BaseModel, ConfigDict, Field, StrictBool, StrictInt, StrictStr, field_validator from typing import Any, ClassVar, Dict, List, Optional from uuid import UUID from typing import Optional, Set @@ -32,10 +32,21 @@ class SaveCategory(BaseModel): name: Optional[StrictStr] = None note: Optional[StrictStr] = None category_group_id: Optional[UUID] = Field(default=None, description="The id of the category group to which this category belongs. An internal category group may not be specified.") - goal_target: Optional[StrictInt] = Field(default=None, description="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.") + goal_target: Optional[StrictInt] = Field(default=None, description="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. When updating a category, passing null removes any existing target.") goal_target_date: Optional[date] = Field(default=None, description="The goal target date in ISO format (e.g. 2016-12-01).") goal_needs_whole_amount: Optional[StrictBool] = Field(default=None, description="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...'.") - __properties: ClassVar[List[str]] = ["name", "note", "category_group_id", "goal_target", "goal_target_date", "goal_needs_whole_amount"] + goal_frequency: Optional[StrictStr] = Field(default=None, description="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. Omit to leave an existing target's cadence unchanged.") + __properties: ClassVar[List[str]] = ["name", "note", "category_group_id", "goal_target", "goal_target_date", "goal_needs_whole_amount", "goal_frequency"] + + @field_validator('goal_frequency') + def goal_frequency_validate_enum(cls, value): + """Validates the enum""" + if value is None: + return value + + if value not in set(['monthly', 'weekly', 'yearly']): + raise ValueError("must be one of enum values ('monthly', 'weekly', 'yearly')") + return value model_config = ConfigDict( validate_by_name=True, @@ -118,7 +129,8 @@ def from_dict(cls, obj: Optional[Dict[str, Any]]) -> Optional[Self]: "category_group_id": obj.get("category_group_id"), "goal_target": obj.get("goal_target"), "goal_target_date": obj.get("goal_target_date"), - "goal_needs_whole_amount": obj.get("goal_needs_whole_amount") + "goal_needs_whole_amount": obj.get("goal_needs_whole_amount"), + "goal_frequency": obj.get("goal_frequency") }) return _obj diff --git a/ynab/models/save_category_group.py b/ynab/models/save_category_group.py index f23e5ca..cdca4dd 100644 --- a/ynab/models/save_category_group.py +++ b/ynab/models/save_category_group.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_category_group_response.py b/ynab/models/save_category_group_response.py index 7327548..0b8122d 100644 --- a/ynab/models/save_category_group_response.py +++ b/ynab/models/save_category_group_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_category_group_response_data.py b/ynab/models/save_category_group_response_data.py index c05dd11..de5c382 100644 --- a/ynab/models/save_category_group_response_data.py +++ b/ynab/models/save_category_group_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_category_response.py b/ynab/models/save_category_response.py index 18adb16..d0588cd 100644 --- a/ynab/models/save_category_response.py +++ b/ynab/models/save_category_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_category_response_data.py b/ynab/models/save_category_response_data.py index 2f1bcc1..922882c 100644 --- a/ynab/models/save_category_response_data.py +++ b/ynab/models/save_category_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_month_category.py b/ynab/models/save_month_category.py index e90ca57..991ce70 100644 --- a/ynab/models/save_month_category.py +++ b/ynab/models/save_month_category.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_payee.py b/ynab/models/save_payee.py index e7a05a7..8011c6f 100644 --- a/ynab/models/save_payee.py +++ b/ynab/models/save_payee.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_payee_response.py b/ynab/models/save_payee_response.py index ea57948..0ed298e 100644 --- a/ynab/models/save_payee_response.py +++ b/ynab/models/save_payee_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_payee_response_data.py b/ynab/models/save_payee_response_data.py index 4b63572..448f406 100644 --- a/ynab/models/save_payee_response_data.py +++ b/ynab/models/save_payee_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_scheduled_transaction.py b/ynab/models/save_scheduled_transaction.py index fa55c53..ef8ecf0 100644 --- a/ynab/models/save_scheduled_transaction.py +++ b/ynab/models/save_scheduled_transaction.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_sub_transaction.py b/ynab/models/save_sub_transaction.py index 18c0962..e4f756d 100644 --- a/ynab/models/save_sub_transaction.py +++ b/ynab/models/save_sub_transaction.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_transaction_with_id_or_import_id.py b/ynab/models/save_transaction_with_id_or_import_id.py index 4dadd83..d073de5 100644 --- a/ynab/models/save_transaction_with_id_or_import_id.py +++ b/ynab/models/save_transaction_with_id_or_import_id.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_transaction_with_optional_fields.py b/ynab/models/save_transaction_with_optional_fields.py index 5a8d959..caa2098 100644 --- a/ynab/models/save_transaction_with_optional_fields.py +++ b/ynab/models/save_transaction_with_optional_fields.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_transactions_response.py b/ynab/models/save_transactions_response.py index d228d5c..8a687a7 100644 --- a/ynab/models/save_transactions_response.py +++ b/ynab/models/save_transactions_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/save_transactions_response_data.py b/ynab/models/save_transactions_response_data.py index 48e1889..1eba256 100644 --- a/ynab/models/save_transactions_response_data.py +++ b/ynab/models/save_transactions_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/scheduled_sub_transaction.py b/ynab/models/scheduled_sub_transaction.py index 7077bb1..eec4c99 100644 --- a/ynab/models/scheduled_sub_transaction.py +++ b/ynab/models/scheduled_sub_transaction.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/scheduled_sub_transaction_base.py b/ynab/models/scheduled_sub_transaction_base.py index 3b088bd..12ae301 100644 --- a/ynab/models/scheduled_sub_transaction_base.py +++ b/ynab/models/scheduled_sub_transaction_base.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/scheduled_transaction_detail.py b/ynab/models/scheduled_transaction_detail.py index c662aa7..6e03096 100644 --- a/ynab/models/scheduled_transaction_detail.py +++ b/ynab/models/scheduled_transaction_detail.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/scheduled_transaction_frequency.py b/ynab/models/scheduled_transaction_frequency.py index af630df..9fe1335 100644 --- a/ynab/models/scheduled_transaction_frequency.py +++ b/ynab/models/scheduled_transaction_frequency.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/scheduled_transaction_response.py b/ynab/models/scheduled_transaction_response.py index b73bf07..492963e 100644 --- a/ynab/models/scheduled_transaction_response.py +++ b/ynab/models/scheduled_transaction_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/scheduled_transaction_response_data.py b/ynab/models/scheduled_transaction_response_data.py index ced047b..4366c7c 100644 --- a/ynab/models/scheduled_transaction_response_data.py +++ b/ynab/models/scheduled_transaction_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/scheduled_transaction_summary.py b/ynab/models/scheduled_transaction_summary.py index 156c498..941ce14 100644 --- a/ynab/models/scheduled_transaction_summary.py +++ b/ynab/models/scheduled_transaction_summary.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/scheduled_transaction_summary_base.py b/ynab/models/scheduled_transaction_summary_base.py index f2c0f54..b6d8a04 100644 --- a/ynab/models/scheduled_transaction_summary_base.py +++ b/ynab/models/scheduled_transaction_summary_base.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/scheduled_transactions_response.py b/ynab/models/scheduled_transactions_response.py index bb9f12c..275cf85 100644 --- a/ynab/models/scheduled_transactions_response.py +++ b/ynab/models/scheduled_transactions_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/scheduled_transactions_response_data.py b/ynab/models/scheduled_transactions_response_data.py index 001821e..c930fe4 100644 --- a/ynab/models/scheduled_transactions_response_data.py +++ b/ynab/models/scheduled_transactions_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/sub_transaction.py b/ynab/models/sub_transaction.py index 177d532..d1aeb82 100644 --- a/ynab/models/sub_transaction.py +++ b/ynab/models/sub_transaction.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/sub_transaction_base.py b/ynab/models/sub_transaction_base.py index 1c996d4..6749f7c 100644 --- a/ynab/models/sub_transaction_base.py +++ b/ynab/models/sub_transaction_base.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/transaction_cleared_status.py b/ynab/models/transaction_cleared_status.py index 298439a..036c53a 100644 --- a/ynab/models/transaction_cleared_status.py +++ b/ynab/models/transaction_cleared_status.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/transaction_detail.py b/ynab/models/transaction_detail.py index 1aca1af..6b218b4 100644 --- a/ynab/models/transaction_detail.py +++ b/ynab/models/transaction_detail.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/transaction_flag_color.py b/ynab/models/transaction_flag_color.py index cb7ea74..c564872 100644 --- a/ynab/models/transaction_flag_color.py +++ b/ynab/models/transaction_flag_color.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/transaction_response.py b/ynab/models/transaction_response.py index 5a55638..0b57ccb 100644 --- a/ynab/models/transaction_response.py +++ b/ynab/models/transaction_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/transaction_response_data.py b/ynab/models/transaction_response_data.py index 8140b4b..9ddc7f7 100644 --- a/ynab/models/transaction_response_data.py +++ b/ynab/models/transaction_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/transaction_summary.py b/ynab/models/transaction_summary.py index 83ec9c3..0cf04d5 100644 --- a/ynab/models/transaction_summary.py +++ b/ynab/models/transaction_summary.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/transaction_summary_base.py b/ynab/models/transaction_summary_base.py index c6db058..108d534 100644 --- a/ynab/models/transaction_summary_base.py +++ b/ynab/models/transaction_summary_base.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/transactions_import_response.py b/ynab/models/transactions_import_response.py index 4e59c2e..b17b06a 100644 --- a/ynab/models/transactions_import_response.py +++ b/ynab/models/transactions_import_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/transactions_import_response_data.py b/ynab/models/transactions_import_response_data.py index 767a13b..01062b3 100644 --- a/ynab/models/transactions_import_response_data.py +++ b/ynab/models/transactions_import_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/transactions_response.py b/ynab/models/transactions_response.py index 6872485..049691e 100644 --- a/ynab/models/transactions_response.py +++ b/ynab/models/transactions_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/transactions_response_data.py b/ynab/models/transactions_response_data.py index f7770dd..d212e81 100644 --- a/ynab/models/transactions_response_data.py +++ b/ynab/models/transactions_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/user.py b/ynab/models/user.py index 3624e4b..2d30c71 100644 --- a/ynab/models/user.py +++ b/ynab/models/user.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/user_response.py b/ynab/models/user_response.py index 5882370..030fe83 100644 --- a/ynab/models/user_response.py +++ b/ynab/models/user_response.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/models/user_response_data.py b/ynab/models/user_response_data.py index c2249cc..7b6d641 100644 --- a/ynab/models/user_response_data.py +++ b/ynab/models/user_response_data.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. diff --git a/ynab/rest.py b/ynab/rest.py index 6220b30..5e99bfb 100644 --- a/ynab/rest.py +++ b/ynab/rest.py @@ -3,9 +3,9 @@ """ 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. - The version of the OpenAPI document: 1.85.0 + The version of the OpenAPI document: 1.86.0 Generated by OpenAPI Generator (https://openapi-generator.tech) Do not edit the class manually. From dbe023e2c6608de0f7ec38c71d1de7ddcf4ac730 Mon Sep 17 00:00:00 2001 From: Brady Holt Date: Wed, 15 Jul 2026 10:43:59 -0500 Subject: [PATCH 2/4] Regenerate SDK from server specification version 1.86.0 Routine regeneration from the YNAB OpenAPI spec (1.86.0 -> 1.86.0). Functional change: - PATCH /transactions success response code changed from 200 -> 209 in the spec, docs, and the bulk-update methods in transactions_api.py. Also adds scripts/generate-and-pr.sh, the wrapper that regenerates the SDK and hands off the commit + PR to Claude. --- scripts/generate-and-pr.sh | 94 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 94 insertions(+) create mode 100755 scripts/generate-and-pr.sh diff --git a/scripts/generate-and-pr.sh b/scripts/generate-and-pr.sh new file mode 100755 index 0000000..f0b0d7a --- /dev/null +++ b/scripts/generate-and-pr.sh @@ -0,0 +1,94 @@ +#!/usr/bin/env bash +# +# Regenerate the SDK from the latest YNAB API spec, then optionally open a PR. +# +# Wraps scripts/generate.sh. After regenerating it detects the old -> new spec +# version and, if you confirm, ensures you're on a gen- branch and +# hands the commit + PR off to `claude`, which writes a real summary of the +# functional spec changes. Requires the `claude` CLI to be installed. + +set -euo pipefail + +REPO_ROOT="$(git rev-parse --show-toplevel)" +SCRIPT_DIR="$REPO_ROOT/scripts" +SPEC="$REPO_ROOT/open_api_spec.yaml" + +cd "$REPO_ROOT" + +# Extract info.version from an OpenAPI spec on stdin (the 2-space-indented +# `version:` inside the top-level `info:` block, not `openapi:` or nested ones). +spec_version() { + awk '/^info:/{f=1} f && /^ version:/{print $2; exit}' +} + +OLD_VERSION="$(git show HEAD:open_api_spec.yaml 2>/dev/null | spec_version || true)" + +# Regenerate: downloads the latest spec and runs openapi-generator. +bash "$SCRIPT_DIR/generate.sh" + +NEW_VERSION="$(spec_version < "$SPEC")" + +if [[ -z "$(git status --porcelain)" ]]; then + echo + echo "No changes after regeneration — spec ${NEW_VERSION:-unknown} is already up to date. Nothing to do." + exit 0 +fi + +echo +echo "Regeneration produced changes. Spec version: ${OLD_VERSION:-unknown} -> ${NEW_VERSION:-unknown}" +git status --short +echo + +read -r -p "Create a pull request for these changes? [y/N] " reply +case "$reply" in + [yY] | [yY][eE][sS]) ;; + *) + echo "Leaving the regenerated changes uncommitted in the working tree. Done." + exit 0 + ;; +esac + +# Never commit on a protected branch: if we're on one, create a fresh +# gen- branch (the uncommitted regen changes carry over). Otherwise +# stay on the current feature branch. +BRANCH="$(git rev-parse --abbrev-ref HEAD)" +DESIRED="gen-${NEW_VERSION//./-}" +case "$BRANCH" in + main | master | develop) + target="$DESIRED" + if git show-ref --verify --quiet "refs/heads/$target"; then + n=2 + while git show-ref --verify --quiet "refs/heads/${DESIRED}-${n}"; do n=$((n + 1)); done + target="${DESIRED}-${n}" + fi + echo "On protected branch '$BRANCH'; creating and switching to '$target'." + git switch -c "$target" + ;; + *) + echo "Committing on current branch: '$BRANCH'." + ;; +esac + +echo +echo "Handing off to Claude to write the commit + PR (this may take a minute)..." +echo + +# Scope the spawned Claude to only the tools the commit/PR flow needs so the +# non-interactive run doesn't stall on approval prompts, without granting a +# blanket permission bypass. +ALLOWED_TOOLS="Bash Read Edit Write Grep Glob Skill TodoWrite" + +PROMPT="The working tree contains a regeneration of this SDK from the YNAB OpenAPI spec, version ${OLD_VERSION:-unknown} -> ${NEW_VERSION:-unknown} (produced by scripts/generate.sh). + +Do the following, and nothing else: +1. Inspect the diff, focusing on open_api_spec.yaml and docs/ for FUNCTIONAL API changes (new or changed fields, endpoints, enums, response codes). Ignore the mechanical per-file header/version churn under ynab/. +2. Commit ALL changes. The subject should note the spec regeneration and version bump (${OLD_VERSION:-unknown} -> ${NEW_VERSION:-unknown}); the body should summarize the functional changes (or state it is a routine refresh if there are none). +3. Push and open a PR against main with a clear title and description. Do NOT request any reviewers. +4. Print the PR URL on the final line. + +Do not modify any generated code — only commit and open the PR." + +claude -p "$PROMPT" --allowedTools $ALLOWED_TOOLS + +echo +echo "Done." From bea97ae47d5aef4feda8fdea5b4bcf6cee96ba81 Mon Sep 17 00:00:00 2001 From: Brady Holt Date: Wed, 15 Jul 2026 10:58:29 -0500 Subject: [PATCH 3/4] Document generate-and-pr.sh in DEVELOPMENT.md Adds the automated PR workflow as an alternative to the manual generate.sh + open-PR steps. --- DEVELOPMENT.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index 1b4ea77..188db14 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -11,6 +11,8 @@ 1. Run `scripts/generate.sh`. This will generate the API client from the latest OpenAPI spec. Once generated, you should open a PR and merge the changes. +Alternatively, run `scripts/generate-and-pr.sh` to do the above and automate the PR. It wraps `generate.sh`, detects the old → new spec version, and (after you confirm) ensures you're on a `gen-` branch, then hands the commit and PR off to the [`claude`](https://docs.claude.com/en/docs/claude-code/overview) CLI, which commits the changes, opens a PR against `main` summarizing the functional spec changes, and prints the PR URL. Requires the `claude` CLI to be installed. + ## Publishing Run the "Publish" GitHub Actions workflow. \ No newline at end of file From 44820bc1f6958b9c0adc1cb7d4490ac4ea4215d3 Mon Sep 17 00:00:00 2001 From: Brady Holt Date: Wed, 15 Jul 2026 11:05:08 -0500 Subject: [PATCH 4/4] Limit LLM use in generate-and-pr.sh to the PR description Bash now handles the commit, branch, push, and PR creation via git/gh; claude is invoked only to draft the PR body from the spec diff. --- DEVELOPMENT.md | 2 +- scripts/generate-and-pr.sh | 51 +++++++++++++++++++++++++------------- 2 files changed, 35 insertions(+), 18 deletions(-) diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index 188db14..70c2ad9 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -11,7 +11,7 @@ 1. Run `scripts/generate.sh`. This will generate the API client from the latest OpenAPI spec. Once generated, you should open a PR and merge the changes. -Alternatively, run `scripts/generate-and-pr.sh` to do the above and automate the PR. It wraps `generate.sh`, detects the old → new spec version, and (after you confirm) ensures you're on a `gen-` branch, then hands the commit and PR off to the [`claude`](https://docs.claude.com/en/docs/claude-code/overview) CLI, which commits the changes, opens a PR against `main` summarizing the functional spec changes, and prints the PR URL. Requires the `claude` CLI to be installed. +Alternatively, run `scripts/generate-and-pr.sh` to do the above and automate the PR. It wraps `generate.sh`, detects the old → new spec version, and (after you confirm) ensures you're on a `gen-` branch, then commits, pushes, and opens a PR against `main` via `git`/`gh`, printing the PR URL. The [`claude`](https://docs.claude.com/en/docs/claude-code/overview) CLI is used only to draft the PR description from the spec diff. Requires the `gh` and `claude` CLIs to be installed and authenticated. ## Publishing diff --git a/scripts/generate-and-pr.sh b/scripts/generate-and-pr.sh index f0b0d7a..e976b62 100755 --- a/scripts/generate-and-pr.sh +++ b/scripts/generate-and-pr.sh @@ -3,9 +3,10 @@ # Regenerate the SDK from the latest YNAB API spec, then optionally open a PR. # # Wraps scripts/generate.sh. After regenerating it detects the old -> new spec -# version and, if you confirm, ensures you're on a gen- branch and -# hands the commit + PR off to `claude`, which writes a real summary of the -# functional spec changes. Requires the `claude` CLI to be installed. +# version and, if you confirm, ensures you're on a gen- branch, then +# commits, pushes, and opens a PR via git/gh. The `claude` CLI is used only to +# draft the PR description from the spec diff. Requires the `gh` and `claude` +# CLIs to be installed and authenticated. set -euo pipefail @@ -63,32 +64,48 @@ case "$BRANCH" in fi echo "On protected branch '$BRANCH'; creating and switching to '$target'." git switch -c "$target" + BRANCH="$target" ;; *) echo "Committing on current branch: '$BRANCH'." ;; esac +# Commit and push the regenerated client. +git add -A +git commit \ + -m "Regenerate SDK from server specification version ${NEW_VERSION}" \ + -m "Regenerated the client from the YNAB API spec ${NEW_VERSION} (previously ${OLD_VERSION:-unknown})." +git push -u origin "$BRANCH" + +# Use claude only to draft the PR description from the meaningful diff (the spec +# and docs; the per-file churn under ynab/ is noise). Everything else is gh/git. echo -echo "Handing off to Claude to write the commit + PR (this may take a minute)..." -echo +echo "Drafting the PR description with Claude..." +DIFF="$(git diff "origin/main...HEAD" -- open_api_spec.yaml docs/; echo; git diff --stat "origin/main...HEAD")" + +BODY_FILE="$(mktemp)" +trap 'rm -f "$BODY_FILE"' EXIT -# Scope the spawned Claude to only the tools the commit/PR flow needs so the -# non-interactive run doesn't stall on approval prompts, without granting a -# blanket permission bypass. -ALLOWED_TOOLS="Bash Read Edit Write Grep Glob Skill TodoWrite" +claude -p "Write a GitHub pull request description for a regeneration of the YNAB Python SDK from the YNAB OpenAPI spec (version ${OLD_VERSION:-unknown} -> ${NEW_VERSION}). -PROMPT="The working tree contains a regeneration of this SDK from the YNAB OpenAPI spec, version ${OLD_VERSION:-unknown} -> ${NEW_VERSION:-unknown} (produced by scripts/generate.sh). +Summarize the FUNCTIONAL API changes (new or changed fields, endpoints, enums, response codes) from the diff below, focusing on open_api_spec.yaml and docs/. If there are no functional changes, say it is a routine spec-generation refresh. Ignore the mechanical per-file header/version churn under ynab/. -Do the following, and nothing else: -1. Inspect the diff, focusing on open_api_spec.yaml and docs/ for FUNCTIONAL API changes (new or changed fields, endpoints, enums, response codes). Ignore the mechanical per-file header/version churn under ynab/. -2. Commit ALL changes. The subject should note the spec regeneration and version bump (${OLD_VERSION:-unknown} -> ${NEW_VERSION:-unknown}); the body should summarize the functional changes (or state it is a routine refresh if there are none). -3. Push and open a PR against main with a clear title and description. Do NOT request any reviewers. -4. Print the PR URL on the final line. +Output ONLY the PR description as Markdown — no preamble and no surrounding code fence. Do not use any tools. -Do not modify any generated code — only commit and open the PR." +Diff: +${DIFF}" > "$BODY_FILE" + +if [[ ! -s "$BODY_FILE" ]]; then + echo "Regenerated the client from the YNAB API spec ${NEW_VERSION} (previously ${OLD_VERSION:-unknown})." > "$BODY_FILE" +fi -claude -p "$PROMPT" --allowedTools $ALLOWED_TOOLS +# Open the PR (no reviewers). gh prints the PR URL. +gh pr create \ + --base main \ + --head "$BRANCH" \ + --title "Regenerate SDK from server specification version ${NEW_VERSION}" \ + --body-file "$BODY_FILE" echo echo "Done."