commit fefde2d745cc1d9ae628e2bcadcc4a8a54e27e04
parent 629e271c7a338b45295d17568dc10638a446d3ad
Author: Christian Grothoff <christian@grothoff.org>
Date: Fri, 20 Jun 2025 14:26:33 +0200
indent
Diffstat:
1 file changed, 6 insertions(+), 18 deletions(-)
diff --git a/core/api-exchange.rst b/core/api-exchange.rst
@@ -1148,7 +1148,7 @@ Management operations authorized by master key
The request must be a `GlobalFees` message.
- **Response**
+ **Response:**
:http:statuscode:`204 No content`:
The configuration update has been processed successfully. The body is empty.
@@ -1228,7 +1228,7 @@ Management operations authorized by master key
The request must be a `WireTeardownMessage`.
- **Response**
+ **Response:**
:http:statuscode:`204 No content`:
The auditor has successfully disabled the wire method. The body is empty.
@@ -1318,7 +1318,7 @@ Management operations authorized by master key
The request must be an `AmlOfficerSetup` message.
- **Response**
+ **Response:**
:http:statuscode:`204 No content`:
The officer settings have been updated successfully.
@@ -1364,7 +1364,7 @@ Management operations authorized by master key
The request must be an `ExchangePartnerSetupRequest` message.
- **Response**
+ **Response:**
:http:statuscode:`204 No content`:
The partner has been added successfully.
@@ -2135,7 +2135,6 @@ Reserve History
The GET request should come with the following HTTP headers:
*If-None-Match*:
-
The client MAY provide an ``If-None-Match`` header with an
Etag. In that case, the server MUST additionally respond with an ``304``
status code in case the reserve history matches the provided Etag.
@@ -2454,13 +2453,11 @@ Coin History
The GET request should come with the following HTTP headers:
*If-None-Match*:
-
The client MAY provide an ``If-None-Match`` header with an
Etag. In that case, the server MUST additionally respond with an ``304``
status code in case the coin history matches the provided Etag.
*Taler-Coin-History-Signature*:
-
The client MUST provide Base-32 encoded EdDSA signature over a
TALER_SIGNATURE_COIN_HISTORY_REQUEST made with the respective
``$RESERVE_PRIV``, affirming desire to download the current coin
@@ -2487,6 +2484,8 @@ Coin History
:http:statuscode:`404 Not found`:
The coin public key is not (yet) known to the exchange.
+ **Details:**
+
.. ts:def:: CoinHistoryResponse
interface CoinHistoryResponse {
@@ -4226,7 +4225,6 @@ Wallet-to-wallet transfers
To authorize the request, the header must contain the following HTTP header:
*Taler-Purse-Signature*:
-
$PURSE_SIG`` where ``$PURSE_SIG`` is the Crockford base32-encoded EdDSA
signature of purpose TALER_SIGNATURE_WALLET_PURSE_DELETE.
@@ -4814,7 +4812,6 @@ regulatory compliance.
**Request:**
*Account-Owner-Signature*:
-
The client must provide Base-32 encoded EdDSA signature with
``$ACCOUNT_PRIV``, affirming the desire to obtain KYC data. Note that
this is merely a simple authentication mechanism, the details of the
@@ -4823,7 +4820,6 @@ regulatory compliance.
private key.
*Account-Owner-Pub*:
-
The client should provide the Base-32 encoded EdDSA public key of
``$ACCOUNT_PUB``, enabling the exchange to easily locate the correct
public key used for the signature in case multiple wire transfers
@@ -4971,7 +4967,6 @@ regulatory compliance.
**Request:**
*If-None-Match*:
-
The client MAY provide an ``If-None-Match`` header with an ETag.
:query timeout_ms=MILLISECONDS:
@@ -5234,7 +5229,6 @@ and freeze or unfreeze accounts suspected of money laundering.
**Request:**
*Taler-AML-Officer-Signature*:
-
The client must provide Base-32 encoded EdDSA signature with
``$OFFICER_PRIV``, affirming the desire to obtain AML data. Note that
this is merely a simple authentication mechanism, the details of the
@@ -5370,7 +5364,6 @@ and freeze or unfreeze accounts suspected of money laundering.
**Request:**
*Taler-AML-Officer-Signature*:
-
The client must provide Base-32 encoded EdDSA signature with
``$OFFICER_PRIV``, affirming the desire to obtain AML data. Note that this
is merely a simple authentication mechanism, the details of the request are
@@ -5407,7 +5400,6 @@ and freeze or unfreeze accounts suspected of money laundering.
**Request:**
*Taler-AML-Officer-Signature*:
-
The client must provide Base-32 encoded EdDSA signature with
``$OFFICER_PRIV``, affirming the desire to obtain AML data. Note that
this is merely a simple authentication mechanism, the details of the
@@ -5638,7 +5630,6 @@ and freeze or unfreeze accounts suspected of money laundering.
**Request:**
*Taler-AML-Officer-Signature*:
-
The client must provide Base-32 encoded EdDSA signature with
``$OFFICER_PRIV``, affirming the desire to obtain AML data. Note that
this is merely a simple authentication mechanism, the details of the
@@ -5711,7 +5702,6 @@ and freeze or unfreeze accounts suspected of money laundering.
**Request:**
*Taler-AML-Officer-Signature*:
-
The client must provide Base-32 encoded EdDSA signature with
``$OFFICER_PRIV``, affirming the desire to obtain AML data. Note that
this is merely a simple authentication mechanism, the details of the
@@ -5876,7 +5866,6 @@ and freeze or unfreeze accounts suspected of money laundering.
**Request:**
*Taler-AML-Officer-Signature*:
-
The client must provide Base-32 encoded EdDSA signature with
``$OFFICER_PRIV``, affirming the desire to obtain AML data. Note that
this is merely a simple authentication mechanism, the details of the
@@ -6258,7 +6247,6 @@ designated account.
**Request:**
*Account-Request-Signature*:
-
The client must provide Base-32 encoded EdDSA signature made with
``$ACCOUNT_PRIV``, affirming its authorization to delete the account.
The purpose used MUST be ``TALER_SIGNATURE_RESERVE_CLOSE``.
