Server2Server OAuth returning: {"code":2031,"message":"Zoom Phone has not been enabled for this account."}

API and Webhooks
, ,
1

In an attempt to call Zoom API to retrieve call recordings by user, we receive the following response. I’ve attached the Request info as well.

Using the Master Admin account to create the App. We created support request, were re-directed to here. We make significant use of Zoom Phone.

Access Token: ey…_s2i67tQ
Request URL: https://api.zoom.us/v2/phone/users/user.email%40domain.com/recordings?page_size=30&from=2023-10-31&to=2023-11-30
Request Headers:
Authorization: Bearer ey…_s2i67tQ
Accept: application/json
Response Status Code: Forbidden
Response Headers:
Date: Thu, 30 Nov 2023 12:50:37 GMT
Connection: keep-alive
x-zm-trackingid: WEB_01ec514e8e4dd1d306c35d27aa66ef9f
x-zm-region: VA2
Vary: Origin, Access-Control-Request-Method, Access-Control-Request-Headers
X-Frame-Options: deny
error_message: Zoom Phone has not been enabled for this account.
Strict-Transport-Security: max-age=31536000; includeSubDomains, max-age=31536000; includeSubDomains
CF-Cache-Status: DYNAMIC
Set-Cookie: __cf_bm=8L0.oFAWa8VYul2922oWGwr.ci0Tni7Qo4gkX3XHaa0-1701348637-0-AfnKOJGoWwl+Ioys1pTK2PxCkOiYVYtE+ubU/CxrmeLk9OG81xnJOU0TPOfn5CPTUQrp2t6lB6Iv6kXdQupuWjQ=; path=/; expires=Thu, 30-Nov-23 13:20:37 GMT; domain=.zoom.us; HttpOnly; Secure
Report-To: {“endpoints”:[{“url”:“https://a.nel.cloudflare.com/report/v3?s=XukvuptR14v8Bv54ZEF4icjW2j3tnaGe2PY2UuWyWXoyaGDZRhE8%2FAMkUjWZqsgGBXnANw5IAXqSVaNeWKtGYFMvn8IkR0Ts8iVwv6enbVozqZpJppE9hpIDyKjA”}],“group”:“cf-nel”,“max_age”:604800}
NEL: {“success_fraction”:0.01,“report_to”:“cf-nel”,“max_age”:604800}
Server: cloudflare
CF-RAY: 82e3379519336991-PHL
Alt-Svc: h3=“:443”; ma=86400
Error Response Content: {“code”:2031,“message”:“Zoom Phone has not been enabled for this account.”}

2

@brenden735 have you enabled zoom phone for the user on whos behalf you are making the API calls?

3

This seems to be a common problem.

Solution: You must use the OAuth protocols found under Server to Server OAuth instructions. We had implemented standard rest API OAuth instructions.

4

Hi @brenden735 ,

Awesome to hear your issue’s fixed! For the benefit of the Zoom developer community, may I kindly request that you provide a brief summary of the steps you took to resolve the problem? Your insights would be invaluable in assisting others who might encounter a similar challenge.

5

Implemented the correct OAuth for Zoom API, see above. Issue is resolved, may close.

6

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