# Web API : Zoom Phone Downloads

**URL:** <https://devforum.zoom.us/t/web-api-zoom-phone-downloads/136838>\
**Category:** API and Webhooks\
**Created:** [August 25, 2025, 3:11pm UTC](https://devforum.zoom.us/t/web-api-zoom-phone-downloads/136838 "2025-08-25T15:11:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![app.auditsystems.pro](https://avatars.discourse-cdn.com/v4/letter/a/db5fbb/32.png) [@app.auditsystems.pro](https://devforum.zoom.us/u/app.auditsystems.pro)\
**Post date:** [August 25, 2025, 3:11pm UTC](https://devforum.zoom.us/t/web-api-zoom-phone-downloads/136838/1 "2025-08-25T15:11:00Z")

</div>

### **API Endpoint(s) and/or Zoom API Event(s)**

**get** /phone/recording/download/{fileId}

**Description**  
_Our site (.net 8) attempts to download a file . This started Saturday after working for over a year. We are still able to get tokens._

**Error?**  
System.AggregateException: One or more errors occurred. (The SSL connection could not be established, see inner exception.)  
—\> System.Net.Http.HttpRequestException: The SSL connection could not be established, see inner exception.  
—\> System.Security.Authentication.AuthenticationException: Authentication failed because the remote party sent a TLS alert: ‘HandshakeFailure’.  
—\> System.ComponentModel.Win32Exception (0x80090326): The message received was unexpected or badly formatted.

**How To Reproduce**

1. In C# .Net 8 app attempt to download with recording url provided from Zoom.

```auto
using (var client = new HttpClient())
{
    var request = new HttpRequestMessage(HttpMethod.Get, recordingUrl);
    request.Headers.Authorization = new AuthenticationHeaderValue("Bearer", token);

    var response = client.SendAsync(request).Result;

```

throws the above error. We are still able to get Oauth Tokens. I can run this in different environments, but not from our production server anymore. We do currently have Tier 2 ticket for this, but wanted to explore the forum if it might helpful. I have inspected packets but I’m an amateur and only see that there is a TLS handshake error. Our Windows 2019 server has TLS1.2 and can authenticate with any other service but Zoom currently.

_2. Authentication method or app type:_ **Server-To-Server OAuth**

---

<div class="post-metadata">

**Author:** ![app.auditsystems.pro](https://avatars.discourse-cdn.com/v4/letter/a/db5fbb/32.png) [@app.auditsystems.pro](https://devforum.zoom.us/u/app.auditsystems.pro)\
**Post date:** [August 25, 2025, 4:00pm UTC](https://devforum.zoom.us/t/web-api-zoom-phone-downloads/136838/2 "2025-08-25T16:00:08Z")

</div>

Our network admin installed IIS Crypto and used best practice settings and that fixed the issue. I suspect the cipher we agreed to use during the handshake was causing issues?

packet inspection showed we offered to use AES\_128\_CBC\_SHA . But it fails during the handshake.

---

<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:** [August 26, 2025, 4:00pm UTC](https://devforum.zoom.us/t/web-api-zoom-phone-downloads/136838/3 "2025-08-26T16:00:36Z")

</div>

Closed on August 26, 2025, 4:00pm UTC

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