# Code 1001: user does not exist, but they do and are setup with scheduling privs

**URL:** <https://devforum.zoom.us/t/code-1001-user-does-not-exist-but-they-do-and-are-setup-with-scheduling-privs/62574>\
**Category:** API and Webhooks\
**Created:** [January 12, 2022, 5:13pm UTC](https://devforum.zoom.us/t/code-1001-user-does-not-exist-but-they-do-and-are-setup-with-scheduling-privs/62574 "2022-01-12T17:13:31Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![bk-zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bk-zoom/32/33992_2.png) [@bk-zoom](https://devforum.zoom.us/u/bk-zoom)\
**Post date:** [January 12, 2022, 5:13pm UTC](https://devforum.zoom.us/t/code-1001-user-does-not-exist-but-they-do-and-are-setup-with-scheduling-privs/62574/1 "2022-01-12T17:13:31Z")

</div>

## Using this template helps us debug your issues more effectively 🙂

**Description**  
I am trying to create a scheduled meeting with multiple alternative hosts via the users/:userid/meetings endpoint, and am getting the response code:1001 user does not exist.

I get the same error when i try to use the email address or the userID which is obtained from hitting endpoint “list users”.

I have also setup scheduling privileges on this users account.

**Error**  
{  
“code”: 1001,  
“message”: “User does not exist: [xxxxx@xxxx.com](mailto:xxxxx@xxxx.com).”  
}

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

**Which Endpoint/s?**  
users/meetings

**How To Reproduce (If applicable)**

```auto
var axios = require('axios');
var data = JSON.stringify({"topic":"test meeting","type":"2","start_time":"2022-02-01T19:00:00+00:00","duration":"30","schedule_for":"brian@bkkling.com","timezone":"US/Arizona","password":"string1","agenda":"This is the agenda text","settings":{"alternative_hosts":"x1@xxxxx.com;x2@xxxxx.com","registrants_email_notification":"true"}});

var config = {
  method: 'post',
  url: 'https://api.zoom.us/v2/users/xxxxx@xxxx.com/meetings',
  headers: { 
    'Content-Type': 'application/json', 
    'Authorization': 'Bearer xxxxxxxxxxxx', 
    'Cookie': 'cred=AAA297087F62C6A3492EB5D9F04527C1'
  },
  data : data
};

axios(config)
.then(function (response) {
  console.log(JSON.stringify(response.data));
})
.catch(function (error) {
  console.log(error);
});

```

---

<div class="post-metadata">

**Author:** ![gianni.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/gianni.zoom/32/32523_2.png) [@gianni.zoom](https://devforum.zoom.us/u/gianni.zoom)\
**Post date:** [January 13, 2022, 2:37am UTC](https://devforum.zoom.us/t/code-1001-user-does-not-exist-but-they-do-and-are-setup-with-scheduling-privs/62574/2 "2022-01-13T02:37:25Z")

</div>

Hi @bk-zoom ,

Thank you for sharing! I was not able to reproduce your error. See below:

 ![Screen Shot 2022-01-12 at 9.32.44 PM](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/0/5/051c6925ec99642efc6b3dc169be15b1447fb577.png)

Can you see the users you’re trying to set as alternative hosts under “Users” on the Admin web portal? [Sign In - Zoom](https://zoom.us/account/user#/)

Gianni

---

<div class="post-metadata">

**Author:** ![bk-zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/bk-zoom/32/33992_2.png) [@bk-zoom](https://devforum.zoom.us/u/bk-zoom)\
**Post date:** [January 13, 2022, 12:39pm UTC](https://devforum.zoom.us/t/code-1001-user-does-not-exist-but-they-do-and-are-setup-with-scheduling-privs/62574/3 "2022-01-13T12:39:50Z")

</div>

The problem is your API doc’s are unclear on using this feature…

For anyone else running into this, here is the problem and fix:

I had to remove the “schedule\_for” parameter in the payload body and now it works utilizing the path variable “:userId” and inputting userID/email passed into the URL for the end point.

```auto
{{baseUrl}}/users/:userId/meetings

```

Can you please advise proper use case for booking a meeting on behalf of another user? What is the function of “schedule\_for” in the payload body, versus the userId/email passed into the URL endpoint?

---

<div class="post-metadata">

**Author:** ![MaxM](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/maxm/32/42303_2.png) [@MaxM](https://devforum.zoom.us/u/MaxM)\
**Post date:** [January 22, 2022, 2:08am UTC](https://devforum.zoom.us/t/code-1001-user-does-not-exist-but-they-do-and-are-setup-with-scheduling-privs/62574/4 "2022-01-22T02:08:04Z")

</div>

@bk-zoom The schedule\_for field allows you to schedule the meeting on behalf of another user. It can only be used when [scheduling privileges](https://support.zoom.us/hc/en-us/articles/201362803-Scheduling-privilege) are configured.

I agree that the documentation for the [Create a Meeting API](https://marketplace.zoom.us/docs/api-reference/zoom-api/meetings/meetingcreate) could be clearer about this. I’ll work with our docs team to get this fixed.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [February 21, 2022, 12:08pm UTC](https://devforum.zoom.us/t/code-1001-user-does-not-exist-but-they-do-and-are-setup-with-scheduling-privs/62574/5 "2022-02-21T12:08:58Z")

</div>

Closed on February 21, 2022, 12:08pm UTC

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