I’m looking to integrate some Zoom api calls into my company’s app. Quite simply, we just want to let users who have Zoom accounts to create meetings quickly by just clicking a button within our app.
I’m going through the example OAuth2 app and it all looks good, except for one thing. When a user authorizes this for the first time, we of course send them out to https://zoom.us/oauth/authorize, with all the necessary arguments.
When they come back into our app, we want to send them back to wherever they were. To accomplish this, there’s a bunch of state that we need to restore. The
authorize endpoint seems to only send users back to a redirect_uri with the authorization code and nothing else, however. So when they come back into our app, we have no way of knowing what the user was doing before they left.
When interacting with other OAuth2 services-- including GSuite, Facebook, and so on-- we have the ability of customizing the redirect uri on a per-request basis, so that state information like this can be preserved by passing it through additional query string arguments. Is there no feature like this for Zoom API, or am I simply missing something?
Which App Type (OAuth / Chatbot / JWT / Webhook)?