allow use of secretId when performing operations on secrets

README.md

@@ -357,9 +357,16 @@ If the current user has access to multiple safes, then the destination safeId wi
 Body
 ```
 {
-    "deviceName": "",
+    "deviceName": "device.example.com",
     "deviceCategory": "",
-    "userName": ""
+    "userName": "example-user"
+}
+```
+
+Body
+```
+{
+    "secretId": 29
 }
 ```
 
@@ -369,6 +376,8 @@ Either deviceName or deviceCategory can be specified (or both). Wildcards are su
 1. The percent sign % wildcard matches any sequence of zero or more characters.
 2. The underscore _ wildcard matches any single character.
 
+If the secretId is known, that can also be used to query for the secret. In this case the secretId uniquely identifies the secret so no other parameters are necessary.
+
 #### Search by device name
 
 **GET** `/api/secret/retrieve/name/<searchname>`