# Zoom Phone API Audios endpoint issues

**URL:** <https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406>\
**Category:** Phone\
**Tags:** api\
**Created:** [May 15, 2023, 2:30pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406 "2023-05-15T14:30:59Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![jesse.ser](https://avatars.discourse-cdn.com/v4/letter/j/c57346/32.png) [@jesse.ser](https://devforum.zoom.us/u/jesse.ser)\
**Post date:** [May 15, 2023, 2:30pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/1 "2023-05-15T14:30:59Z")

</div>

Hello, up until about a month ago I was able to use the following endpoint to create and upload audio assets to another user’s account.

[https://api.zoom.us/v2/phone/users/{user\_id}/audios](https://api.zoom.us/v2/phone/users/%7Buser_id%7D/audios) &  
[https://api.zoom.us/v2/phone/users/{user\_id}/audios/batch](https://api.zoom.us/v2/phone/users/%7Buser_id%7D/audios/batch)

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”  
}

What am I doing wrong?

---

<div class="post-metadata">

**Author:** ![jesse.ser](https://avatars.discourse-cdn.com/v4/letter/j/c57346/32.png) [@jesse.ser](https://devforum.zoom.us/u/jesse.ser)\
**Post date:** [May 15, 2023, 4:32pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/2 "2023-05-15T16:32:42Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [May 16, 2023, 6:28pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/4 "2023-05-16T18:28:10Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![jesse.ser](https://avatars.discourse-cdn.com/v4/letter/j/c57346/32.png) [@jesse.ser](https://devforum.zoom.us/u/jesse.ser)\
**Post date:** [May 16, 2023, 7:07pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/5 "2023-05-16T19:07:03Z")

</div>

Thanks! That is exactly correct.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [May 19, 2023, 12:18pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/6 "2023-05-19T12:18:32Z")

</div>

Thanks @jesse.ser  
I will go ahead and try to replicate this issue on my end and will also follow up with a Private Message  
Cheers,  
Elisa

---

<div class="post-metadata">

**Author:** ![jracz](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jracz/32/58489_2.png) [@jracz](https://devforum.zoom.us/u/jracz)\
**Post date:** [April 9, 2024, 3:01pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/7 "2024-04-09T15:01:03Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [April 10, 2024, 2:28am UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/8 "2024-04-10T02:28:36Z")

</div>

Hi @jracz , could you try uninstalling your app locally, re-installing and generating a new token?

To confirm, are you using an S2S app like the earlier contributor?

---

<div class="post-metadata">

**Author:** ![jracz](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jracz/32/58489_2.png) [@jracz](https://devforum.zoom.us/u/jracz)\
**Post date:** [April 10, 2024, 1:41pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/10 "2024-04-10T13:41:50Z")

</div>

Hello, @gianni.zoom yes, it is S2S. I don’t have an app installed, it is just code that is ephemeral and a new token is generated when it runs.

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [April 15, 2024, 5:07pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/11 "2024-04-15T17:07:01Z")

</div>

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
- screenshot showing added scopes

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [May 1, 2024, 10:47pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/12 "2024-05-01T22:47:18Z")

</div>

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!

---

<div class="post-metadata">

**Author:** ![jracz](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jracz/32/58489_2.png) [@jracz](https://devforum.zoom.us/u/jracz)\
**Post date:** [May 8, 2024, 1:03pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/13 "2024-05-08T13:03:28Z")

</div>

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? "

Thank you for your help!

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [May 8, 2024, 2:32pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/14 "2024-05-08T14:32:57Z")

</div>

Amazing, thank you @jracz for sharing the fix!

---

<div class="post-metadata">

**Author:** ![gpieroni](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gpieroni/32/65096_2.png) [@gpieroni](https://devforum.zoom.us/u/gpieroni)\
**Post date:** [May 2, 2025, 8:50pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/15 "2025-05-02T20:50:20Z")

</div>

Hi - I believe I’m having an identical issue, with the following endpoint:

> **[Phone APIs](https://developers.zoom.us/docs/api/phone/#tag/audio-library/POST/phone/users/%7BuserId%7D/audios)**
>
> API reference for: Phone

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.

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [May 5, 2025, 4:17pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/16 "2025-05-05T16:17:52Z")

</div>

Hi @gpieroni can you confirm that the account owner assigned that particular phone [permission](https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0064983) via the web portal?

 ![image](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/b/0/b00069c7cd7a7eeabd1459322fe9d63727c3e716.png)

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.

---

<div class="post-metadata">

**Author:** ![gpieroni](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gpieroni/32/65096_2.png) [@gpieroni](https://devforum.zoom.us/u/gpieroni)\
**Post date:** [May 5, 2025, 4:35pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/17 "2025-05-05T16:35:46Z")

</div>

Hi Gianni - thanks for taking a look at this.

Yes, I can confirm that I’m in the Admin role and Phone Management has Edit permissions.

![Screenshot 2025-05-05 123251](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/a/f/afd4efe524d7db2b1443497b9267641ae34980f8.png)

I’m also in the Phone Super Admin roll under the Phone tab, which has all the voicemail related privileges enabled, as far as I can tell.

 ![Screenshot 2025-05-05 123454](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/3/b/3bd790e99130b2c736edc7858b3de876cf4684c5.png)

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [May 5, 2025, 5:24pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/18 "2025-05-05T17:24:21Z")

</div>

Got it @gpieroni ! Thanks for confirming. In this instance, please open a [developer support ticket](https://developers.zoom.us/support/) 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:

- [link](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/15) to your post
- client id
- account id
- API endpoint, full request link and response received
- zm-tracking-id from the response header from the API request
- screenshot showing added scopes and role settings for phone super admin

---

<div class="post-metadata">

**Author:** ![gpieroni](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gpieroni/32/65096_2.png) [@gpieroni](https://devforum.zoom.us/u/gpieroni)\
**Post date:** [May 5, 2025, 6:01pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/19 "2025-05-05T18:01:29Z")

</div>

Thank you @Gianni.zoom - I opened a ticket and will report back with the results.

---

<div class="post-metadata">

**Author:** ![gpieroni](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gpieroni/32/65096_2.png) [@gpieroni](https://devforum.zoom.us/u/gpieroni)\
**Post date:** [May 28, 2025, 12:15pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/20 "2025-05-28T12:15:15Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [June 4, 2025, 7:14pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/21 "2025-06-04T19:14:56Z")

</div>

Thanks for sharing this @gpieroni , I’ll see if this has been passed along to our documentation team.

---

<div class="post-metadata">

**Author:** ![mwmatter](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mwmatter/32/73811_2.png) [@mwmatter](https://devforum.zoom.us/u/mwmatter)\
**Post date:** [March 2, 2026, 6:28pm UTC](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406/22 "2026-03-02T18:28:39Z")

</div>

Hello, discovered this post after having similar API issues with my server-to-server integration being unable to list another users audio recordings. We have audio recordings that are in our “Asset Library” made by other users that I want to be able to access and set as a default greeting for a call queue. Based on responses in this thread from others seems like my account needs some sort of special whitelisting done to allow this API endpoint? Any help is greatly appreciated.

Thanks!

[Next page](https://devforum.zoom.us/t/zoom-phone-api-audios-endpoint-issues/88406.md?page=2)
