consul/website/content/commands/intention/delete.mdx

---
layout: commands
page_title: 'Commands: Intention Delete'
---

# Consul Intention Delete

Command: `consul intention delete`

Corresponding HTTP API Endpoints: [\[DELETE\] /v1/connect/intentions/exact](/consul/api-docs/connect/intentions#delete-intention-by-name), [\[DELETE\] /v1/connect/intentions/:uuid](/consul/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](/consul/api-docs/api-structure#authentication). Configuration of
[blocking queries](/consul/api-docs/features/blocking) and [agent caching](/consul/api-docs/features/caching)
are not supported from commands, but may be from the corresponding HTTP endpoint.

| ACL Required                   |
| ------------------------------ |
| `intentions:write`<sup>1</sup> |

<p>
  <sup>1</sup> Intention ACL rules are specified as part of a{' '}
  <code>service</code> rule. See{' '}
  <a href="/docs/connect/intentions#intention-management-permissions">
    Intention Management Permissions
  </a>{' '}
  for more details.
</p>

-> **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`](/consul/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](/consul/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
```