Regional url and api_url

API and Webhooks
1

Dear All,

Due to last Monday’s issue on Zoom [1] caused by an AWS downtime, and since we are working from an EU-provisioned account, we looked into ways to continue working with Zoom despite the AWS issue in the US. One option is to use regional URLs [2]. So, in order to get a token, we do:

POST https://api-eu.zoom.us/oauth/token

{
“access_token”: XXX,
“token_type”: “bearer”,
“expires_in”: 3599,
“scope”: “meeting:write:meeting:admin meeting:update:meeting:admin meeting:update:livestream:admin meeting:update:livestream_status:admin meeting:read:live_streaming_token:admin”,
“api_url”: “https://cern.zoom.us”
}

Since we already know we are going to work with that api_url, could we use it by default for all API interactions?

Thank you very much,
Ruben

[1] Zoom Status - Issue with Zoom Services
[2] Using Zoom APIs

2

Just to add some context (I’m a colleague of @ruben.gaspar.aparici):

The main question here is whether the /oauth/token endpoint should always be called via https://zoom.us as your documentation examples do, or if there is any benefit in also using our vanity URL or something like api-eu.

I would appreciate if this could be clarified on the Zoom side (in your docs). To me it seems odd that you’d use the generic (zoom.us or even api.zoom.us) hostname for this, when there’s also a region-specific one where it works (I tested it).

Especially during the recent (AWS us-east) outage I wonder if using our vanity host (which points to api-eu) would have avoided any API downtimes…