Questa pagina non è tradotta nella tua lingua. Richiedi traduzione

End of support notice: On February 20, 2026, AWS will end support for the Amazon Chime service. After February 20, 2026, you will no longer be able to access the Amazon Chime console or Amazon Chime application resources. For more information, visit the blog post. Note: This does not impact the availability of the Amazon Chime SDK service.

End of support notice: On February 20, 2026, AWS will end support for the Amazon Chime service. After February 20, 2026, you will no longer be able to access the Amazon Chime console or Amazon Chime application resources. For more information, visit the blog post. Note: This does not impact the availability of the Amazon Chime SDK service.

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.

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.

Errors

For information about the errors that are common to all actions, see Common Errors.

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"}}

See Also

For more information about using this API in one of the language-specific AWS SDKs, see the following: