Versions Compared

Version Old Version 7 New Version 8
Changes made by

Michal Gregor

Michal Gregor

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

To get only the fresh transactions (i.e. those which has not been downloaded yet or newly updated ones), good approach is to use updatedFrom query parameter and store lastUpdated the maximum value of the latest downloaded transaction lastUpdated field among all downloaded transactions. Next time you should call the endpoint with stored value plus 1 millisecond.

Info

Very first download

When the bank account is connected for the first time and the initial transactions download from the bank towards Everifin is started, the most recent transactions are stored at first. Download and storing of historical ones follows afterwards. As a result, the older transactions can have more recent timestamp in field lastUpdated than the newest transactions (because these were stored bit earlier).

Therefore, if you do not want to get historical transactions, you may combine parameter like bookingDateFrom (or valueDateFrom depending on your use case) together with updatedFrom. Once there is new transaction on the account bit later after the whole initial transaction download is finished, updatedFrom parameter should be sufficient.

Only new transactions

If you do not want to get updates described above, then you can use query parameter createdFrom (ISO timestamp) and store value from field createdAt of latest transaction. Next time you should call the endpoint with stored value plus 1 millisecond.

...