api
api copied to clipboard
Closed Savers
Is there a way to obtain the details of Savers that have closed/deleted? They appear in the transactions under relationships. However it is only the account.data.id Is there a way to get displayName and accountType into relationships?
When joining the two calls in Power BI or Parabola, I had to build my own reference table based on transactions description of Transfer to "x". X being the name of the saver.
When the saver has been closed, they no longer appear under /accounts
I'm sure others here would find that useful too.
Closed savers is certainly something that has been considered. I think the fact you're getting the account info for transactions on closed Savers is an unexpected oversight in the data coming out of the API, but perhaps the best solution is just to provide the closed Saver. There may be some nuance around this, so we'll have to have a closer look into it 👀
Wonderful! It’s the only thing I can think of at the moment that’s keeping my call ‘self contained’ without manual intervention.
Grant Alexander Twitter | Instagram | Facebook | YouTube
Writer & Photographer @ Lilithia Reviews lilithia.net | Twitter | Instagram | Facebook Reviews | Photography
On Sat, Sep 5, 2020 at 8:45 AM +1000, "Chris Corbyn" [email protected] wrote:
Closed savers is certainly something that has been considered. I think the fact you're getting the account info for transactions on closed Savers is an unexpected oversight in the data coming out of the API, but perhaps the best solution is just to provide the closed Saver. There may be some nuance around this, so we'll have to have a closer look into it 👀
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.
There hasn't been movement on this for a while. Do you have any update on a timeframe for this?
+1 know its a quality of life as we can still go off the account id but would be nice to have it rolled in
+1 on this still for me too
Sorry for the tumbleweeds on this one.
You're right that only transactions on still open accounts are visible in the API, much like in the app.
The solution here would probably be to expose a new Saver relationship on transactions. And add endpoints for returning deleted savers and their transactions.
/savers
/savers/:id/transactions
It's not planned at this stage, but can see how it'd be useful for the full history.