#jake

1 messages · Page 1 of 1 (latest)

robust gorge
#

Correct, 100 reads/writes per second is the standard API call rate limit

tribal tundra
#

Thanks. It was also mentioned there could be some limiting around it being 10 per minute if it's updates to subscriptions that result in a new invoice. Do you have any additional info on that? Docs make it seem like that'd happen if it was created with 'collection_method' as 'charge_automatically' since that produces an invoice but I could be misunderstanding so wanted to double check that part

#

'10 invoices/subscription/minute' was how it was detailed but that could also mean 10 invoices for a specific subscription and I'm misreading it

robust gorge
#

Do you have the doc that we mention that limit in? I was honestly not aware of taht that limit but am happy to look further in to it

tribal tundra
#

It was sent over from someone within stripe so unfortunately that snippet is all I have handy

#

Similarly we were sent '200 quantity updates/subscription/hour' as another throttle/limit point but this one won't impact our work but may help narrow down where this came from

robust gorge
#

Oh is that 200 limit specific to your account?

#

I will see what I can find on that 10 per minute limit and get back to you.

tribal tundra
#

I don't believe it is but it certainly could be

#

Thank you. Seemed really low so we just wanted to be 100% sure exactly where that one applied

robust gorge
#

Unfortunately I am still not finding much on this 10 per minute limit. Our normal doc on rate limits has all of the rate limits that I know of https://stripe.com/docs/rate-limits
If you can find the specific doc with info on this, we can look further in to it. For updating subscriptions and creating invoices though you can definitely do more than 10 per minute. Even in test mode you should be able to do a quick loop that creates 10 subscriptions as fast as it can and those calls should all succeed

Learn about API rate limits and how to work with them.