[DOCUMENT] Updated Change

website/content/api-docs/secret/kv/kv-v2.mdx

@@ -511,25 +511,22 @@ this command.
 
 To list secrets for KV v2, a user must have a policy granting them the list capability on this `/metadata/` path - even if all the rest of their interactions with the KV v2 are via the `/data/` APIs. Access to at least list the `/metadata/` path should typically also be granted.
 
-| Method | Path                                 |
-|:-------|:-------------------------------------|
-| `LIST` | `/:secret-mount-path/metadata/:path` |
+| Method | Path                                      |
+|:-------|:------------------------------------------|
+| `GET`  | `/:secret-mount-path/metadata/?list=true` |
 
 ### Parameters
 
 - `secret-mount-path` `(string: <required>)` - The path to the KV mount containing
 the secret to list, such as `secret`. This is specified as part of the URL.
 
-- `path` `(string: <required>)` – Specifies the path of the secrets to list.
-  This is specified as part of the URL.
-
 ### Sample request
 
 ```shell-session
 $ curl \
     --header "X-Vault-Token: ..." \
-    --request LIST \
-    https://127.0.0.1:8200/v1/secret/metadata/my-secret
+    --request GET \
+    https://127.0.0.1:8200/v1/secret/metadata/?list=true
 ```
 
 ### Sample response