Allow modifications to plaid transactions via API or Rule
in progress
J
JP Shipherd
By default, users cannot update imported transactions from Plaid Accounts, but there is a setting that allows them to override this behavior. When this is set it is possible to (for example) change the value of a transaction from an expense to income.
However, if the same transformation is attempted by API (and possibly by rule), this setting seems to be ignored and the API generates this response:
{'error': ['You cannot change the amount for this transaction because it was automatically imported.']}
Is it possible to make the API (and rules) check this setting before failing?
Log In
J
JP Shipherd
in progress
J
JP Shipherd
under review
J
JP Shipherd
complete
This issue is now fixed and it requests to create or update transactions associated with plaid accounts will work if the account has "Allow Modification To Transactions" enabled.
The upcoming v2 version of the API will include an
allow_transaction_modifications
property on the Plaid Accounts Object that reflects this setting.C
Chih-Wei Chang
JP Shipherd I just tried this and was getting the same error message with "allow modifications" toggled ON. Is this already available in production or we need to wait for some sort of release?
J
JP Shipherd
Chih-Wei Chang it is live now. Are you setting “plaid_account_id” in the transaction insert object?
What response are you getting?
C
Chih-Wei Chang
JP Shipherd here is the curl & response
J
JP Shipherd
Chih-Wei Chang You are right. You still can't change the "amount" attribute of an existing imported transactions via the v1 PUT /transactions API.
The recent fix DOES allow you to import new transactions to a plaid_account but does not address this. We'll move this feature request back to open.
If nothing else, we can definitely address this in the upcoming v2 API.