#and3lkar_financial-accounts-refreshrate
1 messages ยท Page 1 of 1 (latest)
๐ Welcome to your new thread!
โฒ๏ธ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
โฑ๏ธ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
๐ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1262441576395706378
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- ang3lkar_best-practices, 4 days ago, 19 messages
Hi ๐
We do not have any documented rate limit for refreshes. What frequency are you expecting?
I am trying to understand what would be the best approach to have the latest balance available. I have considered two options:
- Refresh results are available within 5-10 seconds, so every time I initiate a refresh and then just poll the results, so I can return the latest balance in the same session.
- Store refresh results in a database and schedule a background job to fetch the latest balance when window opens up again. So, I have the latest balance every time I query my database.
Any suggestions on what would be the best approach?
We don't have a recommended approach here, unfortunately. It is too dependent on each use case. I would recommend you consider how our API rate limits might impact your approach though.
Happy to help