[taler-docs] branch master updated (837416e -> 143ad12)

[gnunet]

This is an automated email from the git hooks/post-receive script.

ms pushed a change to branch master
in repository docs.

    from 837416e  update API for #7684
     new 53c4a16  allow optional cashout address
     new 143ad12  Access API.

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 core/api-bank-access.rst | 3 +++
 libeufin/api-sandbox.rst | 8 ++++++--
 2 files changed, 9 insertions(+), 2 deletions(-)

diff --git a/core/api-bank-access.rst b/core/api-bank-access.rst
index 2b7b07e..155cde7 100644
--- a/core/api-bank-access.rst
+++ b/core/api-bank-access.rst
@@ -184,6 +184,9 @@ Transactions
 
    **Request**
 
+   :query long_poll_ms: Optional number to express how many milliseconds the 
server
+     should wait for at least one result to be shown.  If not given, the server
+     responds immediately, regardless of the result.
    :query page: page number starting from 1.  Page 1 has the latest 
transactions
      and 1 is the default value.
    :query size: how many transactions per page.  It must be at least 1 and 
defaults to 5.
diff --git a/libeufin/api-sandbox.rst b/libeufin/api-sandbox.rst
index c5372e5..17ca05e 100644
--- a/libeufin/api-sandbox.rst
+++ b/libeufin/api-sandbox.rst
@@ -291,8 +291,12 @@ Accounts
        name: string;
 
        // 'payto' address pointing the bank account
-       // where to send cashouts.
-       cashout_address: string;
+       // where to send cashouts.  This field is optional
+       // because not all the accounts are required to participate
+       // in the merchants' circuit.  One example is the exchange:
+       // that never cashouts.  Registering these accounts can
+       // be done via the access API.
+       cashout_address?: string;
      }
 
    :http:statuscode:`403 Forbidden`:

-- 
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.