Now it appears that I can only use my own userid to upload or create audios.
The app was generated using Server-to-Server OAuth with the scope including all items under the Phone API.
This did work before, as I deployed about 60 users using this method, originally using your TTS, and more recently using the batch upload for audio files.
Every time I try to use anybody’s email beside mine it returns a 400 error.
This is the Json I’m passing to the request
{
“text”: “hello”,
“audio_name”: “hello5.mp3”,
“voice_language”: “en-US”,
“voice_accent”: “Joanna-Female”
}
After looking through the error logs further, it appears that I’m really getting a 403 error, saying that I do not have permission. Not sure how to set this up or why it’s letting me submit under my own email address when it’s using server-to-server oauth
Hi @jesse.ser
Thanks for reaching out to the Zoom Developer Forum and welcome to our community!
Is my understanding correct that you were able to use a token generated with a Server to Server Oauth app to create and upload audios for other users in your account and now you are getting a 403 error and you can only do that for your own account?
Hello, I have the exact same issue with the list audios endpoint. I can only like mine, I had this issue before granular scopes came out, now I’m trying with them and have the same issue.
I have made sure I have phone:read:list_audios:admin
“code”:403,“message”:“You do not have permission.”
I’m using many other aspects of the zoom API and have not run into this issue anywhere else
Can you please respond to my private message with the following information. You will see it the notification when you click on your picture and see an “envelope” icon:
client id
account id
developer email associated with app
zm-tracking-id from the response header from the API request
Hi @jracz , this is being escalated accordingly to see what the root issue is. I’ve submitted the request (TS1214869) and you should see an email about it where you can correspond with our internal support team. When a solution is found, can you please share on this thread? Thanks!
Zoom backend engineers fixed this. Below is all the info I have so far.
"back end already include your account on whitelist. Can you please try again and let is know if the issue already fix? "
Hi - I believe I’m having an identical issue, with the following endpoint:
I am also using a Server-to-Server OAuth app and code that generates a new token when it runs and confirmed the app has the phone:write:audio:admin scope
I’m able to use the endpoint against my own account but no one else’s. I get the same 403 You do not have permission error when trying to an audio to someone else’s account.
For instance, I tested by unchecking this permission for my Admin members, but saw that I was still able to add the phone:write:audio:admin scope to my app.
Make sure under Roles → Admin → Phone that the permission is assigned.
Got it @gpieroni ! Thanks for confirming. In this instance, please open a developer support ticket and link this thread explaining you have done the testing with a developer advocate on the forum and they recommended this step. Please include the following:
After some back and forth with Zoom support, they’ve enabled the whitelisting on our account and I’m able to use the API as documented.
I was told that the API documentation is wrong and should be updated, and that the whitelisting is deprecated and planned to be completely disabled/removed in the next 2 quarters, although there is a planned replacement before that happens. Don’t have any more information beyond that.
