# Zoom Events Pre-register ticket eMail OTP API

**URL:** <https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966>\
**Category:** Zoom Events\
**Created:** [November 26, 2025, 4:26pm UTC](https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966 "2025-11-26T16:26:21Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![br1](https://avatars.discourse-cdn.com/v4/letter/b/91b2a8/32.png) [@br1](https://devforum.zoom.us/u/br1)\
**Post date:** [November 26, 2025, 4:26pm UTC](https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966/1 "2025-11-26T16:26:21Z")

</div>

### **API Endpoint(s)**

`POST https://api.zoom.us/v2/zoom_events/events/{{eventId}}/tickets`

* * *

### **Description**

When I add a registration via API to a ticket type that uses **Email + OTP authentication only** , the displayed authentication method is:  
**“Sign in with a Zoom account”**  
instead of  
**“Authenticate via email verification code”**.

Manually added users, however, are correctly set to **“Authenticate via email verification code”**.

* * *

### **Error?**

No technical error occurs, but the behavior is unexpected: the authentication method does not match the ticket configuration.

* * *

### **How To Reproduce**

1. **Request URL:**  
`POST https://api.zoom.us/v2/zoom_events/events/{{eventId}}/tickets`

2. **Headers:**

3. **Body (simplified example):**

4. **Authentication method / App type:**

5. **Observed behavior:**

* * *

**Question:** How can I ensure that registrants added via API use the correct authentication method (Email + OTP), just like manually added users?

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [December 1, 2025, 6:02pm UTC](https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966/2 "2025-12-01T18:02:04Z")

</div>

Hi @br1  
Thanks for reaching out to us and welcome to the Zoom Developer forum!  
I am happy to help here!  
Can you please clarify how are you creating the ticket and if you are doing this via API, can you please share the request body you are using so I can troubleshoot this on my end

---

<div class="post-metadata">

**Author:** ![br1](https://avatars.discourse-cdn.com/v4/letter/b/91b2a8/32.png) [@br1](https://devforum.zoom.us/u/br1)\
**Post date:** [December 1, 2025, 8:56pm UTC](https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966/3 "2025-12-01T20:56:33Z")

</div>

Hello @elisa.zoom

yes, i use the API to create the ticket, and this is the request body:

`{`  
` "tickets": [`  
` {`  
` "first_name": "Mario",`  
` "last_name": "Rossi",`  
` "email": "{{eMail}}",`  
` "ticket_type_id": "{{ticketTypeId}}"`  
` }`  
` ]`  
`}`

this is the request url:

POST /v2/zoom\_events/events/{{eventId}}/tickets

Thanks

---

<div class="post-metadata">

**Author:** ![JacoJazz](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jacojazz/32/72649_2.png) [@JacoJazz](https://devforum.zoom.us/u/JacoJazz)\
**Post date:** [December 4, 2025, 4:26pm UTC](https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966/4 "2025-12-04T16:26:39Z")

</div>

I’ve had exactly the same error, resulting in having to re-add a very large number of registrants again manually to be able to select Email OTP.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [December 9, 2025, 7:50pm UTC](https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966/5 "2025-12-09T19:50:35Z")

</div>

Hey @br1  
Sorry for the late reply here!  
I did not get a notification and did not see your response in the thread.  
When you created the ticket type, did you do this manually or via API? I am trying to reproduce this on my end so I would like to learn how did you create the ticket and how did you setup the ticket for email + OTP

---

<div class="post-metadata">

**Author:** ![JacoJazz](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jacojazz/32/72649_2.png) [@JacoJazz](https://devforum.zoom.us/u/JacoJazz)\
**Post date:** [December 10, 2025, 10:50am UTC](https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966/6 "2025-12-10T10:50:15Z")

</div>

Hello, on our end, the ticket type was created manually, but the ticket issued with API.

---

<div class="post-metadata">

**Author:** ![br1](https://avatars.discourse-cdn.com/v4/letter/b/91b2a8/32.png) [@br1](https://devforum.zoom.us/u/br1)\
**Post date:** [December 10, 2025, 1:34pm UTC](https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966/7 "2025-12-10T13:34:13Z")

</div>

The ticket type was created manually; pre-registration via API, thanks.

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [December 16, 2025, 8:38pm UTC](https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966/8 "2025-12-16T20:38:12Z")

</div>

Thanks @br1 and @JacoJazz  
Could any of you please share the following with me so I can escalate this:

1. Request URL (when adding registration via API to a ticket type that uses **Email + OTP authentication only** )
2. Request body
3. Tracking ID (found in the response headers)
4. Response body

---

<div class="post-metadata">

**Author:** ![JacoJazz](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jacojazz/32/72649_2.png) [@JacoJazz](https://devforum.zoom.us/u/JacoJazz)\
**Post date:** [December 17, 2025, 9:23am UTC](https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966/9 "2025-12-17T09:23:52Z")

</div>

Request URL (when adding registration via API to a ticket type that uses **Email + OTP authentication only** )

```auto
POST https://api.zoom.us/v2/zoom_events/events/7NRgtOGCQCCIdauKVPI7MA/tickets

```

Request body

```auto
{
  "registration_source": "n8n",
  "tickets": [
    {
      "email": "REDACTED",
      "ticket_type_id": "CkGM6lTXTn2HOaXQ26LsKw",
      "send_notification": true,
      "fast_join": false,
      "registration_needed": false,
      "first_name": "REDACTED",
      "last_name": "REDACTED"
    }
  ]
}

```

Tracking ID (found in the response headers)

```auto
WEB_b12f11b51ec5d3c85fc7143e35d08ad8

```

Response body

```auto
{
  "tickets": [
    {
      "ticket_id": "XE8cHplLQxKpHpa2EviF-Q",
      "event_join_link": "https://events.zoom.us/ejl/REDACTED",
      "event_registration_link": "",
      "email": "REDACTED"
    }
  ]
}

```

One question is if there’s a way I needed to set the ticket type to have the correct authentication mode, as both via API or Manually I can’t find that option?

---

<div class="post-metadata">

**Author:** ![JacoJazz](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/jacojazz/32/72649_2.png) [@JacoJazz](https://devforum.zoom.us/u/JacoJazz)\
**Post date:** [February 24, 2026, 12:41pm UTC](https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966/10 "2026-02-24T12:41:11Z")

</div>

Hello, is there any update on this issue?

---

<div class="post-metadata">

**Author:** ![elisa.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/elisa.zoom/32/47836_2.png) [@elisa.zoom](https://devforum.zoom.us/u/elisa.zoom)\
**Post date:** [March 20, 2026, 3:58pm UTC](https://devforum.zoom.us/t/zoom-events-pre-register-ticket-email-otp-api/138966/11 "2026-03-20T15:58:41Z")

</div>

Hi @JacoJazz  
I apologize for the late reply here.  
Would you be able to share a newer request and include the tracking ID so I can escalate this.  
Make sure to @tag me so I get a notification
