Updates released: 2018-02-14 (Imported transactions and lots more)

New support for creating transactions as "imported" has been added. The new "import_id" field can be specified to transactions sent to endpoints  POST /budgets/{budget_id}/transactions and POST /budgets/{budget_id}/transactions/bulk.  The YNAB API Endpoints page has been updated to reflect the changes.  Also, here is a summary of import_id usage:

  • Specifying an import_id is completely optional
  • Duplicate checking by import_id will be performed during creation. If the import_id already exists on the same account, a new transaction will not be created
  • Upon creation, the transaction will be treated as "imported" rather than user entered. The main implication of this is that import transactions can be manually matched to user entered transactions (scheduled transactions are considered user entered). So, now, if a transaction is created with an import_id and a scheduled transaction that corresponds to this transaction is created, these two can now be manually matched.
  • import_id has been added to GET transaction endpoint responses
  • import_id cannot be updated; it can only be specified when a transaction is being created
  • The POST /budgets/{budget_id}/transactions endpoint will respond with a 400 status if a transaction has an import_id specified and it already exists on the target account. The POST /budgets/{budget_id}/transactions/bulk endpoint will now respond with an additional array of "duplicate_import_ids, import_ids specified that were not created as transactions because they already existed on the account.
Oldest first
  • Oldest first
  • Newest first
  • Active threads
  • Popular
  • 3 yrs agoLast active
  • 480Views
  • 2 Following