it’s just that I found there is an issue when redirect_uri uses hash
After doing the authorization process, redirected go back to my site with url pattern => https://example.com/path#zoom?code=xxxxxxx
code url params will be unreadable because it goes into the hash scope
Which App Type (OAuth / Chatbot / JWT / Webhook)?
Btw it’s working if i don’t encode the redirect_uri like this https://zoom.us/oauth/authorize?response_type=code&client_id=xxxxxxx&redirect_uri=https://example.com/path#zoom
then after doing the authorization process, redirected go back to my site with the url pattern =>
with that url pattern, then we can read the param url code:
but without encoding… this goes against the best practice of usage in url params…