diff options
Diffstat (limited to 'core/api-exchange.rst')
| -rw-r--r-- | core/api-exchange.rst | 45 |
1 files changed, 2 insertions, 43 deletions
diff --git a/core/api-exchange.rst b/core/api-exchange.rst index 92e76a54..c5a67832 100644 --- a/core/api-exchange.rst +++ b/core/api-exchange.rst @@ -24,50 +24,9 @@ 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. -.. _keys: - --------------------- -Terms of service API --------------------- - -These APIs allow merchants and wallets to obtain the terms of service -and the privacy policy of an exchange. - - -.. http:get:: /terms - - Get the terms of service of the exchange. - The exchange 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 exchange 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. +.. include:: tos.rst - 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 exchange. - The exchange 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 exchange 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. +.. _keys: --------------------------- Exchange status information |