About
KAiZN
KAiZEN – A Secure Electronic Signature Tool, streamlines e-Signing process with verified digital signatures. Now, Quickly eSign any document from anywhere, anytime on laptop, phone or tablet. Boost efficiency, and go green with the paperless solution.
Integrations
for every workflow
Streamline your workflows with connected integrations—more than 400 of them.
sample code snippets
Salesforce
Python
PHP
Node JsHow to make a secure HTTP Callout to call the KAiZEN “Initiate Sign API” request?
Solution:
Salesforce Admins / Developers can easily integrate KAiZEN API’s to enhance the e-signing capabilities for the company. Additionally, sales team can track the status of the signed documents and can send the documents to multiple signers in the hierarchy model.
KAiZEN API’s can be easily integrated into Apex, Aura Components, or LWC and it also offers wide range of API to manage different type of actions.
HTTP Request Parameters
| Name | Value |
|---|---|
| Content-Type | application/json |
| Method | POST |
| Endpoint | https://fa-kaizen-prod.azurewebsites.net/api/Sign/RequestStr?code=RTa1A0GW5Yl92OF54-73lRqglLFCt_0pVcg86hWf1EjtAzFuNROcdA== |
| Body | JSON Body with parameters |
Request Body Parameters
| Name | Description | Required? |
|---|---|---|
| docContent | Base64 Content for the PDF File | Yes |
| docName | Name of the File | Yes |
| appToken | Unique Code to initiate the request | Yes |
| requesterEmail | Email address of the person initiating the request | Yes |
| requesterName | Name of the person initiating the request | Yes |
| description | Describes the document | NO |
| signers | An array of the signers who needs to sign the document in the pre-defined order. | Yes |
| CallBackURL | CallbackURL defines the url on which the KAiZEN should send a response once all the signers signs the document. It can be webservice url of Salesforce or any external page. Eg: https://duumy.my.salesforce- sites.com/services/apexrest/KaizenCallbackURL/ |
No |
| docDescription | Describes the document | No |
Sample HTTP Request:
HttpRequest request = new HttpRequest();
request.setEndpoint( << Initiate Sign Endpoint URL >> );
request.setMethod(‘POST’);
request.setHeader(‘Content-Type’, ‘application/json’);
request.setBody( << JSON Body as shown below >> );
request.setTimeout(120000);
Sample JSON Body:
{
“docContent”: “<< Base64 Content for the PDF File. Refer Step 1>>”,
“docName”: “TestBase64File”,
“appToken”: “01HQMDX-YCP019-Z2P3SX-QPSB53-8B4A3F-BC40B8-B10908-FB2FF4-A”,
“requesterEmail”: “mishu67777@gmail.com”,
“requesterName”: “Mohit Bansal”,
“description”: “Sales Contract Document”,
“signers”:[
{
“signerEmail”: “testmail@gmail.com”,
“signerName”: “Mr Harjeet”,
“order”:”1″
{
“signerEmail”: “sales@ayansoftwares.com”,
“signerName”: “Mr Gurleen”,
“order”:”2″
},
],
“CallBackURL”: “<< callback url >>
“docDescription”: “Sales Contract Document”
}
Sample HTTP Response:
{
“FailRules”: [],
“Data”: {
“SignRequestId”: “01HV6MEARQD3X8ZXXX5FR3YDB8”,
“RequestNo”: “KAiZEN-118”
}
}
Once the request is submitted, it will send a response with the request Id. If the callback url is configured, it will send a signed copy of the document on the defined url, once all the signers will sign the document.
How to make a secure HTTP Callout to call the KAiZEN “Initiate Sign API” request?
Solution:
Salesforce Admins / Developers can easily integrate KAiZEN API’s to enhance the e-signing capabilities for the company. Additionally, sales team can track the status of the signed documents and can send the documents to multiple signers in the hierarchy model.
KAiZEN API’s can be easily integrated into Apex, Aura Components, or LWC and it also offers wide range of API to manage different type of actions.
HTTP Request Parameters
| Name | Value |
|---|---|
| Content-Type | application/json |
| Method | POST |
| Endpoint | https://fa-kaizen-prod.azurewebsites.net/api/Sign/RequestStr?code=RTa1A0GW5Yl92OF54-73lRqglLFCt_0pVcg86hWf1EjtAzFuNROcdA== |
| Body | JSON Body with parameters |
Request Body Parameters
| Name | Description | Required? |
|---|---|---|
| docContent | Base64 Content for the PDF File | Yes |
| docName | Name of the File | Yes |
| appToken | Unique Code to initiate the request | Yes |
| requesterEmail | Email address of the person initiating the request | Yes |
| requesterName | Name of the person initiating the request | Yes |
| description | Describes the document | NO |
| signers | An array of the signers who needs to sign the document in the pre-defined order. | Yes |
| CallBackURL | CallbackURL defines the url on which the KAiZEN should send a response once all the signers signs the document. It can be webservice url of Salesforce or any external page. Eg: https://duumy.my.salesforce- sites.com/services/apexrest/KaizenCallbackURL/ |
No |
| docDescription | Describes the document | No |
Sample HTTP Request:
import requests
import json
url = "<< Initiate Sign Endpoint URL >>"
payload = json.dumps('<< JSON Body as shown below >>')
headers = {
'Content-Type': 'application/json',
}
response = requests.request("POST", url, headers=headers, data=payload)
print(response.text)
Sample JSON Body:
{
“docContent”: “<< Base64 Content for the PDF File. Refer Step 1>>”,
“docName”: “TestBase64File”,
“appToken”: “01HQMDX-YCP019-Z2P3SX-QPSB53-8B4A3F-BC40B8-B10908-FB2FF4-A”,
“requesterEmail”: “mishu67777@gmail.com”,
“requesterName”: “Mohit Bansal”,
“description”: “Sales Contract Document”,
“signers”:[
{
“signerEmail”: “testmail@gmail.com”,
“signerName”: “Mr Harjeet”,
“order”:”1″
{
“signerEmail”: “sales@ayansoftwares.com”,
“signerName”: “Mr Gurleen”,
“order”:”2″
},
],
“CallBackURL”: “<< callback url >>
“docDescription”: “Sales Contract Document”
}
Sample HTTP Response:
{
“FailRules”: [],
“Data”: {
“SignRequestId”: “01HV6MEARQD3X8ZXXX5FR3YDB8”,
“RequestNo”: “KAiZEN-118”
}
}
Once the request is submitted, it will send a response with the request Id. If the callback url is configured, it will send a signed copy of the document on the defined url, once all the signers will sign the document.
How to make a secure HTTP Callout to call the KAiZEN “Initiate Sign API” request?
Solution:
Salesforce Admins / Developers can easily integrate KAiZEN API’s to enhance the e-signing capabilities for the company. Additionally, sales team can track the status of the signed documents and can send the documents to multiple signers in the hierarchy model.
KAiZEN API’s can be easily integrated into Apex, Aura Components, or LWC and it also offers wide range of API to manage different type of actions.
HTTP Request Parameters
| Name | Value |
|---|---|
| Content-Type | application/json |
| Method | POST |
| Endpoint | https://fa-kaizen-prod.azurewebsites.net/api/Sign/RequestStr?code=RTa1A0GW5Yl92OF54-73lRqglLFCt_0pVcg86hWf1EjtAzFuNROcdA== |
| Body | JSON Body with parameters |
Request Body Parameters
| Name | Description | Required? |
|---|---|---|
| docContent | Base64 Content for the PDF File | Yes |
| docName | Name of the File | Yes |
| appToken | Unique Code to initiate the request | Yes |
| requesterEmail | Email address of the person initiating the request | Yes |
| requesterName | Name of the person initiating the request | Yes |
| description | Describes the document | NO |
| signers | An array of the signers who needs to sign the document in the pre-defined order. | Yes |
| CallBackURL | CallbackURL defines the url on which the KAiZEN should send a response once all the signers signs the document. It can be webservice url of Salesforce or any external page. Eg: https://duumy.my.salesforce- sites.com/services/apexrest/KaizenCallbackURL/ |
No |
| docDescription | Describes the document | No |
Sample HTTP Request:
$curl = curl_init();
curl_setopt_array($curl, array(
CURLOPT_URL = '<< Initiate Sign Endpoint URL >>',
CURLOPT_RETURNTRANSFER => true,
CURLOPT_ENCODING => '',
CURLOPT_MAXREDIRS => 10,
CURLOPT_TIMEOUT => 0,
CURLOPT_FOLLOWLOCATION => true,
CURLOPT_HTTP_VERSION => CURL_HTTP_VERSION_1_1,
CURLOPT_CUSTOMREQUEST => 'POST',
CURLOPT_POSTFIELDS =>'<< JSON Body as shown below >>',
CURLOPT_HTTPHEADER => array(
'Content-Type: application/json',
),
));
$response = curl_exec($curl);
curl_close($curl);
echo $response;
Sample JSON Body:
{
“docContent”: “<< Base64 Content for the PDF File. Refer Step 1>>”,
“docName”: “TestBase64File”,
“appToken”: “01HQMDX-YCP019-Z2P3SX-QPSB53-8B4A3F-BC40B8-B10908-FB2FF4-A”,
“requesterEmail”: “mishu67777@gmail.com”,
“requesterName”: “Mohit Bansal”,
“description”: “Sales Contract Document”,
“signers”:[
{
“signerEmail”: “testmail@gmail.com”,
“signerName”: “Mr Harjeet”,
“order”:”1″
{
“signerEmail”: “sales@ayansoftwares.com”,
“signerName”: “Mr Gurleen”,
“order”:”2″
},
],
“CallBackURL”: “<< callback url >>
“docDescription”: “Sales Contract Document”
}
Sample HTTP Response:
{
“FailRules”: [],
“Data”: {
“SignRequestId”: “01HV6MEARQD3X8ZXXX5FR3YDB8”,
“RequestNo”: “KAiZEN-118”
}
}
Once the request is submitted, it will send a response with the request Id. If the callback url is configured, it will send a signed copy of the document on the defined url, once all the signers will sign the document.
How to make a secure HTTP Callout to call the KAiZEN “Initiate Sign API” request?
Solution:
Salesforce Admins / Developers can easily integrate KAiZEN API’s to enhance the e-signing capabilities for the company. Additionally, sales team can track the status of the signed documents and can send the documents to multiple signers in the hierarchy model.
KAiZEN API’s can be easily integrated into Apex, Aura Components, or LWC and it also offers wide range of API to manage different type of actions.
HTTP Request Parameters
| Name | Value |
|---|---|
| Content-Type | application/json |
| Method | POST |
| Endpoint | https://fa-kaizen-prod.azurewebsites.net/api/Sign/RequestStr?code=RTa1A0GW5Yl92OF54-73lRqglLFCt_0pVcg86hWf1EjtAzFuNROcdA== |
| Body | JSON Body with parameters |
Request Body Parameters
| Name | Description | Required? |
|---|---|---|
| docContent | Base64 Content for the PDF File | Yes |
| docName | Name of the File | Yes |
| appToken | Unique Code to initiate the request | Yes |
| requesterEmail | Email address of the person initiating the request | Yes |
| requesterName | Name of the person initiating the request | Yes |
| description | Describes the document | NO |
| signers | An array of the signers who needs to sign the document in the pre-defined order. | Yes |
| CallBackURL | CallbackURL defines the url on which the KAiZEN should send a response once all the signers signs the document. It can be webservice url of Salesforce or any external page. Eg: https://duumy.my.salesforce- sites.com/services/apexrest/KaizenCallbackURL/ |
No |
| docDescription | Describes the document | No |
Sample HTTP Request:
var request = require('request');
var options = {
'method': 'POST',
'url': '<< Initiate Sign Endpoint URL >>',
'headers': {
'Content-Type': 'application/json',
},
body: '<< JSON Body as shown below >>'
};
request(options, function (error, response) {
if (error) throw new Error(error);
console.log(response.body);
});
Sample JSON Body:
{
“docContent”: “<< Base64 Content for the PDF File. Refer Step 1>>”,
“docName”: “TestBase64File”,
“appToken”: “01HQMDX-YCP019-Z2P3SX-QPSB53-8B4A3F-BC40B8-B10908-FB2FF4-A”,
“requesterEmail”: “mishu67777@gmail.com”,
“requesterName”: “Mohit Bansal”,
“description”: “Sales Contract Document”,
“signers”:[
{
“signerEmail”: “testmail@gmail.com”,
“signerName”: “Mr Harjeet”,
“order”:”1″
{
“signerEmail”: “sales@ayansoftwares.com”,
“signerName”: “Mr Gurleen”,
“order”:”2″
},
],
“CallBackURL”: “<< callback url >>
“docDescription”: “Sales Contract Document”
}
Sample HTTP Response:
{
“FailRules”: [],
“Data”: {
“SignRequestId”: “01HV6MEARQD3X8ZXXX5FR3YDB8”,
“RequestNo”: “KAiZEN-118”
}
}
Once the request is submitted, it will send a response with the request Id. If the callback url is configured, it will send a signed copy of the document on the defined url, once all the signers will sign the document.
