#frida-shtise_api
storm archBOT
👋 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/1466729950643224619
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- frida-shtise_org-api-key-latency, 15 hours ago, 23 messages
- frida-shtise_webhooks, 1 day ago, 27 messages
velvet skiff
Examples:
- accounts.retrieve: req_f5GYxL3YMW5nK5
- accounts.createExternalAccount: req_924l7tnjz8LKCC
- accounts.update: req_Jk2lb0x0KfSWJw
blazing marten
👋
Could you please clarify more details about the latency you are referring too? isn't couple of seconds, couple of minutes ?
What are your expectations exactly ?
storm archBOT
velvet skiff
Hi! Sorry, I should have included that from the other thread:
accounts.createExternalAccount (9146ms vs 1695ms): req_ABCxRt8X1zQ7xo, req_zjnB3XecdWFgIV
accounts.update (14538ms vs 2712ms): req_Jk2lb0x0KfSWJw, req_xjDoJQd7NuOYgW
accounts.retrieve (2264ms vs 595ms): req_rcB4CuihNeeLdm, req_NKQNMTju43sgkf
It's seconds, and 9s vs 2s and 14s vs 3s for example, which is quite the difference
And after updating the stripeContext header, I still see the same latency unfortunately.
These are the newest requests:
accounts.retrieve: req_f5GYxL3YMW5nK5
accounts.createExternalAccount: req_924l7tnjz8LKCC
accounts.update: req_Jk2lb0x0KfSWJw
steep galleon
hey there 👋 I'm taking over as my colleague needs to step away - please give me a few minutes to get caught up 🙂
organisation API keys are a relatively new concept, so I'm investigating whether there is a known difference in regards to latency
overall though, since these requests are being completed within ~20s, this is still roughly within our 'normal' timeframes for latency
velvet skiff
I see. I guess I just need to figure out if I should move away from using the Org. key and use secret keys for the accounts instead, since it`s a huge difference between 28s vs 6s for our payout information endpoint, where we call retrieve account, update external account and update account.
steep galleon
ok yes, I can confirm that some additional latency is expected with org keys, due to some additional permissions checks
if this latency is problematic for you, you should consider using regular account API keys, where organisation-level permissions aren't required
for organisation-level actions, additional latency is expected
yes exactly, it's a trade-off so if this is impactful, you may want to prioritise using account-level keys where possible
velvet skiff
Alright, then that answers my question 🙂
steep galleon
great! we're here if you have any follow-up questions
velvet skiff
just to verify, you didn't see anything wrong with the latest requests I did? They looked correct when being called with the Org. key?
steep galleon
yes they look correct
velvet skiff
ok, thank you for the help:)
steep galleon
any time 🙌