From 3b52a27689552558fef968ae4215009e3345417d Mon Sep 17 00:00:00 2001
From: "Lars K.W. Gohlke" <lkwg82@gmx.de>
Date: Sat, 10 Aug 2024 11:53:44 +0200
Subject: [PATCH] Update README.md

enhance usage
---
 README.md | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/README.md b/README.md
index 23dcc39..ae908fb 100644
--- a/README.md
+++ b/README.md
@@ -35,6 +35,16 @@ kpa.associate();
 You'll get an AssociateID and the public key of an IDKeypair created during the initial connection.
 Both pieces of data combined are needed for further connections. As both are public data, there is no need to store them securely.
 
+next steps:
+```java
+    var id=kpa.getAssociateId();
+    var keyPair = kpa.getIdKeyPairPublicKey();
+
+    var idKeyMap = List.of(Map.of("id", id, "key", keyPair)); // java 21
+    var logins = kpa.getLogins("https://login.url.com/", "", true, idKeyMap);
+    // System.out.println(logins) // nested map with credentials
+```
+
 # keepassxc-protocol
 Communication with KeePassXC happens via the KeePassXC protocol. Currently, the following functionality is implemented:
 *   `change-public-keys`: Request for passing public keys from client to server and back.