# The remote name could not be resolved: 'api.zoom.us'

**URL:** <https://devforum.zoom.us/t/the-remote-name-could-not-be-resolved-api-zoom-us/16248>\
**Category:** API and Webhooks\
**Created:** [May 5, 2020, 4:02pm UTC](https://devforum.zoom.us/t/the-remote-name-could-not-be-resolved-api-zoom-us/16248 "2020-05-05T16:02:48Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mwegner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mwegner/32/7740_2.png) [@mwegner](https://devforum.zoom.us/u/mwegner)\
**Post date:** [May 5, 2020, 4:02pm UTC](https://devforum.zoom.us/t/the-remote-name-could-not-be-resolved-api-zoom-us/16248/1 "2020-05-05T16:02:48Z")

</div>

**Description**  
API calls are no longer working in our development environment and return the error below. This was working yesterday and production environment still making calls successfully.

**Error**  
The remote name could not be resolved: ‘[api.zoom.us](http://api.zoom.us)’

**Which App Type (OAuth / Chatbot / JWT / Webhook)?**  
JWT

**Which Endpoint/s?**  
GET /users  
GET /meetings/{meetingID}  
POST /users/{userID}/meetings  
PATCH /meetings/{meetingID}

**Additional context**  
Given the timing, I’m assuming this is related to the 5/4/20 API release and the fact that our development environment is not https. Can you confirm if that is the reason for the error and if that will be the behavior going forward? Thanks for your help.

---

<div class="post-metadata">

**Author:** ![michael.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael.zoom/32/37213_2.png) [@michael.zoom](https://devforum.zoom.us/u/michael.zoom)\
**Post date:** [May 8, 2020, 6:04pm UTC](https://devforum.zoom.us/t/the-remote-name-could-not-be-resolved-api-zoom-us/16248/2 "2020-05-08T18:04:00Z")

</div>

Hi @mwegner, yes all calls to the Zoom API are required to be over HTTPS. This is the required behavior.

---

<div class="post-metadata">

**Author:** ![mwegner](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/mwegner/32/7740_2.png) [@mwegner](https://devforum.zoom.us/u/mwegner)\
**Post date:** [May 8, 2020, 7:14pm UTC](https://devforum.zoom.us/t/the-remote-name-could-not-be-resolved-api-zoom-us/16248/3 "2020-05-08T19:14:25Z")

</div>

Good afternoon Michael, thank you for the reply.

When I check our development environment now, the calls are working. Just to clarify, we do use https when specifying the endpoint ([https://api.zoom.us](https://api.zoom.us)), but do not have a certificate on our development server so the calls originate from an http connection. If https is required on both ends for all calls then we’ll need to look into alternatives for our development environment, but the behavior seems to be inconsistent and the error message doesn’t quite reflect why the call failed if our connection was in fact the reason for the error we were seeing.

---

<div class="post-metadata">

**Author:** ![tommy](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/tommy/32/72769_2.png) [@tommy](https://devforum.zoom.us/u/tommy)\
**Post date:** [May 13, 2020, 10:31pm UTC](https://devforum.zoom.us/t/the-remote-name-could-not-be-resolved-api-zoom-us/16248/4 "2020-05-13T22:31:37Z")

</div>

Hey @mwegner,

Yes, see if you can change your dev env to use https. 🙂

Thanks for the feedback, we will work on improving our error messages.

Thanks,  
Tommy

---

<div class="post-metadata">

**Author:** ![DeveloperBot](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/developerbot/32/12632_2.png) [@DeveloperBot](https://devforum.zoom.us/u/DeveloperBot)\
**Post date:** [August 21, 2020, 9:18pm UTC](https://devforum.zoom.us/t/the-remote-name-could-not-be-resolved-api-zoom-us/16248/5 "2020-08-21T21:18:38Z")

</div>

Closed on August 21, 2020, 9:18pm UTC