# User Does Not Exists ( Error Code 1001 ) **URL:** \ **Category:** API and Webhooks\ **Created:** [May 2, 2020, 1:34pm UTC](https://devforum.zoom.us/t/user-does-not-exists-error-code-1001/15803 "2020-05-02T13:34:03Z")\ **Posts on this page:** 1\ **Showing post:** 17
**Author:** ![rgutierrezh](https://avatars.discourse-cdn.com/v4/letter/r/b4bc9f/32.png) [@rgutierrezh](https://devforum.zoom.us/u/rgutierrezh)\ **Post date:** [July 31, 2020, 10:54pm UTC](https://devforum.zoom.us/t/user-does-not-exists-error-code-1001/15803/17 "2020-07-31T22:54:51Z")
Hey Everyone, FYI, I just got a Pro account, test the same request, and got a complete different response. BTW, with the free account, the user ID I was using to create a meeting was an active user. **UPDATE** : After swapping Free account for Pro account, I found 2 errors of mine, at least for my request: 1. The account I am using for schedule is **not an assigned scheduler** for the account I set as value for field `schedule_for`, so the response returned a status code 400: `{“code”:1110,“message”:“Not assigned scheduler.”}` Because I wasn’t trying to schedule for other account, I removed the field `schedule_for` from my request 2. After that, I got a 400 status code with this error, which is related to the `alternative_hosts` field: `{ "code": 1114, "message": "some.valid.email@mail.com is not a user in your Zoom account." }` After looking for some more information, I found that @Tommy share that there are some prerequisites for both `schedule_for` and `alternative_hosts` features here: > [@Accessing AlternativeHost/SchedulingFor feature through API](https://devforum.zoom.us/t/accessing-alternativehost-schedulingfor-feature-through-api/16416/3): > > Hey @integrationAnywhere, Please see the prerequisites for the schedule\_for and alternative\_host features here: Thanks, Tommy At the end I removed both fields from my request since I don’t need them. --- _[View the full topic](https://devforum.zoom.us/t/user-does-not-exists-error-code-1001/15803)._