#shashank_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1488530373456695366
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hey there, thanks for these examples
can you also share an example test/sandbox mode request that is working?
unfortunately I do not have access to the stripe dashboard. Only our CEO has access to it. Can I provide the secret key we are using or provide link to our demo website?
Our CEO is unavailable at the moment
are those requests associated with the same account you shared? if so i can look them up
yes the requests above are associated with the same account
the requests are actually from production not from the demo
Yep, i found the sandbox on the same account and i'm looking at some account sessions requests
Yea in the sandbox it looks like you're using a secret key, not a restricted key
For example here, when you can access it: https://dashboard.stripe.com/acct_1SAr9DDSOElcPVh7/test/logs/req_XlH1bPhqwYEO9f
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
yes in the demo we are using secret key, in the production we are using a restricted key
do you recommend that we use secret key in production as well?
Give me a moment to look at this
Ok, was able to reproduce to confirm my suspicion
You (or the person to has dashboard access) needs to modify the Restricted Key permissions to give overall Connect write access, note just the individual items. These are confusingly not the same thing.
The write permission needs to be enabled for all of connect like the second image
Currently your key is configured more like the first image
We're already working on fixing this by giving explicit config options for all API endpoints, but for now you must enable this top-level Connect permission
okay thank you. We will try this. And if we run into any issues, can I reopen this thread?
You can open a new one and it will have a link back to this
okay thank you. Appreciate the help.