55 and relies upon HTTPS for transport. We respond with meaningful HTTP
66 response codes and if an error occurs, we include error details in the
77 response body. API Documentation is at https://api.ynab.com
8- version : 1.81 .0
8+ version : 1.78 .0
99servers :
1010 - url : https://api.ynab.com/v1
1111security :
@@ -2586,24 +2586,24 @@ components:
25862586 type :
25872587 - string
25882588 - " null"
2589- description : " If specified, a new transaction will be assigned this `import_id`
2590- and considered \ " imported\ " . We will also attempt to match this
2591- imported transaction to an existing \ " user-entered\ " transaction
2589+ description : ' If specified, a new transaction will be assigned this `import_id`
2590+ and considered "imported". We will also attempt to match this
2591+ imported transaction to an existing "user-entered" transaction
25922592 on the same account, with the same amount, and with a date +/-10
25932593 days from the imported transaction date.<br><br>Transactions
25942594 imported through File Based Import or Direct Import (not through
25952595 the API) are assigned an import_id in the format:
2596- 'YNAB:[milliunit_amount]:[iso_date]:[occurrence]'. For example,
2596+ '' YNAB:[milliunit_amount]:[iso_date]:[occurrence]' ' . For example,
25972597 a transaction dated 2015-12-30 in the amount of -$294.23 USD
2598- would have an import_id of 'YNAB:-294230:2015-12-30:1'. If a
2598+ would have an import_id of '' YNAB:-294230:2015-12-30:1' ' . If a
25992599 second transaction on the same account was imported and had the
26002600 same date and same amount, its import_id would be
2601- 'YNAB:-294230:2015-12-30:2'. Using a consistent format will
2601+ '' YNAB:-294230:2015-12-30:2' ' . Using a consistent format will
26022602 prevent duplicates through Direct Import and File Based
26032603 Import.<br><br>If import_id is omitted or specified as null, the
2604- transaction will be treated as a \ " user-entered\ " transaction.
2604+ transaction will be treated as a "user-entered" transaction.
26052605 As such, it will be eligible to be matched against transactions
2606- later being imported (via DI, FBI, or API)."
2606+ later being imported (via DI, FBI, or API).'
26072607 SaveTransactionWithIdOrImportId :
26082608 allOf :
26092609 - type : object
@@ -2966,13 +2966,6 @@ components:
29662966 nullable : false
29672967 maxLength : 500
29682968 description : The name of the payee. The name must be a maximum of 500 characters.
2969- PostCategoryWrapper :
2970- required :
2971- - category
2972- type : object
2973- properties :
2974- category :
2975- $ref : " #/components/schemas/NewCategory"
29762969 PostCategoryGroupWrapper :
29772970 required :
29782971 - category_group
@@ -2997,6 +2990,13 @@ components:
29972990 description : The name of the category group. The name must be a maximum of 50
29982991 characters.
29992992 maxLength : 50
2993+ PostCategoryWrapper :
2994+ required :
2995+ - category
2996+ type : object
2997+ properties :
2998+ category :
2999+ $ref : " #/components/schemas/NewCategory"
30003000 PatchCategoryWrapper :
30013001 required :
30023002 - category
0 commit comments