The Amazon Chime SDK Identity, Media Pipelines, Meetings, and Messaging APIs are now published on the new Amazon Chime SDK API Reference. For more information, see the Amazon Chime SDK API Reference.
DeleteAccount
Deletes the specified Amazon Chime account. You must suspend all users before deleting
Team
account. You can use the BatchSuspendUser action
to dodo.
For EnterpriseLWA
and EnterpriseAD
accounts, you must release the
claimed domains for your Amazon Chime account before deletion. As soon as you release
the domain, all users under that account are suspended.
Deleted accounts appear in your Disabled
accounts list for 90 days. To restore
deleted account from your Disabled
accounts list, you must contact AWS
Support.
After 90 days, deleted accounts are permanently removed from your
Disabled
accounts list.
Request Syntax
DELETE /accounts/accountId
HTTP/1.1
URI Request Parameters
The request uses the following URI parameters.
- accountId
-
The Amazon Chime account ID.
Pattern:
.*\S.*
Required: Yes
Request Body
The request does not have a request body.
Response Syntax
HTTP/1.1 204
Response Elements
If the action is successful, the service sends back an HTTP 204 response with an empty HTTP body.
Errors
For information about the errors that are common to all actions, see Common Errors.
- BadRequestException
-
The input parameters don't match the service's restrictions.
HTTP Status Code: 400
- ForbiddenException
-
The client is permanently forbidden from making the request.
HTTP Status Code: 403
- NotFoundException
-
One or more of the resources in the request does not exist in the system.
HTTP Status Code: 404
- ServiceFailureException
-
The service encountered an unexpected error.
HTTP Status Code: 500
- ServiceUnavailableException
-
The service is currently unavailable.
HTTP Status Code: 503
- ThrottledClientException
-
The client exceeded its request rate limit.
HTTP Status Code: 429
- UnauthorizedClientException
-
The client is not currently authorized to make the request.
HTTP Status Code: 401
- UnprocessableEntityException
-
The request was well-formed but was unable to be followed due to semantic errors.
HTTP Status Code: 422
Examples
In the following example or examples, the Authorization header contents(
AUTHPARAMS
) must be replaced with an AWS Signature Version 4 signature. For more information about creating these signatures, see
Signature Version 4 Signing Process in the AWS General Reference.
You only need to learn how to sign HTTP requests if you intend to manually create them. When
you use the AWS Command Line Interface (AWS
CLI)
Example
This example deletes the specified account.
Sample Request
DELETE /console/accounts/12a3456b-7c89-012d-3456-78901e23fg45 HTTP/1.1 Host: service.chime.aws.amazon.com Accept-Encoding: identity User-Agent: aws-cli/1.16.83 Python/3.6.6 Windows/10 botocore/1.12.73 X-Amz-Date: 20190108T180112Z Authorization: AUTHPARAMS Content-Length: 0
Sample Response
HTTP/1.1 204 No Content x-amzn-RequestId: ac41c46f-e26f-4cc1-a9cf-c6056e743647 Content-Type: application/json Date: Tue, 08 Jan 2019 18:01:13 GMT Connection: keep-alive
See Also
For more information about using this API in one of the language-specific AWS SDKs, see the following: