--- layout: commands page_title: 'Commands: Intention Delete' --- # Consul Intention Delete Command: `consul intention delete` Corresponding HTTP API Endpoints: [\[DELETE\] /v1/connect/intentions/exact](/api-docs/connect/intentions#delete-intention-by-name), [\[DELETE\] /v1/connect/intentions/:uuid](/api-docs/connect/intentions#delete-intention-by-id) The `intention delete` command deletes a matching intention. The table below shows this command's [required ACLs](/api-docs#authentication). Configuration of [blocking queries](/api-docs/features/blocking) and [agent caching](/api-docs/features/caching) are not supported from commands, but may be from the corresponding HTTP endpoint. | ACL Required | | ------------------------------ | | `intentions:write`1 |

1 Intention ACL rules are specified as part of a{' '} service rule. See{' '} Intention Management Permissions {' '} for more details.

-> **Deprecated** - The one argument form of this command is deprecated in Consul 1.9.0. Intentions no longer need IDs when represented as [`service-intentions`](/docs/connect/config-entries/service-intentions) config entries. ## Usage Usage: - `consul intention delete [options] SRC DST` - `consul intention delete [options] ID` `SRC` and `DST` can both take [several forms](/commands/intention#source-and-destination-naming). #### Enterprise Options @include 'http_api_partition_options.mdx' @include 'http_api_namespace_options.mdx' #### API Options @include 'http_api_options_client.mdx' ## Examples Delete an intention from "web" to "db" with any action: ```shell-session $ consul intention delete web db ``` Delete an intention by unique ID: ```shell-session $ consul intention delete 4ffed935-439c-695d-4f51-f4fc0b12a7a7 ```