Query Meeting Registrants
Meeting's host and cohost can query the list of registrants for a meeting with a specified meeting ID and registrants email.
URI Parameters
Unique identifier for the meeting. Only the ID of the meeting series is supported for meetingId. IDs of scheduled meetings, meeting instances, or scheduled personal room meetings are not supported. See the Meetings Overview for more information about meeting types.
Query Parameters
Limit the maximum number of registrants in the response, up to 100.
Whether or not to retrieve only the current scheduled meeting of the meeting series, i.e. the meeting ready to join or start or the upcoming meeting of the meeting series. If it's true, return details for the current scheduled meeting of the series, i.e. the scheduled meeting ready to join or start or the upcoming scheduled meeting of the meeting series. If it's false or not specified, return details for the entire meeting series. This parameter only applies to meeting series.
Email address for the meeting host. This parameter is only used if the user or application calling the API has the admin-level scopes. If set, the admin may specify the email of a user in a site they manage and the API will return details for a meeting that is hosted by that user.
Body Parameters
Registrant's status.
Registrant has been approved.
Registrant is in a pending list waiting for host or cohost approval.
Registrant has been rejected by the host or cohost.
Sort order for the registrants.
Registrant ordering field. Ordered by registrationTime by default.
Registrant's first name.
Registrant's last name.
Registrant's status.
registrant's email.
List of registrant email addresses.
Response Properties
Registrants array.
New registrant's ID.
New registrant's status.
Registrant has been approved.
Registrant is in a pending list waiting for host or cohost approval.
Registrant has been rejected by the host or cohost.
Registrant's first name.
Registrant's last name.
Registrant's email.
Registrant's job title.
Registrant's company.
Registrant's first address line.
Registrant's second address line.
Registrant's city name.
Registrant's state.
Registrant's postal code.
Registrant's country or region.
Registrant's work phone number.
Registrant's FAX number.
Registrant's registration time.
Registrant's answers for customized questions, Registration options define whether or not this is required.
Unique identifier for the customized questions retrieved from the registration form.
The answers for customized questions. If the question type is checkbox, more than one answer can be set.
Unique identifier for the option.
The content of the answer or the option for this question.
Registrant's source id.The sourceId is from Create Invitation Sources API.
Random ID authentication for the registrant. Webinars only. Only visible to the webinar host or cohost and only available when enabledRegistrationId is enabled for the webinar.
Response Codes
The list below describes the common success and error responses you should expect from the API:
| Code | Status | Description |
|---|---|---|
| 200 | OK | Successful request with body content. |
| 201 | Created | The request has succeeded and has led to the creation of a resource. |
| 202 | Accepted | The request has been accepted for processing. |
| 204 | No Content | Successful request without body content. |
| 400 | Bad Request | The request was invalid or cannot be otherwise served. An accompanying error message will explain further. |
| 401 | Unauthorized | Authentication credentials were missing or incorrect. |
| 403 | Forbidden | The request is understood, but it has been refused or access is not allowed. |
| 404 | Not Found | The URI requested is invalid or the resource requested, such as a user, does not exist. Also returned when the requested format is not supported by the requested method. |
| 405 | Method Not Allowed | The request was made to a resource using an HTTP request method that is not supported. |
| 409 | Conflict | The request could not be processed because it conflicts with some established rule of the system. For example, a person may not be added to a room more than once. |
| 410 | Gone | The requested resource is no longer available. |
| 415 | Unsupported Media Type | The request was made to a resource without specifying a media type or used a media type that is not supported. |
| 423 | Locked | The requested resource is temporarily unavailable. A Retry-After header may be present that specifies how many seconds you need to wait before attempting the request again. |
| 428 | Precondition Required | File(s) cannot be scanned for malware and need to be force downloaded. |
| 429 | Too Many Requests | Too many requests have been sent in a given amount of time and the request has been rate limited. A Retry-After header should be present that specifies how many seconds you need to wait before a successful request can be made. |
| 500 | Internal Server Error | Something went wrong on the server. If the issue persists, feel free to contact the Webex Developer Support team. |
| 502 | Bad Gateway | The server received an invalid response from an upstream server while processing the request. Try again later. |
| 503 | Service Unavailable | Server is overloaded with requests. Try again later. |
| 504 | Gateway Timeout | An upstream server failed to respond on time. If your query uses max parameter, please try to reduce it. |
Header
Query Parameters
- Limit the maximum number of registrants in the response, up to 100.
- Whether or not to retrieve only the current scheduled meeting of the meeting series, i.e. the meeting ready to join or start or the upcoming meeting of the meeting series. If it's `true`, return details for the current scheduled meeting of the series, i.e. the scheduled meeting ready to join or start or the upcoming scheduled meeting of the meeting series. If it's `false` or not specified, return details for the entire meeting series. This parameter only applies to meeting series.
- Email address for the meeting host. This parameter is only used if the user or application calling the API has the admin-level scopes. If set, the admin may specify the email of a user in a site they manage and the API will return details for a meeting that is hosted by that user.
Body
- Registrant's status.
- Sort order for the registrants.
- Registrant ordering field. Ordered by `registrationTime` by default.
- List of registrant email addresses.
{
"status": "pending",
"orderType": "DESC",
"orderBy": "registrationTime",
"emails": [
"bob@example.com"
]
}{
"items": [
{
"registrantId": "123456",
"status": "pending",
"firstName": "bob",
"lastName": "Lee",
"email": "bob@example.com",
"jobTitle": "manager",
"companyName": "cisco",
"address1": "address1 string",
"address2": "address2 string",
"city": "New York",
"state": "New York",
"zipCode": 123456,
"countryRegion": "United States",
"workPhone": "+1 123456",
"fax": "123456",
"registrationTime": "2021-09-07T09:29:13+08:00",
"customizedQuestions": [
{
"questionId": 330087,
"answers": [
{
"optionId": 1,
"answer": "green"
}
]
}
],
"sourceId": "cisco",
"registrationId": "566476"
}
]
}