diff options
Diffstat (limited to 'core/api-taldir.rst')
| -rw-r--r-- | core/api-taldir.rst | 50 |
1 files changed, 7 insertions, 43 deletions
diff --git a/core/api-taldir.rst b/core/api-taldir.rst index 2e846254..4da9bb02 100644 --- a/core/api-taldir.rst +++ b/core/api-taldir.rst @@ -34,48 +34,10 @@ for all details not specified in the individual requests. The `glossary <https://docs.taler.net/glossary.html#glossary>`_ defines all specific terms used in this section. --------------------- -Terms of service API --------------------- - -These APIs allow wallets to obtain the terms of service -and the privacy policy of the TalDir. - - -.. http:get:: /terms - - Get the terms of service of the TalDir. - The TalDir will consider the "Accept" and "Accept-Language" and - "Accept-Encoding" headers when generating a response. Specifically, - it will try to find a response with an acceptable mime-type, then - pick the version in the most preferred language of the user, and - finally apply compression if that is allowed by the client and - deemed beneficial. - - The TalDir will set an "Etag", and subsequent requests of the - same client should provide the tag in an "If-None-Match" header - to detect if the terms of service have changed. If not, a - "204 Not Modified" response will be returned. +.. contents:: Table of Contents + :local: - If the "Etag" is missing, the client should not cache the response and instead prompt the user again at the next opportunity. This is usually only the case if the terms of service were not configured correctly. - - -.. http:get:: /privacy - - Get the privacy policy of the TalDir. - The TalDir will consider the "Accept" and "Accept-Language" and - "Accept-Encoding" headers when generating a response. Specifically, - it will try to find a response with an acceptable mime-type, then - pick the version in the most preferred language of the user, and - finally apply compression if that is allowed by the client and - deemed beneficial. - - The TalDir will set an "Etag", and subsequent requests of the - same client should provide the tag in an "If-None-Match" header - to detect if the privacy policy has changed. If not, a - "204 Not Modified" response will be returned. - - If the "Etag" is missing, the client should not cache the response and instead prompt the user again at the next opportunity. This is usually only the case if the privacy policy was not configured correctly. +.. include:: tos.rst ------------------------- @@ -103,14 +65,16 @@ Configuration information name: "taler-directory"; // Supported registration methods - methods: Method[]; + methods: TaldirMethod[]; // fee for one month of registration monthly_fee: Amount; } - interface Method { + .. ts:def:: TaldirMethod + + interface TaldirMethod { // Name of the method, e.g. "email" or "sms". name: string; |