#stefan_connect-embedded-ratelimits
loud nebulaBOT
👋 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/1295409907201478687
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
void gate
An increase of requests, additional load, won’t in any way affect our existing payment flows and trigger rate limits on main account?
Depends on your current request volume. If it's high and close to rate limits already, more requests can trigger rate limits
Correct
Only the regular rate limits apply. There isn't any different ones for this
Are you referring to the account session client secret? What do you mean by then claim it to get an api key ?
loud nebulaBOT
fringe maple
Are you referring to the account session client secret?
Yes, I've noticed that client components use account session client secret just to retrieve another different secret "api key" that is used to connect with different Stripe Apis
safe sphinx
Hi 👋
I'm stepping in as my colleague needed to go. I think you may be confusing what API keys are in this case.
https://docs.stripe.com/keys
Can you provide and example of the kind of flow you mean?
fringe maple
Thanks 🙂 I'm refering to POST /v1/account_sessions/claim action and its response, more precisely on "api_key" response field, and how it is later used, for following requests embedded component makes
safe sphinx
Ah that is an ephemeral key
It is very tightly scoped in both it's action and duration
It's only valid for a very short time
fringe maple
Thanks I wanted to double check it, as it seemed to me this is a new feature, and I wasn't sure how much it has been tested yet by real users
safe sphinx
It was actually built at the request of some of our largest Connect users, who tested extensively while it was still in Beta. That being said, it is still a new feature so I would recommend you to write in to Support if you identify features that could help make it better.
fringe maple
Depends on your current request volume. If it's high and close to rate limits already, more requests can trigger rate limits
I think I would just have to dig a bit deeper into this question, if you have any advice here it would mean a lot.
Does each user connect account have a separate rate limit?
Does the main account have a completely separate rate limit pool, and requests to different connected accounts don't influence it in any way?
As we wouldn't want to experience any limits in payment flows on main account, due to some connect accounts having too much requests
safe sphinx
I am pretty sure there are separate rate limits. But the requests to create the sessions are coming from your platform
fringe maple
I'll look into our rate limits and docs, thanks for helping us out 🙂
safe sphinx
Sure thing, happy to help 🙂