Issue With Downloading Recording Transcripts From tenant-specific Zoom Endpoint

API and Webhooks
, ,
1

API Endpoint(s) and/or Zoom API Event(s)
[Get recordings] https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/recordingGet

Description
We’ve encountered an issue while attempting to download transcripts from a recording via the tenant-specific Zoom endpoint. While the calls to

api.zoom.us are successful, we’re experiencing failures specifically with the tenant-specific URL for downloading recording transcripts, such as:

Download URL: Tenant-specific url from the Get recordings api - https://xyz.zoom.us/rec/download/<id>

Proper authorization header (with proper scopes - recording:read) is also passed in the request which works for the API calls through api.zoom.us

The download url above is received from API endpoint defined above.

Error?
Here’s a summary of the error we’re encountering:

Received response:
StatusCode: 403
Response Body:

<?xml version=\"1.0\" encoding=\"UTF-8\"?><Error><Code>AccessDenied</Code><Message>Access denied</Message></Error>

Response headers:

{
  'Via': '1.1 446e26a256db1310ae719d818e420898.cloudfront.net (CloudFront)',
  'Connection': 'keep-alive',
  'Date': 'Mon, 13 May 2024 23:07:11 GMT',
  'X-Amz-Cf-Pop': 'SEA19-C3',
  'Content-Type': 'text/xml',
  'Server': 'CloudFront',
  'X-Amz-Cf-Id': '1euWRAaICiztbrG07oD0VKNNIy1eeKmdKu9SuA0c437zRXVfnkfNWg==',
  'X-Cache': 'Error from cloudfront',
  'Content-Length': '110'
}

How To Reproduce
Steps to reproduce the behavior:

  1. Call user recordings api to get the recordings from a specific period
    https://api.zoom.us/v2/users/me/recordings?from=1970-01-01&page_size=300&to=2024-05-14
  2. Use the download url for the transcript received from the above call and make another call to download the transcript while passing a proper authorization header.
    Authentication method - OAuth2 against a Zoom app

Do we need to whitelist any IPs on the tenant-specific Zoom configuration? We are only seeing this happening in the application code but not while invoking the same download url through a light-weight rest client e.g. Curl.

Any help is very appreciated. Thanks.

2

Hi @ukoppu , have you tried using the download_access_token supplied in the response with the url and experienced different behavior?

4

Hello,
I don’t think the download token exists in the https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/recordingsList response.
We are passing in the user authorization token when downloading the transcript which should be sufficient based on the documentation for the above api. Is there anything that we need to whitelist on the tenant side as I mentioned a similar call works when trying through Postman or any other rest client with proper auth header.

Thanks.

5

Hi @ukoppu , this is true, but the download_access_token is supplied in the original endpoint you referenced in your first message. You should be able to use either the download_access_token or the user’s OAuth access token so I would like to if that one works for you at least in the interim. Please confirm the behavior for me.

When using the OAuth token, you are sending a request like curl -H 'Authorization: Bearer <ACCESS_TOKEN>' https://{{base-domain}}/rec/archive/download/xyz?

6

Hello, yeah we are actually calling user recordings from the endpoint below that are specific to a user and we are passing the user’s oauth token as part of the request as you defined.
The /users/me/recordings endpoint doesn’t provide a download_access_token
https://developers.zoom.us/docs/api/rest/reference/zoom-api/methods/#operation/recordingsList

7

Hi @ukoppu , thanks for confirming your process. I am going to private message you for the following info so I can investigate further:

  • name and production client id of your app

  • dev email associated with credentials making API request

  • full curl request & response

Message will be in your notifications.

8

Hi @ukoppu , created a support ticket (TS1334642) – please check the email you provided to me so you can respond in the thread with support staff.

9

From support: Upon investigation, there is nothing that would block the traffic on the Zoom side. If that were the case, we would see the same result when executing through Postman or Curl which developer has confirmed works fine. Developer is encouraged to review application code.

10

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