Skip to content

Latest commit

 

History

History
41 lines (32 loc) · 3.77 KB

SaveTransactionWithIdOrImportId.md

File metadata and controls

41 lines (32 loc) · 3.77 KB

SaveTransactionWithIdOrImportId

Properties

Name Type Description Notes
account_id str [optional]
var_date date The transaction date in ISO format (e.g. 2016-12-01). Future dates (scheduled transactions) are not permitted. Split transaction dates cannot be changed and if a different date is supplied it will be ignored. [optional]
amount int The transaction amount in milliunits format. Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored. [optional]
payee_id str The payee for the transaction. To create a transfer between two accounts, use the account transfer payee pointing to the target account. Account transfer payees are specified as `transfer_payee_id` on the account resource. [optional]
payee_name str The payee name. If a `payee_name` value is provided and `payee_id` has a null value, the `payee_name` value will be used to resolve the payee by either (1) a matching payee rename rule (only if `import_id` is also specified) or (2) a payee with the same name or (3) creation of a new payee. [optional]
category_id str The category for the transaction. To configure a split transaction, you can specify null for `category_id` and provide a `subtransactions` array as part of the transaction object. If an existing transaction is a split, the `category_id` cannot be changed. Credit Card Payment categories are not permitted and will be ignored if supplied. [optional]
memo str [optional]
cleared TransactionClearedStatus [optional]
approved bool Whether or not the transaction is approved. If not supplied, transaction will be unapproved by default. [optional]
flag_color TransactionFlagColor [optional]
subtransactions List[SaveSubTransaction] An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported. [optional]
id str If specified, this id will be used to lookup a transaction by its `id` for the purpose of updating the transaction itself. If not specified, an `import_id` should be supplied. [optional]
import_id str If specified, this id will be used to lookup a transaction by its `import_id` for the purpose of updating the transaction itself. If not specified, an `id` should be supplied. You may not provide both an `id` and an `import_id` and updating an `import_id` on an existing transaction is not allowed. [optional]

Example

from ynab.models.save_transaction_with_id_or_import_id import SaveTransactionWithIdOrImportId

# TODO update the JSON string below
json = "{}"
# create an instance of SaveTransactionWithIdOrImportId from a JSON string
save_transaction_with_id_or_import_id_instance = SaveTransactionWithIdOrImportId.from_json(json)
# print the JSON string representation of the object
print(SaveTransactionWithIdOrImportId.to_json())

# convert the object into a dict
save_transaction_with_id_or_import_id_dict = save_transaction_with_id_or_import_id_instance.to_dict()
# create an instance of SaveTransactionWithIdOrImportId from a dict
save_transaction_with_id_or_import_id_from_dict = SaveTransactionWithIdOrImportId.from_dict(save_transaction_with_id_or_import_id_dict)

[Back to Model list] [Back to API list] [Back to README]