I’ve spent a week these past few days trying to figure out how to connect to the Zoom API to do some very simple things like create a webinar, add invite links to an existing webinar, etc. and I have to admit I’ve hit a brick wall with the obtuse API calls needed to simply connect to our data.
It seems I have to create either an S2S app, or a “normal” Zoom app, to simply get access to the necessary client ID, client secret, secret token, etc. just to request access to the API for data already stored within our Zoom account.
I’ve written hundreds of apps over the past 40+ years, but this API makes no sense to me. I’ve tried several variants via Postman, but none of them seem to work properly when I try them.
My intent is to be able to make API calls via Oracle REST Data Services (ORDS) and create webinar information from data stored within my Oracle database, but this authentication miasma is making my eyes hurt.
Are there any working examples out there that explain exactly how these parameters are supposed to be supplied to obtain authentication tokens?
Hi @andouc creating a general or S2S app is a requirement to obtain the credentials to auth and access Zoom API. Once you create the app, the credentials are generated automatically and you can use them to complete the rest of the process.
Thanks very much, Gianni! This is much more helpful than anything I’ve found so far within the documentation - I’ll have a close look and make sure I understand everything before I post any other queries.
Hi Gianni, I had the same question and watched the video you posted. One question about S2S OAuth. In the video, you mentioned it’s not necessary to activate the app and were able to retrieve an access token without doing so. But when I tried the same, I got the “invalid_client” error with the message “The application is disabled”.
I also found this doc titled “Create a Server-to-Server OAuth app” that says “You will not be able to generate an access token to make API calls unless your app is activated.”
Am I missing something or has it changed over the past months?
Hi @angus , after a while of non-use S2S apps may become deactivated, so add the missing info to reactivate your app and its credentials. Good call out!
Hi @gianni.zoom, thanks for getting back to me. I want to point out that it seems all S2S apps must be activated (therefore, some info like dev name, email, and company name must be filled) before the credentials can start working. Otherwise, you get the invalid client and app is disabled error.
I tried again just now with a new test account and app and still wasn’t able to retrieve the access token until the app was activated. Please let me know if there’s still a way to have the credentials of a newly created S2S app work with just the scopes field filled.
Hi @angus this must be new behavior as I almost never fill out that info when creating and using test S2S apps. I’ll test this later. In the interim, I’m happy completing the info re-activated the app for you to call the API.
