List Meeting Q and A
Lists questions and answers from a meeting, when ready.
Notes:
Only meeting instances in state
endedorinProgressare supported formeetingId.Long result sets will be split into pages.
This API is paginated by the sum of answers in a meeting, These pagination links are returned in the response header.
Query Parameters
A unique identifier for the meeting instance which the Q&A belongs to.
Limits the maximum number of answers in the response, up to 100.
Response Properties
An array of Q&A objects.
A unique identifier for the question.
A unique identifier for the meeting instance to which the Q&A belongs.
The total number of attendees in the meeting.
The total number of respondents in the meeting.
The name of the user who asked the question.
The email of the user who asked the question.
The question that was asked.
Question's answers.
The pagination links of the question's answers.
Link to the previous page of answers to this question.
Link to the current page of this answers to this question.
Link to the next page of answers to this question.
An array of answer objects for this question.
The name of the person who answered the question.
The email of the person who answered the question.
The ID of the person who answered the question. Only present for authenticated users.
The content of the answer.
Whether or not the question was answered.
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
- A unique identifier for the [meeting instance](/docs/meetings#meeting-series-scheduled-meetings-and-meeting-instances) which the Q&A belongs to.
- Limits the maximum number of answers in the response, up to 100.
{
"items": [
{
"id": "d513da2b-547b-4c69-b717-d83c6b02b657_M_7b789da198e531ce0c4d84243abd9fee_I_231245894851233679",
"meetingId": "7b789da198e531ce0c4d84243abd9fee_I_231245894851233679",
"totalAttendees": 7,
"totalRespondents": 1,
"displayName": "John Andersen",
"email": "john.andersen@example.com",
"question": "Are you ok?",
"answers": {
"links": {
"prev": "https://webexapis.com/v1/meetings/q_and_a/d513da2b-547b-4c69-b717-d83c6b02b657_M_7b789da198e531ce0c4d84243abd9fee_I_231245894851233679/answers?meetingId=7b789da198e531ce0c4d84243abd9fee_I_231245894851233679&offset=0&max=2",
"self": "https://webexapis.com/v1/meetings/q_and_a/d513da2b-547b-4c69-b717-d83c6b02b657_M_7b789da198e531ce0c4d84243abd9fee_I_231245894851233679/answers?meetingId=7b789da198e531ce0c4d84243abd9fee_I_231245894851233679&offset=2&max=2",
"next": "https://webexapis.com/v1/meetings/q_and_a/d513da2b-547b-4c69-b717-d83c6b02b657_M_7b789da198e531ce0c4d84243abd9fee_I_231245894851233679/answers?meetingId=7b789da198e531ce0c4d84243abd9fee_I_231245894851233679&offset=4&max=2"
},
"items": [
{
"displayName": "John Andersen",
"email": "john.andersen@example.com",
"answered": false
},
{
"displayName": "John Andersen",
"email": "john.andersen@example.com",
"personId": "Y2lzY29zcGFyazovL3VzL1BFT1BMRS8xYTY5MmE2Mi00MTNmLTRjYWEtYjdkOS0wYzg0ZDZmMDdlNzY",
"answer": "Fine, thank you.",
"answered": true
}
]
}
}
]
}