Hello Everyone,
I am currently integrating with the Zoom Phone API and have encountered an issue when attempting to retrieve call recordings using the following endpoint:
GET /phone/call_logs/{id}/recordings
According to the documentation, the endpoint appears to support a call log identifier. However, my testing shows different behavior depending on the identifier used.
Environment
Scopes Applied
The following scopes are configured in the application:
-
phone:read:admin
-
phone:read:call_log:admin
-
phone:read:recording:admin
-
phone:read:user:admin
-
phone:read:call_queue:admin
-
user:read:admin
-
account:read:admin
Additional Information
-
The account has a valid Zoom Phone license (Zoom Phone Pro or above).
-
The API requests are executed using an administrator account.
-
Authentication is successful and other Zoom Phone API calls are working as expected.
Test Scenarios
Scenario 1 - Using call_log_id
Request:
GET https://api.zoom.us/v2/phone/call_logs/e19301c7524447719584ac38b30a2f67/recordings
Response:
HTTP 404 Not Found
Scenario 2 - Using call_id
Request:
GET https://api.zoom.us/v2/phone/call_logs/06813ebb327a61ebb0a/recordings
Response:
HTTP 200 OK
Questions
-
Is the endpoint GET /phone/call_logs/{id}/recordings expected to work with both call_id and call_log_id?
-
If call_log_id is supported, are there any known limitations or requirements that could cause a 404 response?
-
Is the intended identifier for this endpoint actually call_id rather than call_log_id?
-
If only call_log_id is available, what is the recommended approach for retrieving the associated recording?
Since the request succeeds when using call_id, this does not appear to be a licensing, scope, or permission issue.
I would appreciate any clarification from the Zoom team regarding the expected behavior of this endpoint.
Thank you.