#werey-re-o_error
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/1334516626879545345
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there!
Can you share the ID (req_xxx) of the failing API request?
https://support.stripe.com/questions/finding-the-id-for-an-api-request
This is not an api call. so it is not showing up in the dashboard. it is just a redirect to https://connect.stripe.com/oauth/v2/authorize?response_type=code&client_id=XYZ
Who is the maintainer of that oauth link?
I am not sure i get the question. I suppose I am. I am integrating in my app so i geenrate the link using the client_id from my dashboard ( in test mode )
Setting scope=read_write works correct and i can link accounts
but it is just too much access for my app scope=read_only is what is needed but the connect page fails with this error everytime i change the scope
I see what you mean, but in order to use that oauth link you need to use the read_write scope:
https://docs.stripe.com/connect/oauth-reference#:~:text=read_write or read_only%2C depending on the level of access you need. Defaults to read_only for Standard accounts. Note read_only can only be specified for extensions.
read_only is only for extensions.
Between, Extensions are depreacted and you need to use Stripe Apps instead:
https://docs.stripe.com/building-extensions
https://docs.stripe.com/stripe-apps
thanks. well noted.
So a stripe app essentially gives me read only data alone? instad of connect?
I will use that instead. Thank you!
It's a Connected based app with more granular permission checks.
That should be a good choice! Happy to help!