List Meeting Interpreters
Lists meeting interpreters for a meeting with a specified meetingId.
This operation can be used for meeting series, scheduled meeting and ended or ongoing meeting instance objects. If the specified meetingId is for a meeting series, the interpreters for the series will be listed; if the meetingId is for a scheduled meeting, the interpreters for the particular scheduled meeting will be listed; if the meetingId is for an ended or ongoing meeting instance, the interpreters for the particular meeting instance will be listed. See the Webex Meetings guide for more information about the types of meetings.
The list returned is sorted in descending order by when interpreters were created.
URI Parameters
Unique identifier for the meeting for which interpreters are being requested. The meeting can be meeting series, scheduled meeting or meeting instance which has ended or is ongoing. Please note that currently meeting ID of a scheduled personal room meeting is not supported for this API.
Query Parameters
Email address for the meeting host. This parameter is only used if the user or application calling the API has the admin on-behalf-of scopes. If set, the admin may specify the email of a user in a site they manage and the API will return interpreters of the meeting that is hosted by that user.
Response Properties
Array of meeting interpreters.
Unique identifier for meeting interpreter.
The pair of languageCode1 and languageCode2 form a bi-directional simultaneous interpretation language channel. The language codes conform with ISO 639-1.
The pair of languageCode1 and languageCode2 form a bi-directional simultaneous interpretation language channel. The language codes conform with ISO 639-1.
Email address of meeting interpreter.
Display name of meeting interpreter.
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
- Email address for the meeting host. This parameter is only used if the user or application calling the API has the admin on-behalf-of scopes. If set, the admin may specify the email of a user in a site they manage and the API will return interpreters of the meeting that is hosted by that user.
{
"items": [
{
"id": "OGQ0OGRiM2U3ZTAxNDZiMGFjYzJjMzYxNDNmNGZhN2RfZTA5MTJiZDBjNWVlNDA4YjgxMTZlMjU4Zjg2NWIzZmM",
"languageCode1": "en",
"languageCode2": "de",
"email": "marcus.hoffmann@example.com",
"displayName": "Hoffmann"
},
{
"id": "3GQ0OGRiM2U3ZTAxNDZiMGFjYzJjMzYxNDNmNGZhN2RfZTA5MAJiZDBjNWVlNDC4YjgxMTZlMjU4Zjg2NWIzZmM",
"languageCode1": "en",
"languageCode2": "fr",
"email": "antoine.martin@example.com",
"displayName": "Martin"
}
]
}