Request items are used to call the Web API, for example. However, they may also be used to notify your website (as a webhook)Documentation Index
Fetch the complete documentation index at: https://help.cryptolens.io/llms.txt
Use this file to discover all available pages before exploring further.
- Url - The URL that Cryptolens will call upon successful transaction.
- Type - The type of request.
- DataRequest - This assumes the website (eg. Web API result) returns a JSON object (a hashmap, to be precise). Cryptolens will take these values and insert them into the thank you page, instead of the
[name]. So, if JSON object is{"key":"ABCD"}, and our message contains **Thank you. Your key is[key]., the customer will see Thank you. Your key is ABCD. - VoidRequest - Simply sends a request without taking into account what it returns.
- DataRequest - This assumes the website (eg. Web API result) returns a JSON object (a hashmap, to be precise). Cryptolens will take these values and insert them into the thank you page, instead of the
- Method - This can either be GET or POST. Web API 3 requires this to be GET.
Passing variables from one request
If the first request returns a JSON, those values can be used in the URL of succeeding requests further down. For example, if the first request returns akey, then we can add this value to the next request using [key]. These values can also be used in the custom message.
Pre-set variables
In addition to the variables returned from each request and the custom field, there are also several variables provided by Cryptolens. They all start with “cl_” prefix. Currently, the following variables are available:cl_transaction_id- the transaction id returned by either Stripe or PayPal. Useful if you would need to issue a refund, etc.cl_email- the email provided in the payment form.