Registration Questions “custom_questions” limited to 50 answers

Related to topic #6905
I am getting an error when I try to Update Meeting registration Questions with a custom question that has more than 50 answers. Type of custom question is “single”.

The problem is that we were trying to automate some manual work for users so they would not have to manually type in those answers for each registration form. We spent some efforts on implementation of this task and this problem was discovered only on the final stage, because no information about this limit is present in documentation. Is this limit present only for and API endpoint ? Is there any way to overcome this problem, increase max answers for example ?


Validation Failed.

Invalid field.

PATCH /meetings/{meetingId}/registrants/questions

Hey @bportakh,

Thanks for reaching out about this—happy to look into this for you and confirm expected behavior. Can you please provide a copy of the request you’re attempting and the associated error/response? This will help me to verify.


Hi @will.zoom,

Yes, sure. Though, on the website I am able to create a meeting registration custom question that has more than 50 answers. Here is an example of request:


HTTP Method

Request Body

            "United States",
            "American Samoa",
            "Antigua and/or Barbuda",
            "Bosnia and Herzegovina",
            "Bouvet Island",
            "British lndian Ocean Territory",
            "Brunei Darussalam",
            "Burkina Faso",
            "Cape Verde",
            "Cayman Islands",
            "Central African Republic",
            "Christmas Island",
            "Cocos (Keeling) Islands",
            "Cook Islands"

Response Code
400 Bad Request

Response Body

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <message>Validation Failed.</message>
        <message>Invalid field.</message>

If I decrease answers size to 50, then I receive successful response. Same behavior is present for other meetings/webinars.

Hi @bportakh,

Thank you for providing that example and for clarifying. At the moment, you’re correct in that there are slightly different requirements for custom requirements when handled in the UI vs. the API. I’ve raised this with our team to see if this is something we might be able to bring greater parity to. (ZOOM-205648).


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