taler-docs

commit 727eab1684485e1cc668e4f4c90ce95072cfe5e0
parent 8bb6189041537bd6ffe1d1fe40e3feb4cc7de313
Author: Sebastian <sebasjm@gmail.com>
Date:   Tue,  5 Aug 2025 13:38:59 +0200

endpoint rename

Diffstat:
M
core/api-merchant.rst
 | 
4
++--

1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
@@ -1248,12 +1248,12 @@ Setting up instances
     would be if a deleted but not purged instance is known under this
     ID to the backend.
 
-.. http:post:: /forgot-password/$INSTANCE
+.. http:post:: [/instances/$INSTANCE]/forgot-password
 
   Same as ``/management/instances/$INSTANCE/auth`` it will update the password of the instance but
   without requiring the current password. On the first call it will validate the request
   and return the challenge id with a 202 response. Once the challenge is solved the
-  request needs to be repeated with the X-Challenge-Id header.
+  request needs to be repeated with the X-Challenge-Id header. Since protocol **v21**
 
   **Request** the request must be an `InstanceAuthConfigurationMessage`.