#KURE
spring wharf
Hello 👋
Not sure I completely understand the ask. I don't think we'd run into a rate limit as such as the webhook events are generated and sent asynchronously. There's no guarantee of the order of the events either. So unlikely that we'd rate limit sending the events.
full burrowBOT
dawn hollow
Hello. This is the question
If I react to 1000 subscription.update events from Stripe webhooks by making API requests for all 1000 customers simultaneously, is there a risk of hitting the API write limit? And if so, what are some best practices to avoid exceeding the rate limit in this scenario?
hearty crane
Hi there 👋 taking over, as my colleague needs to step away
Give me a few minutes to get caught up.
spring wharf
before I step away, yes if you make 1000 API requests to Stripe at the same time then in that case you could run into a rate limit issue. Ideally, you'd queue these requests on your end.
hearty crane
Yup! Also, here's the docs on rate limits in case you might find them helpful: https://stripe.com/docs/rate-limits
spring wharf
It doesn't matter when you receive the events from Stripe, but it does matter when you send the API request to our servers.
icy temple
Hey, im stepping into the conversation, Im a coworker of @dawn hollow.
Does Stripe queue webhook events when sending them?
Or do all the events get sent at once?
Lets say all subscriptions have the same billing cycle
and they are all billed at the same time
are we going to get n(subscriptiions) amount of webhooks?
hearty crane
The webhooks get sent seconds after the event occurs, so they could arrive all at once or one after the other.
are we going to get n(subscriptiions) amount of webhooks?
Yes
icy temple
Ok! thanks
hearty crane
Sure thing!