changedInput schema / properties / transaction / allOf
Previous value: -[
- {
- "properties": {
- "account_id": {
- "format": "uuid",
- "type": "string"
- },
- "amount": {
- "description": "The transaction amount in milliunits format. Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored.",
- "format": "int64",
- "type": "integer"
- },
- "approved": {
- "description": "Whether or not the transaction is approved. If not supplied, transaction will be unapproved by default.",
- "type": "boolean"
- },
- "category_id": {
- "description": "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.",
- "format": "uuid",
- "type": [
- "string",
- "null"
- ]
- },
- "cleared": {
- "description": "The cleared status of the transaction",
- "enum": [
- "cleared",
- "uncleared",
- "reconciled"
- ],
- "type": "string"
- },
- "date": {
- "description": "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.",
- "format": "date",
- "type": "string"
- },
- "flag_color": {
- "description": "The transaction flag",
- "enum": [
- "red",
- "orange",
- "yellow",
- "green",
- "blue",
- "purple",
- "",
- null
- ],
- "type": [
- "string",
- "null"
- ]
- },
- "memo": {
- "maxLength": 500,
- "type": [
- "string",
- "null"
- ]
- },
- "payee_id": {
- "description": "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.",
- "format": "uuid",
- "type": [
- "string",
- "null"
- ]
- },
- "payee_name": {
- "description": "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.",
- "maxLength": 200,
- "type": [
- "string",
- "null"
- ]
- },
- "subtransactions": {
- "description": "An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported.",
- "items": {
- "properties": {
- "amount": {
- "description": "The subtransaction amount in milliunits format.",
- "format": "int64",
- "type": "integer"
- },
- "category_id": {
- "description": "The category for the subtransaction. Credit Card Payment categories are not permitted and will be ignored if supplied.",
- "format": "uuid",
- "type": [
- "string",
- "null"
- ]
- },
- "memo": {
- "maxLength": 500,
- "type": [
- "string",
- "null"
- ]
- },
- "payee_id": {
- "description": "The payee for the subtransaction.",
- "format": "uuid",
- "type": [
- "string",
- "null"
- ]
- },
- "payee_name": {
- "description": "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 on parent transaction) or (2) a payee with the same name or (3) creation of a new payee.",
- "maxLength": 200,
- "type": [
- "string",
- "null"
- ]
- }
- },
- "required": [
- "amount"
- ],
- "type": "object"
- },
- "type": "array"
- }
- },
- "type": "object"
- },
- {
- "properties": {
- "import_id": {
- "description": "If specified, a new transaction will be assigned this `import_id` and considered \"imported\". We will also attempt to match this imported transaction to an existing \"user-entered\" transaction on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).",
- "maxLength": 36,
- "type": [
- "string",
- "null"
- ]
- }
- },
- "type": "object"
- }
-]New value: +[
+ {
+ "properties": {
+ "account_id": {
+ "format": "uuid",
+ "type": "string"
+ },
+ "amount": {
+ "description": "The transaction amount in milliunits format. Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored.",
+ "format": "int64",
+ "type": "integer"
+ },
+ "approved": {
+ "description": "Whether or not the transaction is approved. If not supplied, transaction will be unapproved by default.",
+ "type": "boolean"
+ },
+ "category_id": {
+ "description": "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.",
+ "format": "uuid",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "cleared": {
+ "description": "The cleared status of the transaction",
+ "enum": [
+ "cleared",
+ "uncleared",
+ "reconciled"
+ ],
+ "type": "string"
+ },
+ "date": {
+ "description": "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.",
+ "format": "date",
+ "type": "string"
+ },
+ "flag_color": {
+ "description": "The transaction flag",
+ "enum": [
+ "red",
+ "orange",
+ "yellow",
+ "green",
+ "blue",
+ "purple",
+ "",
+ null
+ ],
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "memo": {
+ "maxLength": 500,
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "payee_id": {
+ "description": "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.",
+ "format": "uuid",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "payee_name": {
+ "description": "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.",
+ "maxLength": 200,
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "subtransactions": {
+ "description": "An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported and will return an error. Splits are not allowed on tracking accounts or on transfers between on-budget accounts; a transfer to a tracking account can be a split.",
+ "items": {
+ "properties": {
+ "amount": {
+ "description": "The subtransaction amount in milliunits format.",
+ "format": "int64",
+ "type": "integer"
+ },
+ "category_id": {
+ "description": "The category for the subtransaction. Credit Card Payment categories are not permitted and will be ignored if supplied.",
+ "format": "uuid",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "memo": {
+ "maxLength": 500,
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "payee_id": {
+ "description": "The payee for the subtransaction.",
+ "format": "uuid",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "payee_name": {
+ "description": "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 on parent transaction) or (2) a payee with the same name or (3) creation of a new payee.",
+ "maxLength": 200,
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "amount"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ },
+ {
+ "properties": {
+ "import_id": {
+ "description": "If specified, a new transaction will be assigned this `import_id` and considered \"imported\". We will also attempt to match this imported transaction to an existing \"user-entered\" transaction on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).",
+ "maxLength": 36,
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ }
+]
changedInput schema / properties / transactions / items / allOf
Previous value: -[
- {
- "properties": {
- "account_id": {
- "format": "uuid",
- "type": "string"
- },
- "amount": {
- "description": "The transaction amount in milliunits format. Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored.",
- "format": "int64",
- "type": "integer"
- },
- "approved": {
- "description": "Whether or not the transaction is approved. If not supplied, transaction will be unapproved by default.",
- "type": "boolean"
- },
- "category_id": {
- "description": "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.",
- "format": "uuid",
- "type": [
- "string",
- "null"
- ]
- },
- "cleared": {
- "description": "The cleared status of the transaction",
- "enum": [
- "cleared",
- "uncleared",
- "reconciled"
- ],
- "type": "string"
- },
- "date": {
- "description": "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.",
- "format": "date",
- "type": "string"
- },
- "flag_color": {
- "description": "The transaction flag",
- "enum": [
- "red",
- "orange",
- "yellow",
- "green",
- "blue",
- "purple",
- "",
- null
- ],
- "type": [
- "string",
- "null"
- ]
- },
- "memo": {
- "maxLength": 500,
- "type": [
- "string",
- "null"
- ]
- },
- "payee_id": {
- "description": "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.",
- "format": "uuid",
- "type": [
- "string",
- "null"
- ]
- },
- "payee_name": {
- "description": "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.",
- "maxLength": 200,
- "type": [
- "string",
- "null"
- ]
- },
- "subtransactions": {
- "description": "An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported.",
- "items": {
- "properties": {
- "amount": {
- "description": "The subtransaction amount in milliunits format.",
- "format": "int64",
- "type": "integer"
- },
- "category_id": {
- "description": "The category for the subtransaction. Credit Card Payment categories are not permitted and will be ignored if supplied.",
- "format": "uuid",
- "type": [
- "string",
- "null"
- ]
- },
- "memo": {
- "maxLength": 500,
- "type": [
- "string",
- "null"
- ]
- },
- "payee_id": {
- "description": "The payee for the subtransaction.",
- "format": "uuid",
- "type": [
- "string",
- "null"
- ]
- },
- "payee_name": {
- "description": "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 on parent transaction) or (2) a payee with the same name or (3) creation of a new payee.",
- "maxLength": 200,
- "type": [
- "string",
- "null"
- ]
- }
- },
- "required": [
- "amount"
- ],
- "type": "object"
- },
- "type": "array"
- }
- },
- "type": "object"
- },
- {
- "properties": {
- "import_id": {
- "description": "If specified, a new transaction will be assigned this `import_id` and considered \"imported\". We will also attempt to match this imported transaction to an existing \"user-entered\" transaction on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).",
- "maxLength": 36,
- "type": [
- "string",
- "null"
- ]
- }
- },
- "type": "object"
- }
-]New value: +[
+ {
+ "properties": {
+ "account_id": {
+ "format": "uuid",
+ "type": "string"
+ },
+ "amount": {
+ "description": "The transaction amount in milliunits format. Split transaction amounts cannot be changed and if a different amount is supplied it will be ignored.",
+ "format": "int64",
+ "type": "integer"
+ },
+ "approved": {
+ "description": "Whether or not the transaction is approved. If not supplied, transaction will be unapproved by default.",
+ "type": "boolean"
+ },
+ "category_id": {
+ "description": "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.",
+ "format": "uuid",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "cleared": {
+ "description": "The cleared status of the transaction",
+ "enum": [
+ "cleared",
+ "uncleared",
+ "reconciled"
+ ],
+ "type": "string"
+ },
+ "date": {
+ "description": "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.",
+ "format": "date",
+ "type": "string"
+ },
+ "flag_color": {
+ "description": "The transaction flag",
+ "enum": [
+ "red",
+ "orange",
+ "yellow",
+ "green",
+ "blue",
+ "purple",
+ "",
+ null
+ ],
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "memo": {
+ "maxLength": 500,
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "payee_id": {
+ "description": "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.",
+ "format": "uuid",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "payee_name": {
+ "description": "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.",
+ "maxLength": 200,
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "subtransactions": {
+ "description": "An array of subtransactions to configure a transaction as a split. Updating `subtransactions` on an existing split transaction is not supported and will return an error. Splits are not allowed on tracking accounts or on transfers between on-budget accounts; a transfer to a tracking account can be a split.",
+ "items": {
+ "properties": {
+ "amount": {
+ "description": "The subtransaction amount in milliunits format.",
+ "format": "int64",
+ "type": "integer"
+ },
+ "category_id": {
+ "description": "The category for the subtransaction. Credit Card Payment categories are not permitted and will be ignored if supplied.",
+ "format": "uuid",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "memo": {
+ "maxLength": 500,
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "payee_id": {
+ "description": "The payee for the subtransaction.",
+ "format": "uuid",
+ "type": [
+ "string",
+ "null"
+ ]
+ },
+ "payee_name": {
+ "description": "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 on parent transaction) or (2) a payee with the same name or (3) creation of a new payee.",
+ "maxLength": 200,
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "required": [
+ "amount"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ },
+ {
+ "properties": {
+ "import_id": {
+ "description": "If specified, a new transaction will be assigned this `import_id` and considered \"imported\". We will also attempt to match this imported transaction to an existing \"user-entered\" transaction on the same account, with the same amount, and with a date +/-10 days from the imported transaction date.<br><br>Transactions imported through File Based Import or Direct Import (not through the API) are assigned an import_id in the format: 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example, a transaction dated 2015-12-30 in the amount of -$294.23 USD would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a second transaction on the same account was imported and had the same date and same amount, its import_id would be 'YNAB:-294230:2015-12-30:2'. Using a consistent format will prevent duplicates through Direct Import and File Based Import.<br><br>If import_id is omitted or specified as null, the transaction will be treated as a \"user-entered\" transaction. As such, it will be eligible to be matched against transactions later being imported (via DI, FBI, or API).",
+ "maxLength": 36,
+ "type": [
+ "string",
+ "null"
+ ]
+ }
+ },
+ "type": "object"
+ }
+]