#nukesforbreakfast_best-practices
old crowBOT
👋 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/1424964182994059356
📝 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.
- nukesforbreakfast_docs, 6 hours ago, 4 messages
- nukesforbreakfast_invoice-payment-additional-filters, 4 days ago, 17 messages
- nukesforbreakfast_api, 4 days ago, 56 messages
- nukesforbreakfast_sub-schedule-prorations, 5 days ago, 37 messages
- nukesforbreakfast_docs, 5 days ago, 8 messages
⛔️ Stripe developers have stepped away for a short while
Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.
balmy crane
the question is noted above, thanks.
old crowBOT
void bronze
hi @balmy crane , there isn't latency differences we're aware, but you are correct that List Invoices API doesn't support "excluding" statuses.
Could you elaborate more on the following
try to minimize extra round trips to Stripe because a page might have draft invoices that get filtered out in code.
Generally when making API requests to Stripe, you'd want to be aware of the rate limiters in place: https://docs.stripe.com/rate-limits#rate-limiter
A workaroud could be you only let your customer retrieve invoices with certain statuses (like Paid or Open), which our API does support.
balmy crane
So if the client is requesting page size 10, and I go to list 10 invoices, there might be invoices that are draft so the 10 invoices returned doesn't match the client's requested size as the draft invoices get filtered out. So I should request the limit + some buffer to try and avoid the extra API call to stripe. Or, I could just always request the max of 100.
Just wondering if it's better to always ask for the max to limit the extra API calls as much as possible, or if it's better to request the limit + some buffer to allow for draft invoices to be filtered out without requesting too much extra data.
void bronze
Hmm..for users who usually need to query the Stripe API often, we encourage them to store the needed information in their own database and query their database instead to avoid running into rate limits
balmy crane
hmm
balmy crane
When it says 100 operations per second, does that mean 100 api calls per second or something else?