# Alternative Hosts + Meeting Registration = Headache

**URL:** <https://devforum.zoom.us/t/alternative-hosts-meeting-registration-headache/83293>\
**Category:** Meetings\
**Created:** [February 16, 2023, 9:50pm UTC](https://devforum.zoom.us/t/alternative-hosts-meeting-registration-headache/83293 "2023-02-16T21:50:12Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jonathan\_Champ](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jonathan_champ/32/45_2.png) [@Jonathan\_Champ](https://devforum.zoom.us/u/Jonathan_Champ)\
**Post date:** [February 16, 2023, 9:50pm UTC](https://devforum.zoom.us/t/alternative-hosts-meeting-registration-headache/83293/1 "2023-02-16T21:50:12Z")

</div>

**API Endpoint**  
[https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/meetingCreate](https://marketplace.zoom.us/docs/api-reference/zoom-api/methods/#operation/meetingCreate)

**Description**  
Create a meeting for `user1@example.com` with `approval_type: 0` and `alternative_hosts: 'user2@example.com'`. User1 will be able to join using the `start_url`, but User2 and all other users need to join using the `join_url`. As long as User2 is already logged in to the Zoom website, that’s fine.

**Problem**  
As the meeting was created with the API, it’s likely that User2 is not logged in to the Zoom website. Thus, User2 will be asked to register for the meeting. When they provide the same email address as the `alternative_host` field, they receive an error message “Host can not register”.

**Ideas**

1. Zoom documents a URL parameter for the join URLs that sends a user through the Zoom login process. (This is my preference)
2. Zoom updates the error message to instruct the user to log in so they can join the meeting. (Please do this no matter what)
3. Zoom creates an API for getting meeting join URLs that works for both registered users and host / alternative hosts. (This would allow me to workaround the issue, but it wouldn’t be efficient)