Yapily's knowledge article about Starling's bespoke API.
Starling implements a bespoke API and it differs from other UK banks (that more closely follow the Open Banking standard) in several fundamental ways.
This is related to the Yapily endpoint Get Transactions
transactions/valueDateTime
transactions/bookingDateTime
There is no real differentiation between a ‘booked date’ and ‘value date’ for a transaction. Starling reports two timestamps on it’s transactions:
For transactions that are still pending, only ‘Transaction Time’ is reported (as above), not the date the transaction is expected to be booked.
This is related to the Yapily endpoints:
accountBalances/type
There is no distinction between a ‘cleared balance’ and ‘booked balance’. Therefore, when reported, the following balances will always be the same value:
INTERIM_BOOKED
and INTERIM_CLEARED
OPENING_BOOKED
and OPENING_CLEARED
accountBalances/datetime
The date and time that the balance was last updated is not reported by Starling. As it is not possible for Yapily to derive this value, no ‘datetime’ is returned against the balance records.