#ely-delva_api

1 messages ¡ Page 1 of 1 (latest)

boreal socketBOT
#

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

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

gusty marlin
hybrid latch
#

I'm having a problem; I can't find this error in the Stripe logs (see image).

I've tried removing all filters and selecting the logs for connected accounts, but nothing works; it's as if the request doesn't exist.

I'm getting a 403 error. Could this be related or explain it?

Capture_decran_2025-08-29_a_15.47.49.png Capture_decran_2025-08-29_a_15.47.56.png
gusty marlin
#

If you have multiple accounts, it is possible that you're using the wrong API key. This error occurs when you use a key with an account that does not belong to that account, or if the connection has been revoked.

hybrid latch
#

Ok I see... And is it possible that this same API key can be used to create a connect account but not to be able to retrieve the account info? (accounts.retrieve)

#

For your information, we have just finished configuring Stripe. Could a configuration choice on the platform product be the cause of this problem?

gusty marlin
#

No, that is not possible. If you created the account with key 123, you should be able to retrieve it using key 123

#

It is possible that you envoked the connection accidentally

#

The account ids shown on the screenshots do not match

boreal socketBOT