# Unexpected hashing algorithm used in the recording checksum

**URL:** <https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265>\
**Category:** Phone\
**Created:** [August 11, 2023, 2:44pm UTC](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265 "2023-08-11T14:44:26Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![franciscocastanheira](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/franciscocastanheira/32/50129_2.png) [@franciscocastanheira](https://devforum.zoom.us/u/franciscocastanheira)\
**Post date:** [August 11, 2023, 2:44pm UTC](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/1 "2023-08-11T14:44:26Z")

</div>

Hello Zoom Developer team!

We have a script that uses the Zoom Phone API to download recorded calls.  
We do this in Python, through the `download_url` parameter that we get in the “Get call recordings” response ([Zoom Phone API](https://developers.zoom.us/docs/api/rest/reference/phone/methods/#operation/getPhoneRecordings)).

We make the request to download the recording, and the response has some headers, one of them being ‘Zoom-File-SHA256’, which we use to ensure that the file we downloaded is not corrupted.

We had an issue being flagged for the call with `call_log_id = '96c95bae-1c69-49db-9668-c82df90cd9a4'`, where the checksum failed. We ended up realizing that, for that particular call, the hashing algorithm that was used was md5, instead of sha256, despite the checksum value being under the ‘Zoom-File-SHA256’ header.

Here is the error we logged upon finding this issue

```auto
16:39:57.872099000 [Error] [zoom_phone_call_validator.zoom_phone_api_client] Checksum is not correct. SHA256 of recording: 9a50b3842cf9bef0f8a34106f4773b238be0adbe0717efd7769179706cbdfc52. API response header checksum: aa1565d842ee87567c0301bd74a72f23.

```

Is this expected behaviour? It was the only call that we have seen this happen with.

Please let me know if you need any more information from me.

Thank you in advance.

Best Regards,  
Francisco Castanheira

---

<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:** [August 16, 2023, 3:03pm UTC](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/2 "2023-08-16T15:03:56Z")

</div>

Hi @franciscocastanheira ,

Can you please private message me with the following?

- your developer email
- application credentials used to make the request
- the full API request/response
- recordings.id and download\_url of this call

Thanks!

---

<div class="post-metadata">

**Author:** ![franciscocastanheira](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/franciscocastanheira/32/50129_2.png) [@franciscocastanheira](https://devforum.zoom.us/u/franciscocastanheira)\
**Post date:** [August 17, 2023, 7:37am UTC](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/4 "2023-08-17T07:37:13Z")

</div>

Hello Gianni,

Can you clarify what you mean with “application credentials used to make the request”?  
We are using OAuth, and therefore we have, an Account ID, Client ID, and Client Secret. But it sounds very sketchy to me to be sharing those. Am I misinterpreting something?

Also, I am not using my developer email for anything other than posting on this forum. Do you still need it?

Best,  
Francisco Castanheira

---

<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:** [August 17, 2023, 8:01pm UTC](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/5 "2023-08-17T20:01:58Z")

</div>

@franciscocastanheira , just clarified via private message. I just need the client id used to make the request. Thanks!

---

<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:** [August 27, 2023, 8:57pm UTC](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/6 "2023-08-27T20:57:41Z")

</div>

Service engineering looking into this (ZSEE-103431, ZOOM-587214).

---

<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:** [August 28, 2023, 3:54pm UTC](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/7 "2023-08-28T15:54:35Z")

</div>

Hi @franciscocastanheira ,

Upon further investigation, I learned that we use MD5 when the file needs to be uploaded in parts to the file server.

A formal request has been made to use the same checksum formula (ZOOM-587214).

Temp workaround: If the length of the token is equal to 32, please use the MD5 algorithm for verification. If the length of the token is equal to 64, please use the SHA256 algorithm for verification.

Does this help?

---

<div class="post-metadata">

**Author:** ![franciscocastanheira](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/franciscocastanheira/32/50129_2.png) [@franciscocastanheira](https://devforum.zoom.us/u/franciscocastanheira)\
**Post date:** [August 29, 2023, 7:09am UTC](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/8 "2023-08-29T07:09:00Z")

</div>

Hello Gianni,

Thank you for clarifying!

We will use the workaround for now. Can you notify me when there is a resolution for the formal request?

---

<div class="post-metadata">

**Author:** ![sjoerdwels](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/sjoerdwels/32/54764_2.png) [@sjoerdwels](https://devforum.zoom.us/u/sjoerdwels)\
**Post date:** [May 23, 2024, 9:39am UTC](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/9 "2024-05-23T09:39:23Z")

</div>

Hi @gianni.zoom,

What is the status of ZOOM-586960? Is there a way to check this our selves?

Kind regards,  
Sjoerd

---

<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 23, 2024, 9:10pm UTC](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/10 "2024-05-23T21:10:54Z")

</div>

Hey @sjoerdwels , this is an internal ticket, but I just checked in with the team to see if it’s been put on the roadmap.

---

<div class="post-metadata">

**Author:** ![trevnbec.17](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/trevnbec.17/32/19701_2.png) [@trevnbec.17](https://devforum.zoom.us/u/trevnbec.17)\
**Post date:** [June 6, 2024, 7:30pm UTC](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/11 "2024-06-06T19:30:44Z")

</div>

> [@Unexpected hashing algorithm used in the recording checksum](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/8):
>
> Hello Gianni, Thank you for clarifying! We will use the workaround for now. Can you notify me when there is a resolution for the formal request?

---

<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 6, 2024, 8:12pm UTC](https://devforum.zoom.us/t/unexpected-hashing-algorithm-used-in-the-recording-checksum/93265/12 "2024-06-06T20:12:44Z")

</div>

Still not yet on roadmap (ZOOM-587214).
