--- layout: commands page_title: 'Commands: Intention Get' --- # Consul Intention Get Command: `consul intention get` Corresponding HTTP API Endpoints: [\[GET\] /v1/connect/intentions/exact](/api-docs/connect/intentions#read-specific-intention-by-name), [\[GET\] /v1/connect/intentions/:uuid](/api-docs/connect/intentions#read-specific-intention-by-id) The `intention get` command shows a single intention. -> **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. The table below shows this command's [required ACLs](/api#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:read`1 |

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

## Usage Usage: - `consul intention get [options] SRC DST` - `consul intention get [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 ```shell-session $ consul intention get web db Source: web Destination: db Action: deny ID: 20edfa56-9cd4-51db-8c22-db09fdec61ef Created At: Thursday, 24-May-18 17:07:49 PDT ```