taler-docs

commit 3374b425be0b4f9a65e8a547f9f1f9533451c7fd
parent 66cb3c58afcf772530701de8721bd66595d543ed
Author: Christian Grothoff <christian@grothoff.org>
Date:   Fri,  3 Apr 2026 18:00:28 +0200

fix minor spec isues

Diffstat:
M
core/exchange/get-transfers-WTID.rst
 | 
2
+-
M
core/exchange/post-kyc-start-ID.rst
 | 
5
+++++
M
core/exchange/post-management-global-fees.rst
 | 
15
+++++++++------
M
core/exchange/post-recoup-refresh.rst
 | 
17
++++++++---------
M
core/exchange/post-withdraw.rst
 | 
4
++--

5 files changed, 25 insertions(+), 18 deletions(-)
diff --git a/core/exchange/get-transfers-WTID.rst b/core/exchange/get-transfers-WTID.rst
@@ -48,7 +48,7 @@
       // Should match one of the exchange's signing keys from ``/keys``.  Again given
       // explicitly as the client might otherwise be confused by clock skew as to
       // which signing key was used.
-      exchange_pub: EddsaSignature;
+      exchange_pub: EddsaPublicKey;
     }
 
   .. ts:def:: TrackTransferDetail
diff --git a/core/exchange/post-kyc-start-ID.rst b/core/exchange/post-kyc-start-ID.rst
@@ -33,6 +33,11 @@
     The uploaded body is to long, it exceeds the size limit.
     Returned with an error code of
     ``TALER_EC_GENERIC_UPLOAD_EXCEEDS_LIMIT``.
+  :http:statuscode:`400 Internal Server Error`:
+    The server had an internal problem processing the request.
+    Returned with error codes of:
+    - ``TALER_EC_EXCHANGE_KYC_GENERIC_LOGIC_BUG``
+    - ``TALER_EC_GENERIC_INTERNAL_INVARIANT_FAILURE``
 
   **Details:**
 
diff --git a/core/exchange/post-management-global-fees.rst b/core/exchange/post-management-global-fees.rst
@@ -11,9 +11,12 @@
   :http:statuscode:`204 No content`:
     The configuration update has been processed successfully. The body is empty.
   :http:statuscode:`403 Forbidden`:
-    The signature is invalid.
+    The signature is invalid. Returned with an error code
+    of ``TALER_EC_EXCHANGE_MANAGEMENT_GLOBAL_FEE_SIGNATURE_INVALID``.
   :http:statuscode:`409 Conflict`:
     The exchange has previously received a conflicting configuration message.
+    Returned with an error code of
+    ``TALER_EC_EXCHANGE_MANAGEMENT_GLOBAL_FEE_MISMATCH``.
   :http:statuscode:`413 Request entity too large`:
     The uploaded body is to long, it exceeds the size limit.
     Returned with an error code of
@@ -25,11 +28,14 @@
 
     interface GlobalFeesRequest {
 
+      // Signature of `TALER_GlobalFeesPS`.
+      master_sig: EddsaSignature;
+
       // What date (inclusive) does these fees go into effect?
-      start_date: Timestamp;
+      fee_start: Timestamp;
 
       // What date (exclusive) does this fees stop going into effect?
-      end_date: Timestamp;
+      fee_end: Timestamp;
 
       // Account history fee, charged when a user wants to
       // obtain a reserve/account history.
@@ -63,7 +69,4 @@
       // plus this value.
       purse_timeout: RelativeTime;
 
-      // Signature of `TALER_GlobalFeesPS`.
-      master_sig: EddsaSignature;
-
     }
diff --git a/core/exchange/post-recoup-refresh.rst b/core/exchange/post-recoup-refresh.rst
@@ -22,11 +22,13 @@
   **Response:**
 
   :http:statuscode:`200 OK`:
-    The request was successful, and the response is a `RecoupRefreshConfirmation`.
+    The request was successful, and the response
+    is a `RecoupRefreshConfirmationResponse`.
     Note that repeating exactly the same request
-    will again yield the same response, so if the network goes down during the
-    transaction or before the client can commit the coin signature to disk, the
-    coin is not lost.
+    will again yield the same response, so if the
+    network goes down during the transaction or
+    before the client can commit the coin signature to disk,
+    the coin is not lost.
   :http:statuscode:`403 Forbidden`:
     The coin's signature is invalid.
     This response comes with a standard `ErrorDetail` response.
@@ -72,13 +74,10 @@
     }
 
 
-  .. ts:def:: RecoupRefreshConfirmation
+  .. ts:def:: RecoupRefreshConfirmationResponse
 
-    interface RecoupRefreshConfirmation {
+    interface RecoupRefreshConfirmationResponse {
       // Public key of the old coin that will receive the recoup.
       old_coin_pub: EddsaPublicKey;
 
-      // The new balance of the old coin, after it has absorved
-      // the residual values of the coins from the request.
-      balance: Amount;
     }
diff --git a/core/exchange/post-withdraw.rst b/core/exchange/post-withdraw.rst
@@ -64,7 +64,7 @@
        The response comes with a standard `ErrorDetail` response with
        an error-code of
        ``TALER_EC_EXCHANGE_RESERVES_AGE_RESTRICTION_REQUIRED``
-       and an additional field ``allowed_maximum_age`` for the
+       and an additional field ``maximum_allowed_age`` for the
        maximum age (in years)
        that the client can commit to in a call to ``/withdraw``, this time
        with ``max_age`` set accordingly and ``coin_evs`` being an array
@@ -73,7 +73,7 @@
        according to the reserve's birthday. The response comes with a
        standard `ErrorDetail` response with error-code
        ``TALER_EC_EXCHANGE_AGE_WITHDRAW_MAXIMUM_AGE_TOO_LARGE``
-       and an additional field ``allowed_maximum_age`` for the maximum
+       and an additional field ``maximum_allowed_age`` for the maximum
        age (in years) that the client can commit to in a call
        to ``/withdraw``.
     4. The request uses a nonce value that was previously seen by