jasonkuhrt_api

[prisma lily]

👋 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/1464287739439485093

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[idle totem]

Connected accounts will each have their separate rate limit. So your migration on the one account won't block API calls on the other connected accounts

To be clear that is specifically when using the Stripe-Account header. If you ever work with other Connect setups where calls for the connected accounts are made on the platform, those still count towards the platform limits.
But that is a different situation than your current one with this migration. So you should be safe to do this migration.

[keen siren]

Thanks, really appreciate the quick answer this, huge help.

fwiw: Feedback for docs team: The rate-limits page (https://docs.stripe.com/rate-limits) doesn't clarify that using the Stripe-Account header counts
against the connected account's limit, not the platform's.

The current wording "Connect platforms use a separate allocation to make read requests on behalf of their connected accounts" reads like the
platform has ONE allocation for all connected account requests pooled together.

Suggested clarification: "When using the Stripe-Account header, requests count against that connected account's rate limit, not your platform's
limit. Each connected account has its own 100 req/sec allocation."

This would have saved me a lot of research time. Thanks for the quick answer!

Oh @idle totem one more follow up Q then

The docs say "Write API requests have no allocation limit" - does that mean writes (like subscriptions.create) have a higher
req/sec limit than reads, or just no monthly quota? Want to know if I can safely push closer to 100 req/sec for subscription creates.

[idle totem]

I believe that is more about the monthly quota. You should be able to make however many subscription create calls that still keeps you under that 100 req/s limit