Recording completed event gives wrong caption (CC) download URL

API and Webhooks
#1

Description
I am trying to download MP4 and CC files that are given in the “All Recordings Completed” event.

The MP4 download URL looks like this:
https://zoom.us/rec/webhook_download/vs[REDACTED]Fi/98[REDACTED]hg

The CC download URL looks like this:
https://zoom.us/rec/play/vtt?fid=vs[REDACTED]Fi&type=cc/98[REDACTED]hg

Notice, the CC download URL has the extra “/98[REDACTED]hg” at the end of the URL when it shouldn’t be there. This makes the query parameter “type=cc/98[REDACTED]hg” when it should just be “type=cc.”

Error
This CC URL returns a 200 HTTP response code, but gives no data. Removing “/98[REDACTED]hg” from the URL returns the correct CC file.

Also, after cleaning up the URL, I can download it in a browser while logged in, but when I try to use that URL with the authorization header, it still returns a 200 HTTP response code with no data.

Which App Type (OAuth / Chatbot / JWT / Webhook)?
OAuth Event Subscription

#2

Hey @e399,

Thanks for your bug report. We will investigate this and get back to you. :slight_smile: (ZOOM-164861)

-Tommy

#3

Hey @e399,

In order for us to investigate further, we need the full recording url. Can you please email it and a link to this thread to developersupport@zoom.us ?

Thanks,
Tommy

#4

Hey @e399,

Are you still having this issue?

Thanks,
Tommy

#5

Yes, I’m still having this issue. I have exchanged several emails with support and the issue was escalated last I heard (July 9).

I was planning on asking if there were updates today, so this is good timing on your part.

#6

Hey @e399,

Can you share another sample closed caption url with this issue? Feel free to share it here if it is just a test meeting. (ZOOM-164861)

Thanks,
Tommy

#7

I made a new recording and emailed the bad CC download link in the existing email chain (I do not want to share it here).

1 Like
#8

Thanks @e399, we will get to you shortly.

-Tommy

#9

This is still an issue, any updates @tommy?

#10

Hi @e399,

Our team is still working on this—I’ve just followed up with them and hope to have an update for you shortly.

Thanks,
Will

#11

Hey @e399,

We have found the bug, and are working to fix it asap. I will update you once it is fixed. :slight_smile:

Thanks,
Tommy

#12

Hey @e399,

This is currently scheduled to be fixed in our December release. :slight_smile:

Thanks,
Tommy

1 Like
#13

Hey @e399,

This has been pushed to our January release. I will notify when it is fixed. :slight_smile:

Thanks,
Tommy

#14

Thanks for the update. Let me know if you need me to test anything.

#15

Thanks for your patience, @e399!

#16

Hey @e399,

This should be fixed sometime this month! :slight_smile:

-Tommy

#17

I can confirm, this is fixed now. Thanks for your help!

#18

Awesome, glad we could help, @e399! Thanks again for raising this with us.