DeleteBot - Amazon Lex


Deletes all versions of a bot, including the Draft version. To delete a specific version, use the DeleteBotVersion operation.

When you delete a bot, all of the resources contained in the bot are also deleted. Deleting a bot removes all locales, intents, slot, and slot types defined for the bot.

If a bot has an alias, the DeleteBot operation returns a ResourceInUseException exception. If you want to delete the bot and the alias, set the skipResourceInUseCheck parameter to true.

Request Syntax

DELETE /bots/botId/?skipResourceInUseCheck=skipResourceInUseCheck HTTP/1.1

URI Request Parameters

The request uses the following URI parameters.


The identifier of the bot to delete.

Length Constraints: Fixed length of 10.

Pattern: ^[0-9a-zA-Z]+$

Required: Yes


When true, Amazon Lex doesn't check to see if another resource, such as an alias, is using the bot before it is deleted.

Request Body

The request does not have a request body.

Response Syntax

HTTP/1.1 202 Content-type: application/json { "botId": "string", "botStatus": "string" }

Response Elements

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

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


The unique identifier of the bot that Amazon Lex is deleting.

Type: String

Length Constraints: Fixed length of 10.

Pattern: ^[0-9a-zA-Z]+$


The current status of the bot. The status is Deleting while the bot and its associated resources are being deleted.

Type: String

Valid Values: Creating | Available | Inactive | Deleting | Failed | Versioning


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


HTTP Status Code: 409


HTTP Status Code: 500


HTTP Status Code: 412


HTTP Status Code: 402


HTTP Status Code: 429


HTTP Status Code: 400

See Also

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