#david-thorand_api

1 messages ¡ Page 1 of 1 (latest)

hearty nicheBOT
#

👋 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. Thank you for your patience!

⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime! If this thread is closed and you have another question you'll need to start a new thread.

🔗 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/1215017401406722048

📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.

gilded fiberBOT
#

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

jaunty oak
#

Hi, we document a bit on this here: https://docs.stripe.com/rate-limits. Stripe allows up to 100 read operations per second and 100 write operations per second in live mode for most APIs. You would need to space your requests out so you do dot exeed making requests higher than this limit. However, I feel like there is a question behind the question here. Can you share if you're worried about any specifics about the rate limits?

bitter flint
#

100 per second just feels a little low. But maybe that's just due to lack of experience.

In order to work around any limits being hit, we'd implement some kind of queue as well as a retry mechanism.

Any other tips and/or best practices from your experience?

jaunty oak
#

100 per second is pretty high, not many merchants hit this as long as they follow our integration guidelines.

Yeah, in instances where you have higher than mormal traffic you can space these requests out. Also, the common trend I see is sometimes merchant make too many unnecessary GET requests to attain the level of data they need but you could leverage the Expand function for instance, https://docs.stripe.com/api/expanding_objects to avoid making more than one call to retrieve the data.

#

In cases of a sudden increase in charge volume like a flash sale might result in rate limiting and if you suspect that an upcoming event might push you over the limits listed above, you can contact our support team, https://support.stripe.com/contact.

supple owl
#

60k transactions in a hour is pretty dope tho

#

oh my bad didnt see you was upto adding such concept just saw nd read it

jaunty oak
#

@bitter flint does that help?

gilded fiberBOT