summaryrefslogtreecommitdiff
path: root/core
diff options
context:
space:
mode:
Diffstat (limited to 'core')
-rw-r--r--core/api-exchange.rst20
-rw-r--r--core/api-merchant.rst4
2 files changed, 12 insertions, 12 deletions
diff --git a/core/api-exchange.rst b/core/api-exchange.rst
index e427e42f..3d8d8b7e 100644
--- a/core/api-exchange.rst
+++ b/core/api-exchange.rst
@@ -991,7 +991,7 @@ This part of the API is for the use by auditors interacting with the exchange.
The auditor signature is invalid.
:http:statuscode:`404 Not found`:
The denomination key for which the auditor is providing a signature is unknown.
- The response will be a `DenominationUnkownMessage`.
+ The response will be a `DenominationUnknownMessage`.
:http:statuscode:`410 Gone`:
This auditor is no longer supported by the exchange.
:http:statuscode:`412 Precondition failed`:
@@ -1389,7 +1389,7 @@ exchange.
The denomination key or the reserve are not known to the exchange. If the
denomination key is unknown, this suggests a bug in the wallet as the
wallet should have used current denomination keys from ``/keys``.
- In this case, the response will be a `DenominationUnkownMessage`.
+ In this case, the response will be a `DenominationUnknownMessage`.
If the reserve is unknown, the wallet should not report a hard error yet, but
instead simply wait for up to a day, as the wire transaction might simply
not yet have completed and might be known to the exchange in the near future.
@@ -1434,7 +1434,7 @@ exchange.
// What kind of operation was requested that now
// failed?
- oper: String;
+ oper: string;
}
@@ -1580,7 +1580,7 @@ denomination.
Either the denomination key is not recognized (expired or invalid),
or the wire type is not recognized.
If the denomination key is unknown, the response will be
- a `DenominationUnkownMessage`.
+ a `DenominationUnknownMessage`.
:http:statuscode:`409 Conflict`:
The deposit operation has either failed because the coin has insufficient
residual value, or because the same public key of the coin has been
@@ -1975,7 +1975,7 @@ denomination.
purse_pub: EddsaPublicKey;
// Signature by the exchange over a
- // `TALER_CoinPurseRefundConfirmationPS`
+ // ``TALER_CoinPurseRefundConfirmationPS``
// of purpose ``TALER_SIGNATURE_EXCHANGE_CONFIRM_PURSE_REFUND``.
exchange_sig: EddsaSignature;
@@ -2022,7 +2022,7 @@ the API during normal operation.
The exchange does not recognize the denomination key as belonging to the exchange,
or it has expired.
If the denomination key is unknown, the response will be
- a `DenominationUnkownMessage`.
+ a `DenominationUnknownMessage`.
:http:statuscode:`409 Conflict`:
The operation is not allowed as the coin has insufficient
residual value, or because the same public key of the coin has been
@@ -2315,14 +2315,14 @@ in using this API.
The denomination key is unknown, or the blinded
coin is not known to have been withdrawn.
If the denomination key is unknown, the response will be
- a `DenominationUnkownMessage`.
+ a `DenominationUnknownMessage`.
:http:statuscode:`409 Conflict`:
The operation is not allowed as the coin has insufficient
residual value, or because the same public key of the coin has been
previously used with a different denomination. Which case it is
can be decided by looking at the error code
(``TALER_EC_EXCHANGE_RECOUP_COIN_BALANCE_ZERO`` or
- ``TALER_EC_EXCHANGE_GENERIC_COIN_CONFLICTING_DENOMINATION_KEY``).
+ ``TALER_EC_EXCHANGE_GENERIC_COIN_CONFLICTING_DENOMINATION_KEY``).
The response is a `DepositDoubleSpendError`.
:http:statuscode:`410 Gone`:
The requested denomination key is not yet or no longer valid.
@@ -2490,7 +2490,7 @@ typically also view the balance.)
**Request:**
- :query merchant_sig: EdDSA signature of the merchant made with purpose ``TALER_SIGNATURE_MERCHANT_TRACK_TRANSACTION`` over a `TALER_DepositTrackPS`, affirming that it is really the merchant who requires obtaining the wire transfer identifier.
+ :query merchant_sig: EdDSA signature of the merchant made with purpose ``TALER_SIGNATURE_MERCHANT_TRACK_TRANSACTION`` over a ``TALER_DepositTrackPS``, affirming that it is really the merchant who requires obtaining the wire transfer identifier.
**Response:**
@@ -2773,7 +2773,7 @@ Wallet-to-wallet transfers
previously used with a different denomination. Which case it is
can be decided by looking at the error code
(``TALER_EC_EXCHANGE_DEPOSIT_INSUFFICIENT_FUNDS`` or
- ``TALER_EC_EXCHANGE_GENERIC_COIN_CONFLICTING_DENOMINATION_KEY``).
+ ``TALER_EC_EXCHANGE_GENERIC_COIN_CONFLICTING_DENOMINATION_KEY``).
The fields of the response are the same in both cases.
The request should not be repeated again with this coin.
In this case, the response is a `PurseDepositDoubleSpendError`.
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
index cb59314a..ea2ca0b3 100644
--- a/core/api-merchant.rst
+++ b/core/api-merchant.rst
@@ -1478,7 +1478,7 @@ Reserving inventory
// UUID that identifies the frontend performing the lock
// Must be unique for the lifetime of the lock.
- lock_uuid: String;
+ lock_uuid: string;
// How long does the frontend intend to hold the lock?
duration: RelativeTime;
@@ -1602,7 +1602,7 @@ Creating orders
// be used in case different UUIDs were used for different
// products (i.e. in case the user started with multiple
// shopping sessions that were combined during checkout).
- lock_uuids: String[];
+ lock_uuids: string[];
// Should a token for claiming the order be generated?
// False can make sense if the ORDER_ID is sufficiently