How to add Digital Signature in C# using KAiZEN APIs?

Step-by-Step Guide to Integrate eSignatures in C# Applications:

1. Step 2:

   You’ll need to initiate a secure HTTP POST request to the KAiZEN “Initiate Sign API” with the following parameters:

   HTTP Call Details

   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

   Key Parameters for the 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
   newRequestEmailSubject	Describes the email subject	No
   requesterMessage	Describes the prompt eSignature field	No
   docDescription	Describes the document	No

2. Step 3:

   C# Code Example for Integration

   							
   var client = new HttpClient();
   var request = new HttpRequestMessage(HttpMethod.Post, "https://fa-kaizen-staging.azurewebsites.net/api/Sign/RequestStr?code=mLgEBTpi9dfooQ6TB9gc7sa4qiIuuxmqQYoTx8nQQ1StAzFu93g06A==");
   var content = new StringContent("{\n    \"docContent\":\"<>\",\n    \"requesterEmail\": \"xyz@gmail.com\",\n    \"requesterName\": \"XYZ\",\n    \"requesterPhone\": \"xxxxx-xxx-xxxx\",\n    \"description\" :\"\",\n    \"newRequestEmailSubject\":\"You have a document to sign\",\n    \"requesterMessage\": \"Kindly eSign your KAiZEN Test PDF\",\n    \"signers\": [\n        {\n            \"signerEmail\": \"signer1@gmail.com\",\n            \"signerName\": \"Signer1\",\n            \"signerPhone\": \"xx-xxx-xxxx-xxx\",\n            \"order\": \"1\",\n            \"signerRole\": \"signer\"\n               \n        },{\n            \"signerEmail\": \"signer2@gmail.com\",\n            \"signerName\": \"Signer2\",\n            \"signerPhone\": \"xxx-xxx-xxxx-xxxx\",\n            \"order\": \"2\",\n            \"signerRole\": \"reviewer\"\n               \n        }\n    ],\n    \n    \"docDescription\": \"Base 64 string based test doc\",\n    \"callbackurl\": \"\"\n}", null, "application/json");
   request.Content = content;
   var response = await client.SendAsync(request);
   response.EnsureSuccessStatusCode();
   Console.WriteLine(await response.Content.ReadAsStringAsync());
   
   
   
   							
   						

   Sample API Response:

   							
   								{
   “FailRules”: [],
   “Data”: {
   “SignRequestId”: “01HV6MEARQD3X8ZXXX5FR3YDB8”,
   “RequestNo”: “KAiZEN-118”
   }
   }
   							
   						

   Once the request is accepted, a unique request ID is returned. If a callback URL is provided, a signed PDF will be sent to the specified endpoint after all signers have completed their actions.

   What Happens After the API Call?

   Each signer receives an email notification to begin signing, following the pre-defined order. The signing flow is intuitive and secure.