#neha-api-latency
jolly widgetBOT
Hello! We'll be with you shortly. 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.
- neha____, 3 days ago, 24 messages
pine knoll
It's best to cache this in your database I would say
hardy abyss
i know, need to get around to that
any ideas on a workaround in the interim?
i feel like what i want (customer's revenue from inception to 3 months later) is simple but what i'm doing is hard
pine knoll
No I can't think of a workaround, you're using an API to search for information and it takes a while to complete
if I were you I'd ingest the data in my database and use that cache moving forward
hardy abyss
what about Sigma? or using a non-search API?
pine knoll
Sigma could work yes if you want to look at historical data, but you'd still get the lag of the time it takes to generate the results
neha-api-latency
pine knoll
use our List APIs and ingest the data you care about such as https://stripe.com/docs/api/customers/list or https://stripe.com/docs/api/payment_intents/list
hardy abyss
appreciate it