commit b9041ff37b7d47722ef7c2a257481259dfd29e58 parent c84725208dab853f3eeb10349dedb72d99568161 Author: Bohdan Potuzhnyi <bohdan.potuzhnyi@gmail.com> Date: Sun, 28 Sep 2025 00:48:13 +0200 #0010461 adding description for the donau patch charity Diffstat:
| M | core/api-donau.rst | | | 23 | ++++++++++++++++++----- |
1 file changed, 18 insertions(+), 5 deletions(-)
diff --git a/core/api-donau.rst b/core/api-donau.rst @@ -714,20 +714,33 @@ The GET status requests require an authorized bearer token as well. Modify a charity. Only allowed if the request comes with the administrator bearer token. - Not yet implemented (see #10461). - **Request:** - - The body must be a `CharityRequest`. + **Request:** ``CharityRequest`` **Response:** :http:statuscode:`200 OK`: - The request was successful. + The update succeeded. The response body is empty. + + :http:statuscode:`400 Bad Request`: + The request was malformed. For example, ``max_per_year`` must not be + smaller than the current ``receipts_to_date`` of the charity. + + :http:statuscode:`401 Unauthorized`: + Missing or invalid bearer token. :http:statuscode:`403 Forbidden`: The request did not contain an accepted administrator bearer token in its header. + :http:statuscode:`404 Not Found`: + The charity ID is unknown to the Donau. + + **Details:** + + The request body has the same shape as :ts:type:`CharityRequest` used by + :http:POST:`/charities`. All fields are required and will replace the stored + values of the charity. + .. http:DELETE:: /charities/{charity_id}