# Fetch meeting recording

**URL:** <https://devforum.zoom.us/t/fetch-meeting-recording/95826>\
**Category:** API and Webhooks\
**Tags:** recording, api\
**Created:** [September 26, 2023, 3:15pm UTC](https://devforum.zoom.us/t/fetch-meeting-recording/95826 "2023-09-26T15:15:24Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![trechtoapp](https://avatars.discourse-cdn.com/v4/letter/t/8dc957/32.png) [@trechtoapp](https://devforum.zoom.us/u/trechtoapp)\
**Post date:** [September 26, 2023, 3:15pm UTC](https://devforum.zoom.us/t/fetch-meeting-recording/95826/1 "2023-09-26T15:15:24Z")

</div>

I was used JWT previously to fetch meeting recording.  
And recently i migrated my app from jwt to outh. All working good.  
I am facing problem while fething meeting recording.  
So following is my old PHP code

public function meeting\_recording(){  
header(“Content-Type: application/json; charset=UTF-8”);  
$params = json\_decode(file\_get\_contents(‘php://input’), TRUE);  
$meeting\_id = $params[‘meeting\_id’];  
$request\_url = “[https://api.zoom.us/v2/meetings/“.$meeting\_id.”/recordings](https://api.zoom.us/v2/meetings/%22.$meeting_id.%22/recordings)”;  
$token = array(  
“iss” =\> API\_KEY,  
“exp” =\> time() + 3600  
);  
$getJWTKey = JWT::encode($token, API\_SECRET);  
$headers = array(  
"authorization: Bearer " . $getJWTKey,  
“content-type: application/json”,  
“Accept: application/json”,  
);

```
    $ch = curl_init();
    curl_setopt_array($ch, array(
        CURLOPT_URL => $request_url,
        CURLOPT_RETURNTRANSFER => true,
        CURLOPT_ENCODING => "",
        CURLOPT_MAXREDIRS => 10,
        CURLOPT_TIMEOUT => 30,
        CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
        CURLOPT_CUSTOMREQUEST => "GET",
        CURLOPT_HTTPHEADER => $headers,
    ));

    $result = curl_exec($ch);
    $err = curl_error($ch);
    curl_close($ch);
    if (!$result)
    {
        return $err;
    }
    // echo $result;
     $result = json_decode($result);
    foreach($result->recording_files as $key=>$value){
        $result->recording_files[$key]->password = $result->password;
        $result->recording_files[$key]->title = $result->topic;
    }
    
    if($result)
    {
        // $result->meeting_details= $this->db->get_where('live_class',array('meeting_id'=>$params['meeting_id']))->row();
        $data["response"] = true;
        $data["data"] = $result;
        
    }else{
        $data["response"] = false;
	    $data["message"] = 'Data Not Available';
    }
     echo json_encode($data);
}

```

One more thing, i used this api for attendee(student) side.  
So can you please suggest what should i do for fetching recording from oauth app

---

<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:** [October 2, 2023, 2:36pm UTC](https://devforum.zoom.us/t/fetch-meeting-recording/95826/2 "2023-10-02T14:36:20Z")

</div>

Hi @trechtoapp  
Thanks for reaching out to us!  
Are you still having this issue? If so, could you please explain what the issue is?

---

<div class="post-metadata">

**Author:** ![trechtoapp](https://avatars.discourse-cdn.com/v4/letter/t/8dc957/32.png) [@trechtoapp](https://devforum.zoom.us/u/trechtoapp)\
**Post date:** [October 3, 2023, 5:22am UTC](https://devforum.zoom.us/t/fetch-meeting-recording/95826/3 "2023-10-03T05:22:22Z")

</div>

Look @elisa.zoom  
I successfully integrated Oauth in my app  
creating meetings and recording meetings are working fine.  
but in my app, I give access of recording to my student using above API with jwt token.  
I fetched the recording and displayed it on the students’ side.  
But here in the Oauth app type How can i do?

is it possible?, if student grant app using there own zoom account and creates token and fetch meetings from my account?  
if yes then i will proceed accordingly. If no then please guide me.  
Thank You.

---

<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:** [October 3, 2023, 12:47pm UTC](https://devforum.zoom.us/t/fetch-meeting-recording/95826/4 "2023-10-03T12:47:53Z")

</div>

Hi @trechtoapp  
Thanks for the clarification  
Unfortunately, this is not possible using an OAuth app type.  
If your student authorizes the app using their own zoom account and creates an access token, they will only be able to fetch meetings and recordings from their own account.  
The access token is associated with the owner of the account.

---

<div class="post-metadata">

**Author:** ![trechtoapp](https://avatars.discourse-cdn.com/v4/letter/t/8dc957/32.png) [@trechtoapp](https://devforum.zoom.us/u/trechtoapp)\
**Post date:** [October 4, 2023, 10:37am UTC](https://devforum.zoom.us/t/fetch-meeting-recording/95826/5 "2023-10-04T10:37:41Z")

</div>

So if i want to show meeting recordings to the student side then what will be the solution?  
How can i fetch recordings using api and show it on student side?

---

<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:** [October 4, 2023, 4:14pm UTC](https://devforum.zoom.us/t/fetch-meeting-recording/95826/6 "2023-10-04T16:14:37Z")

</div>

Students won’t be able to see your recordings unless you download them and share the recordings with them.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [October 6, 2023, 7:39pm UTC](https://devforum.zoom.us/t/fetch-meeting-recording/95826/7 "2023-10-06T19:39:55Z")

</div>

Closed on October 6, 2023, 7:39pm UTC

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.
