Get Meeting Archive Details
Retrieves details for a meeting archive report with a specified archive ID, which contains recording metadata.
Meeting archive details are only available to full administrators, not even the meeting host.
Request Header
timezone: Time zone in conformance with the IANA time zone database. The default is UTC iftimezoneis not defined.
URI Parameters
A unique identifier for the meeting archive summary.
Response Properties
A unique identifier for the meeting archive summary.
Recording achrive report's service-type.
Meeting title.
Start time for meeting in ISO 8601 compliant format.
End time for a meeting in ISO 8601 compliant format.
Display name for the meeting host.
Email address for the meeting host.
The participants of the meeting archive.
An internal ID that is associated with each join.
Display name for the meeting participant.
The time the participant joined the meeting.
The time the participant left the meeting.
Email address for the meeting participant.
The chats of the meeting archive.
Whether the type of the chat is private, public or group. Private chat is for the 1:1 chat. Public chat is for the message which is sent to all the people in the meeting. Group chat is for the message which is sent to a small group of people, like a message to the "host and presenter".
Display name for the sender of the chat snippet.
Chat time for the chat snippet in ISO 8601 compliant format.
Information of the receivers of the chat snippet.
The text of the chat snippet.
The polls of the meeting archive.
The type of the question.
The date and time the poll started in ISO 8601 compliant format.
The date and time the poll ended in ISO 8601 compliant format.
The content of the meeting archive poll;
The total number of questions.
The total number of users.
The number of voters among users.
Poll's questions.
The voters among users.
An internal ID that is associated with each join.
Display name for the meeting participant.
Email address for the meeting participant.
The poll's question.
The number of choices in the questions.
The type of the question.
The text of the question.
The answer summary of the archive poll.
The total number of people who selected this answer.
Whether the answer is correct.
The text of the answer.
The voters among users.
An internal ID that is associated with each join.
Display name for the meeting participant.
Email address for the meeting participant.
The question's respondents.
An internal ID that is associated with the respondent's each join.
Display name for the poll respondent.
Email address for the poll respondent.
An array of answers to the question.
Meeting meeting archive's Q and A.
The priority of the Q and A.
Whether the type of the Q and A is private, public, or group. Private Q and A is for the 1:1 chat. Public Q and A are for the message which is sent to all the people in the meeting. Group Q and A are for the message which is sent to a small group of people, like a Q and A to "host and presenter".
The email of the user who asked the question.
The date and time the question was created in ISO 8601 compliant format.
Information of the user who asked the question.
The question that was asked.
Question's answers.
The answer's response mode.
The name of the person who answered the question.
An internal ID that is associated with the answer's each join.
The email of the person who answered the question.
The date and time the question answered in ISO 8601 compliant format.
The text of the answer.
The system Information of the meeting archive, which can be only supported when serviceType is SupportCenter.
The name of the person who accessed the meeting archive.
The catalogs of system information.
System summary.
The browser user agent of the person who acted.
The type of hardware that the user used to attend the meeting.
The software that the user used to attend the meeting.
The software the user used that is running.
Startup Programs.
The storage information of the user's device.
The video of the user's device.
The network of the user's device.
The operating system of the user's device.
The environment variables of the user's device.
The processes of the user's device.
The logical drives of the user's device.
The device of the user.
The service of the user's device.
The system driver of the user's device.
The sign driver system of the user's device.
The event viewer of the user's device.
The basic input and output system.
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
{
"archiveId": "4E3254897D3A2E24E05386CA24AD93A6_R_1000637312",
"serviceType": "MeetingCenter",
"title": "Marcos Alonso's Personal Room",
"start": "2022-11-03T10:37:32+08:00",
"end": "2022-11-03T10:37:32+08:00",
"hostDisplayName": "Marcos Alonso",
"hostEmail": "marcos@example.com",
"participants": [
{
"correlationId": -25516827,
"displayName": "Marcos Alonso",
"joinedTime": "2022-11-03T10:32:09+08:00",
"leftTime": "2022-11-03T10:37:32+08:00"
},
{
"correlationId": 10947662,
"displayName": "Antoine Griezmann",
"joinedTime": "2022-11-03T10:32:09+08:00",
"leftTime": "2022-11-03T10:37:32+08:00",
"email": "linzhou@example.com"
},
{
"correlationId": -25516842,
"displayName": "Marco Reus",
"joinedTime": "2022-11-03T10:32:09+08:00",
"leftTime": "2022-11-03T10:37:32+08:00"
}
],
"chats": [
{
"type": "public",
"senderName": "Marcos Alonso",
"chatTime": "2022-11-03T10:32:48+08:00",
"target": "All Participants",
"text": "Hi everyone!"
}
],
"polls": [
{
"type": "public",
"startTime": "2022-11-03T10:33:40+08:00",
"endTime": "2022-11-03T10:37:32+08:00",
"content": {
"questionCount": 1,
"userCount": 1,
"votedUserCount": 3,
"questions": [
{
"voteUsers": [
{
"correlationId": -25516827,
"displayName": "Marcos Alonso"
},
{
"correlationId": -25516842,
"displayName": "Antoine Griezmann"
},
{
"correlationId": -25516847,
"displayName": "Marco Reus"
}
],
"question": {
"choiceCount": 3,
"type": "single answer",
"text": "Q1"
},
"answerSummary": [
{
"totalRespondents": 1,
"isCorrect": false,
"text": "1",
"voteUsers": [
{
"correlationId": -25516842,
"displayName": "Antoine Griezmann"
}
]
},
{
"totalRespondents": 2,
"isCorrect": false,
"text": "2",
"voteUsers": [
{
"correlationId": -25516827,
"displayName": "Marcos Alonso"
},
{
"correlationId": -25516847,
"displayName": "Marco Reus"
}
]
},
{
"totalRespondents": 0,
"isCorrect": true,
"text": "3"
}
],
"respondents": [
{
"correlationId": -25516827,
"displayName": "Marcos Alonso",
"answers": [
"2"
]
},
{
"correlationId": -25516842,
"displayName": "Antoine Griezmann",
"answers": [
"1"
]
},
{
"correlationId": -25516847,
"displayName": "Marco Reus",
"answers": [
"2"
]
}
]
}
]
}
}
],
"qas": [
{
"priority": "NA",
"type": "private",
"displayName": "Marcos Alonso",
"questionTime": "2022-11-03T10:32:40+08:00",
"target": "All Panelists",
"question": "What we will do next step?",
"answers": [
{
"displayName": "Marcos Alonso",
"correlationId": -25516827,
"answerTime": "2022-11-03T10:32:34+08:00",
"text": "Go home"
},
{
"displayName": "Adam Zhou",
"correlationId": 10947662,
"email": "linzhou@example.com",
"answerTime": "2022-11-03T10:34:58+08:00",
"text": "Hiking"
},
{
"displayName": "Marcos Alonso",
"correlationId": -25516827,
"answerTime": "2022-11-03T10:32:40+08:00",
"text": "Drink Some"
}
]
},
{
"type": "dismissed",
"displayName": "Marcos Alonso",
"questionTime": "2022-11-03T10:35:30+08:00",
"question": "Thank you for your question. The information that you requested cannot be provided by any of the hosts or cohosts."
}
]
}