#mrroblox_best-practices
sage tideBOT
đ 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/1229547894781116486
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
zinc marlinBOT
ebon wren
Hi there!
By "generate Stripe API token", do you mean they're creating a restricted API key?
summer nymph
Yeah, exactly
ebon wren
The way you're approaching this makes sense for retrieving historical information and keeping a record of this in your database. I recommend using webhooks once you've "caught up" so you don't have to continuously retrieve/poll
You could also immediately go to listing all invoices and filter by customer on your end: https://docs.stripe.com/api/invoices/list
summer nymph
Yeah, maybe it will save a bit time (listing all invoices), but what about webhooks
I didn't get the idea. Let's say we got a client with 1000 customers and 10 000 invoices. How webhooks will help here if this data already was created long time ago?
Do you mean we need to pull all these invoices on "customer set up" in our internal database and add new invoices only on webhook call?
ebon wren
Webhooks won't help for historical data
Yep, that's exactly what I meant. You'd list the invoices during setup/initial configuration, and rely on webhooks for any net-new invoices
ebon wren
Happy to help!