Request Syntax URI Request Parameters Request Body Response Syntax Response Elements Errors Examples See Also

RegenerateSecurityToken

Regenerates the security token for a bot.

Request Syntax


POST /accounts/accountId/bots/{botId}?operation=regenerate-security-token HTTP/1.1

URI Request Parameters

The request uses the following URI parameters.

accountId

The Amazon Chime account ID.

Pattern: .*\S.*

Required: Yes

botId

The bot ID.

Pattern: .*\S.*

Required: Yes

Request Body

The request does not have a request body.

Response Syntax


HTTP/1.1 200
Content-type: application/json

{
   "Bot": { 
      "BotEmail": "string",
      "BotId": "string",
      "BotType": "string",
      "CreatedTimestamp": "string",
      "Disabled": boolean,
      "DisplayName": "string",
      "SecurityToken": "string",
      "UpdatedTimestamp": "string",
      "UserId": "string"
   }
}

Response Elements

If the action is successful, the service sends back an HTTP 200 response.

The following data is returned in JSON format by the service.

Bot

A resource that allows Enterprise account administrators to configure an interface that receives events from Amazon Chime.

Type: Bot object

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

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) or one of the AWS SDKs to make requests to AWS, these tools automatically sign the requests for you with the access key that you specify when you configure the tools. When you use these tools, you don't need to learn how to sign requests yourself.

Example

This example regenerates the security token for the specified bot.

Sample Request


POST /accounts/12a3456b-7c89-012d-3456-78901e23fg45/bots/123abcd4-5ef6-789g-0h12-34j56789012k?operation=regenerate-security-token HTTP/1.1 Host: service.chime.aws.amazon.com Accept-Encoding: identity User-Agent: aws-cli/1.16.170 Python/3.6.0 Windows/10 botocore/1.12.160 X-Amz-Date: 20190918T173015Z Authorization: AUTHPARAMS Content-Length: 0

Sample Response


HTTP/1.1 200 OK x-amzn-RequestId: 0c755efb-46f9-4d5a-84b0-55f7b254ed7d Content-Type: application/json Content-Length: 374 Date: Wed, 18 Sep 2019 17:30:16 GMT Connection: keep-alive {"Bot":{"BotEmail":"myBot@example.com","BotId":"123abcd4-5ef6-789g-0h12-34j56789012k","BotType":"ChatBot","CreatedTimestamp":"2019-09-18T17:24:39.534Z","Disabled":false,"DisplayName":"myBot (Bot)","SecurityToken":"je7MtGbClwBF/2Zp9Utk/h3yCo8nvbEXAMPLEKEY","UpdatedTimestamp":"2019-09-18T17:24:39.534Z","UserId":"123abcd4-5ef6-789g-0h12-34j56789012k"}}