ynab_api_async_fork/models/
existing_transaction.rs

1/*
2 * YNAB API Endpoints
3 *
4 * Our API uses a REST based design, leverages the JSON data format, and relies upon HTTPS for transport. We respond with meaningful HTTP response codes and if an error occurs, we include error details in the response body.  API Documentation is at https://api.ynab.com
5 *
6 * The version of the OpenAPI document: 1.72.1
7 * 
8 * Generated by: https://openapi-generator.tech
9 */
10
11
12
13
14#[derive(Clone, Debug, PartialEq, Serialize, Deserialize)]
15pub struct ExistingTransaction {
16    #[serde(rename = "account_id", skip_serializing_if = "Option::is_none")]
17    pub account_id: Option<String>,
18    /// 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.
19    #[serde(rename = "date", skip_serializing_if = "Option::is_none")]
20    pub date: Option<String>,
21    /// The transaction amount in milliunits format.  Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored.
22    #[serde(rename = "amount", skip_serializing_if = "Option::is_none")]
23    pub amount: Option<i64>,
24    /// 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.
25    #[serde(rename = "payee_id", skip_serializing_if = "Option::is_none")]
26    pub payee_id: Option<String>,
27    /// 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.
28    #[serde(rename = "payee_name", skip_serializing_if = "Option::is_none")]
29    pub payee_name: Option<String>,
30    /// 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.
31    #[serde(rename = "category_id", skip_serializing_if = "Option::is_none")]
32    pub category_id: Option<String>,
33    #[serde(rename = "memo", skip_serializing_if = "Option::is_none")]
34    pub memo: Option<String>,
35    #[serde(rename = "cleared", skip_serializing_if = "Option::is_none")]
36    pub cleared: Option<crate::models::TransactionClearedStatus>,
37    /// Whether or not the transaction is approved.  If not supplied, transaction will be unapproved by default.
38    #[serde(rename = "approved", skip_serializing_if = "Option::is_none")]
39    pub approved: Option<bool>,
40    #[serde(rename = "flag_color", skip_serializing_if = "Option::is_none")]
41    pub flag_color: Option<crate::models::TransactionFlagColor>,
42    /// An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported.
43    #[serde(rename = "subtransactions", skip_serializing_if = "Option::is_none")]
44    pub subtransactions: Option<Vec<crate::models::SaveSubTransaction>>,
45}
46
47impl ExistingTransaction {
48    pub fn new() -> ExistingTransaction {
49        ExistingTransaction {
50            account_id: None,
51            date: None,
52            amount: None,
53            payee_id: None,
54            payee_name: None,
55            category_id: None,
56            memo: None,
57            cleared: None,
58            approved: None,
59            flag_color: None,
60            subtransactions: None,
61        }
62    }
63}
64
65
ynab_api_async_fork/models/existing_transaction.rs

ynab_api_async_fork/models/
existing_transaction.rs
