# OAuth server to server & recordings api

**URL:** <https://devforum.zoom.us/t/oauth-server-to-server-recordings-api/92807>\
**Category:** Authentication\
**Tags:** recording, api, s2s-oauth\
**Created:** [August 2, 2023, 11:52am UTC](https://devforum.zoom.us/t/oauth-server-to-server-recordings-api/92807 "2023-08-02T11:52:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sandor.antal](https://avatars.discourse-cdn.com/v4/letter/s/59ef9b/32.png) [@sandor.antal](https://devforum.zoom.us/u/sandor.antal)\
**Post date:** [August 2, 2023, 11:52am UTC](https://devforum.zoom.us/t/oauth-server-to-server-recordings-api/92807/1 "2023-08-02T11:52:21Z")

</div>

**Description**  
We are trying to migrate away from JWT app to the OAuth server to server app.

We are making a request to get the list of recordings we have inside of our account. In order to do so we are using the following api endpoint and also we are using an oauth token for authorization. When we make a call using the oauth token the response payload does not contain a download\_url per recording file while we have it when we make a call to the same api endpoint using a jwt token.  
We have checked the scopes on the OAuth app and the recordings scope is checked.

**Error?**  
OAuth approach returns: missing download url for recordings  
…  
“recording\_files”: [  
{  
“id”: “…0”,  
“meeting\_id”: “…=”,  
“recording\_start”: “…”,  
“recording\_end”: “…”,  
“file\_type”: “”,  
“file\_extension”: “”,  
“file\_size”: 0,  
“status”: “processing”  
}  
…

while the JWT approach returns the recordings with the download url:

“recording\_files”: [  
{  
“id”: “3…”,  
“meeting\_id”: “…==”,  
“recording\_start”: “…”,  
“recording\_end”: “…”,  
“file\_type”: “M4A”,  
“file\_extension”: “M4A”,  
“file\_size”: 3390825,  
_ **“play\_url”: “https://…zoom.us/rec/play/…”,** _  
\*\*\* “download\_url”: “https://…zoom.us/rec/download/…”,\*\*\*  
“status”: “completed”,  
“recording\_type”: “audio\_only”  
}

**How To Reproduce**  
Create an OAuth server to server app and make calls to the recordings api.

---

<div class="post-metadata">

**Author:** ![rrosas](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rrosas/32/49333_2.png) [@rrosas](https://devforum.zoom.us/u/rrosas)\
**Post date:** [August 7, 2023, 10:49pm UTC](https://devforum.zoom.us/t/oauth-server-to-server-recordings-api/92807/2 "2023-08-07T22:49:27Z")

</div>

Hello there @sandor.antal!

I had the same issue just exactly as you’ve described, for me the answer was to use the solution provided by @elisa.zoom here:

> [@The meeting recordings API stoped returning the download\_url on July 11](https://devforum.zoom.us/t/the-meeting-recordings-api-stoped-returning-the-download-url-on-july-11/92117/5):
>
> Hi @will-decker thanks for reaching out Can you please make sure that the customer affected has the view recording content permission enabled for their role. You can do this by going to the Admin Tab \> User Management \> Roles \> Role settings \> View recording content

And that was it.

Cheers.

Rodrigo RZ