Deletes an organization, by ID. It may take up to 10 minutes for the organization to be deleted after the response is returned.
Specify the org ID in the
orgId parameter in the URI.
Deleting your organization permanently deletes all of the information associated with your organization and is irreversible.
Deleting an Organization may fail with a HTTP 409 Conflict response and encounter one or more of the errors described below. Resolve these conditions to allow the delete to succeed.
Org cannot be deleted as it has Linked sites.
Org cannot be deleted as it has active subscriptions or licenses.
Org cannot be deleted as Directory Synchronization is enabled.
Org cannot be deleted as it has more than 1 user.
Org cannot be deleted as it has more than 1 managed by relationship.
Org cannot be deleted as it has managed orgs.
When deleting a Webex for BroadWorks Organization with BroadWorks Directory Synchronization enabled, a prerequisite is to disable BroadWorks Directory Synchronization for the given Organization and then remove all the BroadWorks Directory Synchronization users. Refer to the Organization Deletion section of the Webex for BroadWorks guide for more information.
The unique identifier for the organization.
The list below describes the common success and error responses you should expect from the API.
|200||OK||Successful request with body content.|
|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 |
|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 |
|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 |