[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[GNUnet-SVN] [taler-api] branch master updated: clarify frontend API
From: |
gnunet |
Subject: |
[GNUnet-SVN] [taler-api] branch master updated: clarify frontend API |
Date: |
Thu, 12 Jan 2017 15:05:21 +0100 |
This is an automated email from the git hooks/post-receive script.
dold pushed a commit to branch master
in repository api.
The following commit(s) were added to refs/heads/master by this push:
new f0aa7df clarify frontend API
f0aa7df is described below
commit f0aa7dfecf94c1af3d767e6f50f9e195a3c46138
Author: Florian Dold <address@hidden>
AuthorDate: Thu Jan 12 15:05:18 2017 +0100
clarify frontend API
---
api-merchant.rst | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/api-merchant.rst b/api-merchant.rst
index a6b2809..9eccc2f 100644
--- a/api-merchant.rst
+++ b/api-merchant.rst
@@ -29,10 +29,11 @@ Before reading the API reference documentation, see the
:ref:`merchant architect
The Frontend HTTP API
---------------------
+This frontend API is non-normative, and only gives an example of what a
typical frontend API would look like.
+
.. http:get:: contract_url
- Triggers the contract generation. Note that the URL may differ between
- merchants.
+ Requesting this URL generates a contract, typically with a new (and unique)
transaction id.
**Request:**
@@ -51,7 +52,8 @@ The Frontend HTTP API
Send the deposit permission to the merchant. The client should POST a
`DepositPermission`_
- object.
+ object. If the payment was processed successfully by the merchant, this URL
will set session
+ state that allows the fulfillment URL to show the final product.
.. _DepositPermission:
.. code-block:: tsref
--
To stop receiving notification emails like this one, please contact
address@hidden
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [GNUnet-SVN] [taler-api] branch master updated: clarify frontend API,
gnunet <=