PATCH /meetings/{meetingId}/registrants/questions
Update registration questions that will be displayed to users while registering for a meeting.
Scopes: meeting:write, meeting:write:admin
Rate Limit Label: Light
Servers
- https://api.zoom.us/v2
Path parameters
| Name | Type | Required | Description |
|---|---|---|---|
meetingId |
Integer | Yes |
The meeting ID in long format. The data type of this field is "long"(represented as int64 in JSON). While storing it in your database, store it as a long data type and not as an integer, as the Meeting IDs can be longer than 10 digits. |
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
questions[] |
Array | No |
Array of Registrant Questions |
questions[].required |
Boolean | No |
Indicates whether or not the displayed fields are required to be filled out by registrants. |
questions[].field_name |
String | No |
Field name of the question. Valid values:
|
custom_questions[] |
Array | No |
Array of Registrant Custom Questions |
custom_questions[].required |
Boolean | No |
Indicates whether or not the custom question is required to be answered by participants or not. |
custom_questions[].answers[] |
Array | No |
Answer choices for the question. Can not be used for |
custom_questions[].title |
String | No |
Title of the custom question. |
custom_questions[].type |
String | No |
Type of the question being asked. Valid values:
|
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.