Create an Issue
Create a new issue.
Users can create issues for themselves and admins can create issues for both themselves and on behalf of other users.
Body Parameters
The subject title for the issue.
The full description of the issue.
The initial type for the issue.
The meeting ID related to the issue.
Any custom identifier associated with the issue, such as from an external ticketing system.
Response Properties
A unique identifier for the issue.
A shorter identifier for the issue, unique only to the organization it belongs to.
The subject summary for the issue.
The full description of the issue.
The person ID of user the issue was created for.
The organization the issue belongs to.
The type for the issue, such as PROBLEM or DEFECT.
Issue type for general comments.
Issue type for reporting defects.
Issue type for feature requests.
Issue type for reporting new problems. (default)
Issue type for questions that need answers.
The status for the issue, such as NEW or CLOSED.
Status for issues sssigned to a support person.
Status for issues that were closed without resolving.
Status for issues that were escalated to another support team.
Status for open issues. (default)
Status for issues that were fixed and resolved.
The person ID of user assigned to resolve the issue.
A description of how the issue was resolved.
Date and time issue was created.
Date and time issue was last modified.
The person ID of user that last modified the issue.
The log ID submitted by webex clients when a user triggers feedback.
The meeting ID related to the issue.
The space ID created to collaborate on the issue.
Any custom identifier associated with the issue, such as from an external ticketing 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
Body
- The subject title for the issue.
- The full description of the issue.
- The initial type for the issue.
- The meeting ID related to the issue.
- Any custom identifier associated with the issue, such as from an external ticketing system.
{
"subject": "No audio during meeting from Webex client.",
"description": "I could not hear any audio during a Webex Meeting I joined from my Webex for Android client.",
"type": "PROBLEM",
"logId": "99e71be2-25a6-4628-9b77-37002fe40f47",
"meetingId": "dfb45ece33264639a7bc3dd9535d53f7_20200516T230000Z",
"externalKey": "TICKET-12345"
}{
"id": "Y2lzY29zcGFyazovL3VzL0lTU1VFLzIyNWE0YWY0LTIxYTctNDY2OC05NjhhLWI5NWU2MjlhMjBlNg",
"shortKey": 123,
"subject": "No audio during meeting from Webex client.",
"description": "I could not hear any audio during a Webex Meeting I joined from my Webex for Android client.",
"createdFor": "Y2lzY29zcGFyazovL3VzL1BFT1BMRS9mNWIzNjE4Ny1jOGRkLTQ3MjctOGIyZi1mOWM0NDdmMjkwNDY",
"orgId": "Y2lzY29zcGFyazovL3VzL09SR0FOSVpBVElPTi85NmFiYzJhYS0zZGNjLTExZTUtYTE1Mi1mZTM0ODE5Y2RjOWE",
"type": "PROBLEM",
"status": "NEW",
"assignee": "Y2lzY29zcGFyazovL3VzL1BFT1BMRS9mNWIzNjE4Ny1jOGRkLTQ3MjctOGIyZi1mOWM0NDdmMjkwNDY",
"resolution": "The end user's Bluetooth headset was not paired successfully with her Android phone. Re-paring fixed the issue.",
"created": "2019-06-01T00:00:00.000Z",
"lastModified": "2019-06-01T00:00:00.000Z",
"lastModifiedBy": "Y2lzY29zcGFyazovL3VzL1BFT1BMRS9mNWIzNjE4Ny1jOGRkLTQ3MjctOGIyZi1mOWM0NDdmMjkwNDY",
"logId": "99e71be2-25a6-4628-9b77-37002fe40f47",
"meetingId": "dfb45ece33264639a7bc3dd9535d53f7_20200516T230000Z",
"spaceId": "Y2lzY29zcGFyazovL3VzL1JPT00vYmJjZWIxYWQtNDNmMS0zYjU4LTkxNDctZjE0YmIwYzRkMTU0",
"externalKey": "TICKET-12345"
}