taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit c448fec3f70eaf102a24ac5cda9c4347891c6c6f
parent 420a45a8fe2ae23a7a182fa90e8d19513d04f462
Author: Bohdan Potuzhnyi <bohdan.potuzhnyi@gmail.com>
Date:   Tue, 23 Sep 2025 18:37:01 +0200

couple of compiler warning fixes

Diffstat:
Mcore/api-donau.rst | 8++------
1 file changed, 2 insertions(+), 6 deletions(-)

diff --git a/core/api-donau.rst b/core/api-donau.rst @@ -308,7 +308,7 @@ Batch Issue This is the effectiv issue receipts request. Depending on the amount of the donation a certain amount of blinded unique donation identifiers, or for short BUDIs, are required. Every BUDI will be signed by the corresponding requested donation unit, which is associated with a value. -This API is used by the charity but the `BlindedDonationReceiptKeyPairs` are coming from the donor. +This API is used by the charity but the array of `BlindedDonationReceiptKeyPair` are coming from the donor. To make the request idempotent, the hash of the hole request is recorded under the corresponding charity_id by the Donau. @@ -653,10 +653,6 @@ The GET status requests require an authorized bearer token as well. The referenced resource needed to create the charity was not found. This response comes with a standard `ErrorDetail` response. - :http:statuscode:`413 Content too large`: - The request exceeded internal limits. This response comes with a standard - `ErrorDetail` response. - .. ts:def:: CharityRequest interface CharityRequest{ @@ -668,7 +664,7 @@ The GET status requests require an authorized bearer token as well. charity_name: string; // Allowed donation volume for the charity per calendar year. max_per_year: Amount; - // Donation volume that has already been received for `current_year`. + // Donation volume that has already been received for current_year. receipts_to_date: Amount; // Calendar year the accounting information refers to. current_year: Integer;