πŸ“Sign Contract

1. Create Session Token : First Step When Customer Click On Sign contract You Have To Initialize Session First By Creating Session Token Using The Following API :

post
Authorizations
Header parameters
Accept-LanguageStringOptional
Body
TenantIdstringOptional
TenantSecretstringOptional
ApplicantIdstring | nullableOptional
selectedSignContractIdstring | nullableOptional
contractTemplateIdintOptional
SignContractFilestring Β· binary | nullableOptional
signContractApproachEnuminteger Β· enumOptionalPossible values:
SignContractModeinteger Β· enumOptionalPossible values:
ContractDetails.GeneralTextstringOptional
ContractDetails.TechnicalTextstring | nullableOptional
ContractDetails.FinancialTextstring | nullableOptional
ContractDetails.LegalTextstring | nullableOptional
ContractDetails.ExtraTextstring | nullableOptional
post
POST /api/v1/Auth/GenerateSignContractRequestSessionToken HTTP/1.1
Host: 
Authorization: YOUR_API_KEY
Content-Type: multipart/form-data
Accept: */*
Content-Length: 383

{
  "TenantId": "text",
  "TenantSecret": "text",
  "ApplicantId": "text",
  "selectedSignContractId": "text",
  "contractTemplateId": null,
  "SignContractFile": "binary",
  "signContractApproachEnum": 1,
  "SignContractMode": 1,
  "ContractDetails.GeneralText": "text",
  "ContractDetails.TechnicalText": "text",
  "ContractDetails.FinancialText": "text",
  "ContractDetails.LegalText": "text",
  "ContractDetails.ExtraText": "text"
}

Sign Contract Approach Enum (1) value if you want to sign by applicant and (2) if you want to sign by organization.

In case (upload file by applicant )

  • the required data only (tenant Id, tenant secret , applicant id , SignContractMode(1 or 2) for low and high modes respectively , SignContractApproachEnum (1 , 2 ) for applicant and organization

  • in case of applicant (SignContractApproachEnum = 1 ) , SignContractFile is Mandatory to be uploaded

  • in case of organization (SignContractApproachEnum = 2) , selectedSignContractId is Mandatory

In case (using Existing Template Created By Organization Admin) or Contract Template Will be created Using Back to Back APIs on the fly

  • in case applicant want to sign ( applicant id and contract template id is mandatory ) in nullable data ( in case organization admin already created an contract Template )

  • in case organization want to sign ( slectedSignContractId is mandatory ) in nullable data ( in case organization admin already created an contract Template )

Low mode (1) for signing contracts using OTP (One-Time Password) is a secure and efficient method where a unique, time-sensitive code is sent to the signatory's mobile device or email. By entering the OTP, the signatory confirms their identity and intent to sign, ensuring only the intended recipient can authorize the contract. This process enhances security and simplifies the signing procedure, making it ideal for remote or digital transactions.

High mode (2) for signing contracts involves using digital signatures, a robust and secure method of authentication. Digital signatures use cryptographic techniques to create a unique digital fingerprint for the signer, which is then attached to the document. This ensures the identity of the signer and the integrity of the document, preventing tampering and unauthorized alterations. High mode digital signatures are ideal for important and legally binding agreements, offering the highest level of security and authenticity.

HighRiskFRA mode (4) for signing contracts involves using digital signatures, a robust and secure method of authentication. Digital signatures use cryptographic techniques to create a unique digital fingerprint for the signer, which is then attached to the document. This ensures the identity of the signer and the integrity of the document, preventing tampering and unauthorized alterations. HighRiskFRA mode digital signatures are ideal for important and legally binding agreements, offering the highest level of security and authenticity.

LowRiskFRA mode (5) for signing contracts using OTP (One-Time Password) is a secure and efficient method where a unique, time-sensitive code is sent to the signatory's mobile device or email. By entering the OTP, the signatory confirms their identity and intent to sign, ensuring only the intended recipient can authorize the contract. This process enhances security and simplifies the signing procedure, making it ideal for remote or digital transactions.

applicantId is sent back to you after onboarding success at the callback URL you configured here. You must save the ID to use for updating and authentication.

Import eNROLL JS File in index.html :

<script src="eNROLL.min.js"></script>

Add Div Element With Specifying Id For This Div

<div id="myDiv">
</div>

Initialize eNroll Component Anywhere In Your JS File After the Document Is Loaded:

eNROLL.init({
        elementId: 'frame',
        mode:"digitalSign",
        url: environment.pluginUrl,
        sessionId: sessionStorage.getItem('sessionToken'),
        onExit: () => {
          this.router.navigateByUrl('login');
        },
        onComplete: () => {
          alert("Completed");
          this.router.navigateByUrl('login');
        },
        onError: (errorCode,message) => {
          alert(`errorCde : ${errorCode} , Message x:${message}`);
        },
      });

Last updated