diff options
Diffstat (limited to 'texinfo/taler-merchant-api-tutorial.texi')
-rw-r--r-- | texinfo/taler-merchant-api-tutorial.texi | 24 |
1 files changed, 12 insertions, 12 deletions
diff --git a/texinfo/taler-merchant-api-tutorial.texi b/texinfo/taler-merchant-api-tutorial.texi index c4ce9ffb..558313fe 100644 --- a/texinfo/taler-merchant-api-tutorial.texi +++ b/texinfo/taler-merchant-api-tutorial.texi @@ -21,7 +21,7 @@ @copying @quotation -GNU Taler 0.9.0, Jul 06, 2022 +GNU Taler 0.9.0, Nov 03, 2022 GNU Taler team @@ -242,7 +242,7 @@ key in the @code{Authorization} header. The value of this header must be @example >>> import requests >>> requests.get("https://backend.demo.taler.net", -... headers=@{"Authorization": "ApiKey sandbox"@}) +... headers=@{"Authorization": "secret-token:secret"@}) <Response [200]> @end example @@ -363,9 +363,9 @@ A minimal Python snippet for creating an order would look like this: ... summary="Donation", ... fulfillment_url="https://example.com/thanks.html"), ... create_token=false) ->>> response = requests.post("https://backend.demo.taler.net/private/order", +>>> response = requests.post("https://backend.demo.taler.net/private/orders", ... json=body, -... headers=@{"Authorization": "ApiKey sandbox"@}) +... headers=@{"Authorization": "secret-token:secret"@}) <Response [200]> @end example @@ -424,7 +424,7 @@ backend to do it is the safest method. @example >>> import requests >>> r = requests.get("https://backend.demo.taler.net/private/orders/" + order_id, -... headers=@{"Authorization": "ApiKey sandbox"@}) +... headers=@{"Authorization": "secret-token:secret"@}) >>> print(r.json()) @end example @@ -453,7 +453,7 @@ the merchant’s obligations under the contract. @cartouche @quotation Note You do not need to keep querying to notice changes -to the order’s transaction status. The endpoints +to the order's transaction status. The endpoints support long polling, simply specify a @code{timeout_ms} query parameter with how long you want to wait at most for the order status to change to @code{paid}. @@ -508,7 +508,7 @@ This code snipped illustrates giving a refund: ... reason="Customer did not like the product") >>> requests.post("https://backend.demo.taler.net/private/orders/" ... + order_id + "/refund", json=refund_req, -... headers=@{"Authorization": "ApiKey sandbox"@}) +... headers=@{"Authorization": "secret-token:secret"@}) <Response [200]> @end example @@ -551,8 +551,8 @@ from the QR code). The merchant backend then updates the session ID of the existing order to the current session ID of the browser. When the payment status for the -“new” unpaid order is checked (or already in long-polling), the backend -detects that for the browser’s @emph{session ID} and @emph{fulfillment URL} there is an +"new" unpaid order is checked (or already in long-polling), the backend +detects that for the browser's @emph{session ID} and @emph{fulfillment URL} there is an existing paid contract. It then tells the browser to immediately redirect to the fulfillment URL where the already paid article is available. @@ -595,7 +595,7 @@ funds available for tipping, query the @code{/tip-query} endpoint: @example >>> import requests >>> requests.get("https://backend.demo.taler.net/tip-query?instance=default", -... headers=@{"Authorization": "ApiKey sandbox"@}) +... headers=@{"Authorization": "secret-token:secret"@}) <Response [200]> @end example @anchor{taler-merchant-api-tutorial authorize-tip}@anchor{14} @@ -634,7 +634,7 @@ This code snipped illustrates giving a tip: ... justification="User filled out survey", ... next_url="https://merchant.com/thanks.html") >>> requests.post("https://backend.demo.taler.net/tip-authorize", json=tip_req, -... headers=@{"Authorization": "ApiKey sandbox"@}) +... headers=@{"Authorization": "secret-token:secret"@}) <Response [200]> @end example @@ -1020,8 +1020,8 @@ render fields that they do not understand as a key-value list. @printindex ge -@anchor{c}@w{ } @anchor{taler-merchant-api-tutorial The-Taler-Order-Format}@w{ } +@anchor{c}@w{ } @c %**end of body @bye |