In the documentation located at https://marketplace.zoom.us/docs/guides/auth/oauth the API call for oath/token is called using the code gathered from oath/authorize. However, when I take that code and all the other requirements for oath/token and make the call, the response is HTML content from the following URL:
I tried this server-side and client-side with the same response result. I tried client-side just to see if it was doing icky session checks, thus the redirect to signin.
The documentation states that a JSON result is returned on success, but it does not mention what result to expect on failure. So I expect this is some undesirable failure result. Undesirable because it would be so much more handy if, on failure, a JSON response with a reason for failure was returned!
My first thought is something off in the way I am creating the header for the call:
Resulting Base64 String:
Applied as the header:
Authorization: Basic SUZBSk5udlR6eVFfVWUxaHYzUENnOkVSUUhDeXRZSlhZV0NjSEJiMkJndVJ4VHpBUURmRmR6
Just verified the Base64 conversion here: https://www.base64encode.org/
The code changes each time I run outh/authorize. Always leads to the redirect.
HTTP redirect + HTML instead of JSON
Which App Type (OAuth / Chatbot / JWT / Webhook)?
How To Reproduce (If applicable)
Not sure in this case
Screenshots (If applicable)