api
api copied to clipboard
up-banking
No Account Info for deleted Transactions
Hello, I am using the Up API to forward data to YNAB. I want to be able to keep track of pending transactions there as well so I can always have the same live balance in YNAB as I do in Up. I noticed today that if I receive a webhook event for TRANSACTION_DELETED, although I receive a transaction ID, I am unable to query for more information about that transaction from the GET /transactions/{id} endpoint as I receive a 404. Intuitively, this does make some sense... however, I am missing information on which account this transaction came from, which is necessary for me to identify the corresponding YNAB transaction and then delete it.
How can I know which account a transaction that has been deleted is/was associated with?
Thanks in advance! I'm really enjoying that you have totally changed the game in banking with this API ❤️
:+1: Good call. I believe we have enough info available to include a relationship to the account in the event payload. Happy to have a look at this one!
~I am not 100% sure... But I think I may have received a DELETED event before the CREATED event... It's hard for me to confirm, b/c it looks like the transaction ID is different, but there was no other transaction that occurred during the timespan. i.e. I only received one DELETED event, then after received one CREATED event. The transaction that was created was created in a HELD status and in the app shows as "Pending charge from 24 Apr Expired." Although it too lists it as two transactions...~ (I did get a rogue DELETED that I can't match, but I don't think it's related to the paypal transactions shown below...) ~So I'm~ Still a bit confused now...
Can you confirm that DELETED events must be received after CREATED events, or is it possible the order can get mixed?
Cheers!
Here's what it looks like in my app btw.
When I tap on either one of the PayPal entries in the list shown in the screenshot the same detail view pops up from the bottom. Here is that...
(Sorry, I realize this may deserve to be documented under a separate issue, happy to make one if you want me to).
Can you confirm that DELETED events must be received after CREATED events, or is it possible the order can get mixed?
You might get events out of sequence if the event delivery failed on the first attempt and needs to be retried.
TRANSACTION_CREATED event is attempted, fails.
TRANSACTION_DELETED event is attempted, succeeds.
TRANSACTION_CREATED event is retried, succeeds.
We don't currently have a way of holding the queue of subsequent events if any single event needs to be retried.
But aside from retries, you are correct that deletes should always follow create events.
Okay, great thanks! It's possible that I was restarting the service when a TRANSACTION_CREATED was attempted and failed. Thanks :)