#supay_docs

1 messages ยท Page 1 of 1 (latest)

cold pineBOT
#

๐Ÿ‘‹ 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/1319379822140592138

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

merry narwhalBOT
violet shadow
boreal cave
#

@violet shadow Can I disregard this then ? Users in our app could possibly update seats 5-10 times in an hours if they add users one by one

violet shadow
#

Where are you seeing that surfaced?

It is sound advice, depending on the number of Subscriptions you're planning on updating. Rate limits are measured in requests per second (rps) and livemode supports up to 100rps for POST requests. That is shared across all the endpoints for your account though.

If you're going to have a lot of Subscriptions and potentially have a lot of simultaneous updates, it's something to be wary about. If your current rps are fairly low and there's a low likelihood of your Subscription update flow leading to a spike, then it's likely less concerning.

boreal cave
#

If it's just a suggestion and not a limit, that answers my question. ๐Ÿ‘

violet shadow
#

Ah, I see it now, thank you! Yeah, it's mostly a suggestion/word of caution. It's something to be mindful of, and may be a good place in your code to have error detection so you can track whether rate limits become a problem there.

boreal cave
#

Thanks