#frida-shtise_org-api-key-latency

1 messages · Page 1 of 1 (latest)

crystal oysterBOT
#

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

📝 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.

maiden palm
#

An example is that we're updating a connected account with individual details, and I timed the request to 14538ms with the Organization key vs 2712ms with the Secret key.
sk_org: req_Jk2lb0x0KfSWJw vs. sk_test: req_xjDoJQd7NuOYgW

cold jewel
#

Hello
Let me take a look

#

Yeah I do see higher end to end duration on the API call made by the Org API key

maiden palm
#

Is that expected..? I guess I need to know if it's not recommended to use the Org key vs the account secret key

cold jewel
#

Hmm I don't see any known issue/guidence about Org level API key taking more time for API requests. Are you seeing this consistently across all your requests OR just some specific endpoints?

maiden palm
#

I haven't timed our Stripe integration tests, but I did notice that I got more timeouts when starting to work with the Org key.
But it was especially today I noticed with the accounts calls:

  • accounts.createExternalAccount (9146ms vs 1695ms)
  • accounts.update (14538ms vs 2712ms)
  • accounts.retrieve (2264ms vs 595ms)

Do you want me to check other endpoints, like paymentIntents ?

cold jewel
#

Yeah that'd be great

maiden palm
#

Seems like paymentIntents and paymentMethods endpoints are faster

#

Example requests (with Org. key)

  • payment intents: req_O90OxqhYtKI6Ye
  • customer: req_hiAGZXUxFY9EVJ
  • payment methods: req_vtytETiZSXeHrF
cold jewel
#

Gotcha
So it's just Account object related APIs?

#

also can you share the request IDs for these?

But it was especially today I noticed with the accounts calls:
accounts.createExternalAccount (9146ms vs 1695ms)
accounts.update (14538ms vs 2712ms)
accounts.retrieve (2264ms vs 595ms)

crystal oysterBOT
maiden palm
#

Yes, sorry for the wait, I'll find them now

#
  • 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
faint shale
#

Hi 👋

I'm taking over as my colleague had to go. Thanks for providing these IDs. This will help us review what might be causing these delays.

faint shale
#
  1. Would it be possible to test one endpoint, like the createExternalAccount, with the same Account ID?
#

We want to verify how you are passing the Stripe Context as we describe it here. Can you share example Node.js code you are using to make the request with the Org key?

#

Looking at this request, it looks like you just provided the Platform ID in the stripeContext parameter.

Our docs state:

For the connected account, use a path that identifies both the platform and the connected account, following the format acct_1R3fqDP6919yCiFv/acct_1032D82eZvKYlo2C.

So for that request we would want {stripeContext: 'acct_1SdEMHCPzZMl5cfq/acct_1SuvV7Fd44ClRod2'}

#

Can you try that and provide me the request ID?

crystal oysterBOT