# Welcome to Evia Sign Evia Sign is an intuitive digital platform to securely and seamlessly get your electronic documents signed. Evia Sign can help you transition to a more paperless workplace by providing an e-signing experience to streamline workflows, increase productivity and security, and achieve greater business agility. ## Quick Navigation {% content-ref url="/pages/KE1QgWp3mM1mZev8wg9w" %} [What can Evia Sign do?](/welcome-to-evia-sign/what-can-evia-sign-do) {% endcontent-ref %} # What can Evia Sign do? The paradigm shift in the workspace culture has made the world turn digital. To cope with the new normal, Evia Sign has revolutionized your conventional ways of signing a document into a digital experience that is hassle-free, secure, and faster. Evia Sign can provide you with: * A seamless e-signing experience * Improved productivity among remote and global teams * Simplify complicated workflow processes * Protection of confidential documents and sensitive data * An on-the-go digital solution that is less erroneous and time-saving * Less paperwork, eco-friendly and sustainable # How to send signature request? In Evia Sign, sending a document can be done in simple steps, check out the instructions below: {% embed url="" %} ### **Document upload** * Start by clicking on the **SIGN REQUEST** button.
This action will take you to the document-sending process.
* Click on the **BROWSE** button and choose a file in the supported format (PDF/DOC/DOCX) or simply drag and drop the document onto the dotted rectangular space. * You can also upload a document through your OneDrive cloud account. ![](/files/sDx9YqemDYpurgOKtmgC) * You can upload multiple documents by clicking the Browse button again and choosing a file in the supported format (PDF/DOC/DOCX), or drag and drop the document onto the dotted rectangular space or upload via your OneDrive cloud account.
* Once the documents are uploaded successfully, click **NEXT**. ### **Adding signatory** * Type the signatory name followed by the email address in the provided space. You can add multiple signatories by clicking the **PLUS** button and following a similar process. Once done click **NEXT**. ![ ](/files/c37n4kou1oYbrd9Scnpt) {% hint style="info" %} In a multiple signatories scenario, you can modify the signatories' signing order using the drag and drop icon. {% endhint %} ![](/files/dSYk0zL6EXLlj5SBSM4l) ### **Adding the stamps** * First, select the signatory to whom you want to configure the stamps. * Next, click on the required stamp and click again on the document's specific location where you want the stamp to appear. ![](/files/UrdKvB9oHPzweMLIYGq9) ![](/files/3UPodFn6PFqfdyPuTvy5) {% hint style="info" %} Follow the same procedure for any required stamp of choice (Signature, Initial, Date Signed, Email, and Text). {% endhint %} * Select the next signatory and repeat the same process. ![](/files/dcRx8sCY4B6SE5f10ZF5) {% hint style="info" %} To delete a stamp, select the required stamp and click DELETE key on your keyboard or you can right-click on the required stamp and click on the **Delete** option. {% endhint %} * In the case of multiple documents, once you have configured the stamps for the first document, click on the second document and repeat the same process to configure the stamps for the signatories.
### **Authentication and Private Messaging** Enabling the authentication option allows you to set up OTP or Access code to verify the signatory before they access the document for signing. Enabling the private messaging option allows you to send messages to each signatory individually. Click **NEXT**. ![](/files/hIY6JWamN4SGdVmLpQZM) ### **Document summary** * In the final step, the default title of the document can be modified and you can also type a common message to be delivered to all the signatories. * Finally, click the **SEND** button. ![](/files/Y9fN9cgG5yFFeDiKka9n) * You will receive a pop-up message confirming the delivery of your document. The delivered document will have a built-in 30-day expiration date. ![](/files/Ik1ZDRSzwylIjykqGBvP) ## **Quick Navigation** {% content-ref url="/pages/YLMqrNYOc7zSLBaDDGnX" %} [How do you configure stamps?](/faqs/how-do-you-configure-stamps) {% endcontent-ref %} {% content-ref url="/pages/TrmufdnawnFduQSHczXE" %} [How do you add authentication to your request?](/how-to-send-signature-request/how-do-you-add-authentication-to-your-request) {% endcontent-ref %} {% content-ref url="/pages/XjQEqEuCafMYMbWDg6jb" %} [How do you send a private message?](/how-to-send-signature-request/how-do-you-send-a-private-message) {% endcontent-ref %} # How to enable multiple signatories to access and sign documents at the same time? Evia Sign allows you to send a signature request to all signatories simultaneously. Multiple signatories can now access and sign documents at the same time, giving them the flexibility to sign without following a specific order. \ \ Here's a simplified guide: ### **Upload the Document** * Start by uploading your document to Evia Sign.

Upload Document

### **Disabling the Signing Order** * Move to the next step where you can disable the signing order option. * This allows signatories to access and sign documents simultaneously, irrespective of their position in the queue.

Disabling the Signing Order

Unordered Signing

### **Add Your Signatories** * Proceed to add your signatories for the signature request. ### **Complete Additional Actions** * Move on to steps 3 and 4 to finish the additional actions required. {% hint style="info" %} For a more detailed guide on completing steps 3 and 4, please refer to the link below: {% endhint %} {% content-ref url="/pages/bSIcL11ZHdESBUQwbvGU" %} [How to send signature request?](/how-to-send-signature-request) {% endcontent-ref %} ### Send the Document to Signatories * Finally, send the document to the relevant signatories, who can now sign simultaneously, streamlining the signing workflow for enhanced efficiency. # How to add approvers and CC recipients to a signature request? Follow the below process to add approvers and CC recipients to a signature request: * Once you have uploaded the document that you want to send for signature request, click Next to proceed to the second step.
* In this step, you can assign roles to each recipient: whether they will act as a signatory, an approver, or simply receive a copy (CC) of the document. You can do this by clicking on the **Role** icon.
To add an approver: * Click on the approver option.
* Enter the name and the email address for the approver in the provided spaces.
{% hint style="info" %} If multiple approvers are needed, repeat this step for each one. {% endhint %} To add a CC recipient: * Click on the CC option.
* Enter the name and the email address for the CC recipient in the provided spaces.
{% hint style="info" %} If multiple CC recipients are needed, repeat this step for each one. **Note:** CC recipients will receive a copy of the signed document for informational purposes, but they are not required to take any action. {% endhint %} You can proceed to the third step, where you have the option to place the signatory stamp. During this step, you can still change the roles by clicking the **Role** icon and adjust the order of the recipients using the **Drag and Drop** icon, according to your preference.
{% hint style="info" %} After you have determined the recipients and their roles in the document, you can proceed with the further actions to successfully send your signature request. {% endhint %} # How do you add authentication to your request? Verifying your signatory is essential when handling confidential documents that contain sensitive data. The authentication feature has two options: 1. Email OTP (One Time Password) 2. Access code Check out how each authentication type works:
OTP (EMAIL/SMS) *A six-digit verification code auto-generated by the Evia Sign.* You have the option of sending this OTP to the signatory's phone number, the email address, or both.
Access code The signature requester *can specify a verification code of their choice. In this case, the verification code will be directly communicated to the signatory(s).*
Follow the detailed steps below to set up authentication: * Select the signatory to whom you want to set up the authentication option and enable authentication by clicking the toggle switch to activate the feature. ![](/files/61mZ4smb2EryyMsPu9Pw) * Select one of the authentication options. ![One Time Password (OTP)](/files/llvGBfAwPMo835qvOZhS) ![Access Code](/files/dpar43Anlg1GfrInkQhr) * This action will assure that an email OTP or an access code is always requested from the signatory when proceeding to open and sign the document. {% hint style="info" %} In the case of multiple signatories, follow the same procedure. {% endhint %} # How do you send a private message? You can send private messages to each signatory along with the requested document. Follow the detailed steps below to send a private message: * Select the signatory you want to send the private message. * Enable the private message feature by clicking the toggle switch. ![](/files/U0URHpqQdEt8qAQ8ttXY) * Type your message in the provided space ![](/files/FmMjhvzMJMW2YaLUSevS) # How to sign documents? ### **Opening the document through your email** * Open the document through your email. and click on the **VIEW DOCUMENT** to open and sign the document. ![](/files/zHm74ohh12eUQ73QJZrU) * Click the **CONTINUE** button once you have read and accepted the terms. ![](/files/ztnDR7x32BlpLowhwxS1) ### **Signing your document** * Click on the **Sign Here** stamp. ![](/files/UL58vBPEtTrzV2a10hNo) * This action will bring out an **ADD SIGNATURE** dialogue box with four options 1. Choosing a pre-determined signature font style generated by Evia Sign 2. Signing with a mobile device 3. Drawing your signature 4. Signature file upload. ![](/files/kq1aG2hra0OtZUHjW7or) * Select one of the four options and click **SAVE AND** **USE** button to add the signature to the document. ![](/files/jcR00lP6fqPUTUQ0DuCV) {% hint style="info" %} **SAVE AND USE** This feature saves your signature or the initial, which can be reused for future documents that will be signed through Evia Sign. {% endhint %} ### **Completing the document** Once you have filled the requested stamps in the document. * Click the **COMPLETE** button. ![](/files/T1XJTQa6LA2oxXopWqEt) * This action will produce a popup message confirming that you have completed and signed your document. ![](/files/2wrHMyqLquKKKThR408u) {% hint style="info" %} Once all relevant signatories have completed signing copy of the completed document will be sent to your email. {% endhint %} ## Quick Navigation {% content-ref url="/pages/sZAorlgITD018WU7W1nI" %} [Opening a document through Evia Sign inbox](/how-to-sign-documents/opening-a-document-through-evia-sign-inbox) {% endcontent-ref %} {% content-ref url="/pages/nayGruXtFF79YIBt4FsR" %} [Explore the different ways to add your signature](/how-to-sign-documents/explore-the-different-ways-to-add-your-signature) {% endcontent-ref %} {% content-ref url="/pages/S9eoeDytUCiIqUs7SFPu" %} [How do you decline a document?](/faqs/how-do-you-decline-a-document) {% endcontent-ref %} {% content-ref url="/pages/KBwWggc30tsfZNpzqF1p" %} [How do you download a document?](/faqs/how-do-you-download-a-document) {% endcontent-ref %} # Opening a document through Evia Sign inbox You can also open the requested document through Evia Sign Inbox. * Go to your Evia Sign Inbox and click on the required document. ![](/files/etEo13vqEKkZI3lvHehv) * Click on the **SIGN** button to open and sign the document. ![](/files/jlBZyCzowSY8aU6WZ8do) * You can also directly click on the **SIGNATURE** icon to open and sign the document. ![](/files/GGkJfrTlL5v2THoIdh0M) ### # Explore the different ways to add your signature ### **Signing through pre-determined signature font styles** * Click the **Type** option and enter your name in the provided space. ![](/files/8xoIxQS88C3RCzsLqj8A) * This action will generate a bunch of pre-determined signature font styles, select one of these options to proceed. Click **SAVE AND USE**. ![](/files/XiYOGkl8X2YllYag8zov) ### **Signing through your mobile phone** * Click on the **From Mobile** option. * Scan the QR code displayed on the screen that will generate a URL on your QR code scanner application. ![](/files/VreJFnGNbPp3SRun1ZbR) * Click on the URL to get directed to a whiteboard where you can draw your signature using your mobile screen. ![Choose one of the three colors (red/black/blue) to draw your signature.](/files/HSZY2SBxUPdE3udynOfT) * If you choose to re-draw your signature, you can click on the **CLEAR** button at the bottom of your mobile phone and re-draw your signature and finally, click **SAVE AND USE**. . ![](/files/Qy9KZJMIKR6Lvt2lQICJ) ![](/files/VdYjrvRSFROUo5fM0yb6) * This action will produce a popup message confirming the successful addition of your signature.
* This process will upload the signature from the whiteboard of your mobile screen and replace it with the QR code on the ADD SIGNATURE dialogue box. If you wish to alter your signature, click the CLOSE icon on the ADD SIGNATURE dialogue box and reupload another signature through your mobile phone, following the same process.
### **Drawing your signature** * Click **Draw** in the ADD SIGNATURE dialogue box and choose one of these three colors (red/black/blue) to draw your signature. ![](/files/uaqBGnuiFfslclbUk1jX) * You can also increase or decrease the thickness of your signature by adjusting the size scale. ![](/files/onloWUs9PNxp7e8h8z9c) * Draw your signature on the space provided in the ADD SIGNATURE dialogue box. Click **SAVE AND USE.** ![](/files/XRxJpGkglTYbietO6ceC) * If you choose to re-draw your signature, you can click on the CLEAR button at the bottom of the ADD SIGNATURE dialogue box and re-draw your signature. ![](/files/EqLMAGS9ToGEEdzWDmpk) ### **Uploading a file with your signature** * Click **From File** in the ADD SIGNATURE dialogue box and click Upload a file to upload the signature file in the system-supported formats (JPG/PNG/BMP). ![](/files/i6XRCc4ophiU2NdoXiAm) * The upload signature file will appear on the ADD SIGNATURE dialogue box, showcasing a preview of your signature. Click **SAVE AND USE.** ![](/files/uoricwX4gZy6XFemHVuv) * To alter the uploaded file, click the close button on the ADD SIGNATURE dialogue box and reupload another file with your signature following the same process. ![](/files/jsZoYZYitiAzzBA2QHNl) {% hint style="info" %} To fill in your initials, utilize the same procedures as the signature alternatives. {% endhint %} # How to draft documents? You can cancel out the sending process of your documents at any point and save them as draft documents in Evia Sign. ### **Saving draft documents** * To save documents as drafts, click the **CANCEL** button at the bottom of your screen at any point of the document sending process. * This action will produce a pop-up message providing you with the option to save the document as a draft. Click **YES** to proceed. ![](/files/2dHCFNbhqZe3iUvK3yPt) * Once the document is saved successfully as a draft, the system will provide a **Success** pop-up message. ![](/files/OdqGJi9P5PO1Fw3BEi5O) ### **Sending a saved draft document** The DRAFTS section of the Evia Sign home screen contains all the drafted documents. * Go to your Evia Sign home screen and click **DRAFTS** on the side menu. ![](/files/nqRHuCMJVsbgV7SYdsq4) * Click on the draft document you need to utilize to upload it back to the document sending process. You can now start your process of sending the document from the point where you left the last time, following the procedures. ![](/files/rDpHKApY2LnXMXyuGXxS) ## Quick Navigation {% content-ref url="/pages/eGxCkZV3DXTmtCaZvYhI" %} [Components of DRAFTS in Evia Sign](/how-to-draft-documents/components-of-drafts-in-evia-sign) {% endcontent-ref %} # Components of DRAFTS in Evia Sign ### **Title** The Title column in the Evia Sign drafts represents the names of the drafted documents. Below the document name, you can also view the name of the user who prepared the draft. ### **Last Activity** The Last Activity column in the Evia Sign template represents the date and time most recently used to work and the most recent activity on the document. ![](/files/nOBcy994PRpGz1pNx8Pk) ### **Search and filtration of the draft documents** You can search the required draft documents by clicking on the tags at the top of your screen. ![](/files/VE1BxF1UmUQcbGJFbLPJ) You can also search the draft documents by directly typing the name on the search bar at the top right corner of your screen. ![](/files/LAbwd3GSw1YKj6qxIVTw) # Explore Evia Sign Inbox Evia Sign inbox performs the same functionality as any inbox mechanism that you would have come across. It works as a hub where all documents sent and received through Evia Sign are organized. The following are the six tabs of Evia Sign: {% tabs %} {% tab title="Waiting for Me" %} This tab contains all the documents sent within the organization or from other organizations that request your signature and the documents that need to be self-signed. {% endtab %} {% tab title="Waiting for Others" %} This tab contains all the requested documents waiting for the signature of the relevant signatories. {% endtab %} {% tab title="Requested by Me" %} This tab contains the document you sent to the signatory(s) or yourself to be self-signed which commonly works as mailed items or outbox. {% endtab %} {% tab title="Completed" %} This tab contains the documents you have completed and signed and the documents requested by you that are completed and signed by the other signatories. {% endtab %} {% tab title="Declined" %} This tab contains the documents you have declined and the documents you have requested that are declined by the other signatories. {% endtab %} {% tab title="All" %} This tab collectively stores all the documents from the other Evia Sign inbox tabs. {% endtab %} {% endtabs %} ## **More about Evia Sign Inbox components** Components of the Evia Sign inbox table: ### **Title** The Title column in the Evia Sign inbox represents the document name. Below the document name, you can also view the document sender's name. ### **Status** The Status column in the Evia Sign inbox represents the most present status of the document. The following are the statuses and the respective color codes. | Status | Color | | -------------------------------- | ----------------------------------------- | | Waiting for Me | Orange | | Waiting for Others | Purple | | Completed by all the signatories | Green | | Completed by you | Purple | | Declined | Red | | Recall | Red | ### **Last Activity** The Last Activity column in the Evia Sign inbox represents the date and time most recently used to work on the document. Below the date and time, you can also view the activity performed on the document. ![](/files/xtN3X4ZHrk4Wjnhq04j2) ### **Search bar** You can search the required documents by directly typing the name on the search bar at the top right corner of your screen. ![](/files/qc4fh6lJhpMl6GJuZBeL) ### **Document Previewer and Document Sign buttons** The document previewer button on the table allows you to preview the document. * Click the **DOCUMENT PREVIEWER** button to view the document. ![](/files/SXODXXF4sAn7jMAUoCtK) The document sign button on the table allows you to sign the document directly from your Evia Sign inbox. * Click the **DOCUMENT SIGN** button to sign the document from your Evia Sign inbox. ![](/files/6XsWgh1UjWk5SKLCOFnU) ### **The expandable feature of the document details** Clicking on a document in Evia Sign Inbox will unwrap the document details in an expandable manner. ![](/files/nMMNytovAFEXzKHn2REt) **If you click on the document with the status, Waiting for Me, you can view:** * Minimized preview of the document. * The message sent along with the requested document * Latest activity on the document. * The signatory(s) and their current activity on the document (Signed/Pending) * You will also find the DECLINE and SIGN THE DOCUMENT button to proceed forward with the document. ![](/files/SasLFjIwLpfdCQvaMpfP) **If you click on the document with the status, Waiting for Others, you can view:** * The message sent along with the requested document * Minimized preview of the document. * Latest activity on the document. * The signatory(s) and their current activity on the document (Signed/Pending) ![](/files/QpFdZO8qJXJNSISx5Esi) **If you click on the document with the status, Completed, you can view:** * Minimized preview of the document. * Document requested date * Latest activity on the document. * The signatory(s) that has signed the document ![](/files/5E8n9qCSg3ibeDQbZGzh) **If you click on the document with the status, Declined, you can view:** * Minimized preview of the document. * Document requested date * Latest activity on the document. * The signatory who has declined the document along with the reason. ![](/files/VybNOQeluqzokvYb1xCa) **If you click on the document with the status, Recalled, you can view:** * Minimized preview of the document. * Document requested date * Document recalled date * The reason for the recall action
# How to create and use templates Templates are pre-made documents containing a pre-determined design layout and other essential elements. You can create your templates through Evia Sign and share them frequently in the future course of the work processes. ## **Creating Templates** Follow the procedures outlined below to create templates: * Go to your Evia Sign home screen and click **TEMPLATES** on the side menu. This action will direct you to the Templates section of Evia Sign.
* Click the **New Template** tile to get started on the template-creating process.
### **Document upload** * You can provide the details of your template under ADD TEMPLATE DETAILS section of the screen, such as the **TITLE** and the **DESCRIPTION** of the template and click NEXT.
* Click on the **BROWSE** button and choose a file in the supported format (PDF/DOC/DOCX) or simply drag and drop the document onto the dotted rectangular space. * You can also upload a document through your OneDrive cloud account.
* To proceed to the next step, click **NEXT.** ### **Adding a role** The ADD ROLE section serves the option to identify the signatory(s) of the template based on a specific role. Ex: Human Resources, Finance, etc. * Type the role of the signatory(s) in the **ROLE** text box. * Next, type the signatory name followed by the email address in the provided space. You can add multiple signatories by clicking the **PLUS** button and following a similar process. Once done click **NEXT**.
* You can add multiple roles by clicking the plus button. * Then click **NEXT.** {% hint style="info" %} In a multiple role scenario, you can rearrange the signatory role order by modifying the order number displayed next to the signatory role. {% endhint %} ### **Adding the stamps** Once you have included the relevant signatory role(s) in the template, the following steps involve the configuration of the stamps: * Select the signatory role to whom you want to configure the stamps. * Next, click on the required stamp and click again on the document's specific location where you want it to appear.
{% hint style="info" %} Follow the same for any required stamp of choice. {% endhint %} {% hint style="info" %} To delete a stamp, select the required stamp and click DELETE key on your keyboard or you can right-click on the required stamp and click on the **Delete** option. {% endhint %} * To proceed to the next step, you can click **NEXT**. ### **View template document summary** In the SUMMARY section, you can view a completed template, ready to be saved, inclusive of all the relevant signatory's roles and stamps. This document previewer will allow you to confirm all the elements in the requested documents. You can always go back and edit the document based on your preferences. * You can alter the default title of the document and provide a suitable one by typing a new title in the Document Title textbox. * The Message textbox reserves the space for the construction of the email body. You can type a piece of additional information or any relevant message alongside your template.
* To store your template for potential future usage, click the **SAVE** button. This action will save your template in the **TEMPLATE** section of Evia Sign.
## **Sending templates** The TEMPLATE section of the Evia Sign contains all the template documents. * Go to your Evia Sign home screen and click TEMPLATES. * Select the template document you need to utilize and click USE.
{% hint style="info" %} Any default value that you provide throughout the template creation process can now be modified, such as *Template, Role, Stamps and Document Details.* {% endhint %} {% hint style="info" %} You can also set up authentication and type the private message to your signatories. {% endhint %} * Once your document is ready to be sent, click **SEND** to deliver the template document to the relevant signatory(s).
## Quick Navigation {% content-ref url="/pages/adukBrxBGugUt03j0f0V" %} [Broken mention](broken://pages/adukBrxBGugUt03j0f0V) {% endcontent-ref %} {% content-ref url="/pages/X2A7itmg2jr9mYOHQkRY" %} [Components of TEMPLATES](/how-to-create-and-use-templates/components-of-templates) {% endcontent-ref %} # Components of TEMPLATES ### **Search and filtration of the draft documents** You can search the required draft documents by clicking the tabs at the top of your screen. {% tabs %} {% tab title="My Templates" %} This tab contains all the templates that you have prepared through Evia Sign. {% endtab %} {% tab title="Shared with Me" %} This tab contains all the templates shared with you. {% endtab %} {% tab title="Shared by Me" %} This tab contains all the templates shared by you. {% endtab %} {% tab title="All " %} All the templates from the other tabs are stored collectively on this tab. {% endtab %} {% endtabs %} **Search Bar** You can also search the template documents by directly typing the name on the search bar at the top right corner of your screen.
# How to save your signature and initial? With Evia Sign, you have the option to store your signature and initial in the system and make further modifications to it as needed. To save your signature, follow the procedures outlined below: * Go to your Evia Sign home screen and click **MY SIGNATURE** on the Evia Sign side menu. This action will direct you to the MY SIGNATURE section of Evia Sign. ![](/files/9DOQiEfffveE04Jkda22) * Click **ADD SIGNATURE** button. This action will provide a dialogue box with four options to store your signature, s*igning* by c*hoosing a pre-determined signature font style generated by Evia Sign, signing with a mobile device, drawing your signature, and uploading a file with your signature.* ![](/files/dQz9H0MVo0SLV10qKV4h) ![](/files/3atWETYc3VX0LICDTJAY) * Once you have selected one of the four options to sign the document, click **SAVE AND USE**. ![](/files/Vf6yrrqdqYrkXTJ5GdHY) {% content-ref url="/pages/nayGruXtFF79YIBt4FsR" %} [Explore the different ways to add your signature](/how-to-sign-documents/explore-the-different-ways-to-add-your-signature) {% endcontent-ref %} To save your initials: * Click **ADD INITIAL** button. ![](/files/96Yp94PU3kLk1b2baHIQ) * This action will provide an **ADD INITIAL** dialogue box with four options to store your initials. ![](/files/g12rfCXpbEcOsy3UHZsz) * Once you have selected one of the four options, click **SAVE AND USE**. ![](/files/DMEpfrvo188vvZdMxzwC) {% hint style="info" %} To store your initials, utilize the same procedures as the signature alternatives.
{% endhint %} * Once you have saved your SIGNATURE AND INITIALS, you can store them for future utilization. ![](/files/l947T99FFkof7WQlD2YS) # How to add date stamp to your signature? You can customize your signatures with date stamp. Follow the procedures outlined below: * Go to your Evia Sign home screen and click on the "Settings" tab.
* Then, select "Settings.
* In the "Signature Settings" section, you can customize your signature with a date stamp. To do this, choose the "add with date stamp" option, and then click on "SAVE CHANGES."
* From now on, when you add your signature, you will see the date stamp below your signature.
# How to set up automatic reminders & expiration for signature requests ## Overview Evia Sign allows administrators to automate reminders for pending sign requests and set expiration dates to ensure timely document completion. This guide walks you through configuring these settings to maintain efficiency and compliance. ## Accessing Reminders & Expiration Settings For Admin Users Start by logging in to your **Evia Sign admin account** and click on **Settings** from the main menu.
Navigate to the **Reminders & Expiration** section.
### Configuring Automatic Reminders Admins can enable automatic reminders to notify signers at set intervals until they complete the signing process. Locate the **Automatic Reminders** check box and **enable** automatic reminders
Configure the following options: * **Days before the first reminder**: Set the number of days after the initial sign request before the first reminder is sent.
* **Interval between reminders**: Define how frequently reminders should be sent after the first one.
### Setting Up Expiration Dates Sign requests can be configured to expire if not completed within a specified timeframe. Locate the **Sign Request Expiration** check box and **enable** sign request expiration.
Set the following parameters: * **Days before sign request expires**: Define how long the sign request remains active before expiring.
* **Days to warn signers before expiration**: Set the number of days before expiration when signers will receive a final warning notification.
### Overriding Admin Settings (Optional) By default, all sign requests under an admin follow the settings configured above. However, admins can allow individual request senders to override these values. Locate the **"Allow senders to override account defaults"** toggle.
**Enable** this option if request senders should have the flexibility to modify reminder and expiration settings for their specific requests.
{% hint style="info" %} **If this toggle remains disabled, all requests will strictly follow the admin-defined values.** {% endhint %} ### Saving Changes Once all settings are configured, the admin must click **Save Changes** to apply the modifications.
## Accessing Reminders & Expiration Settings for Users Under an Admin When sending a signature request, users under a specific admin will be able to see the **preset document request reminders and expiry settings** defined by the admin during the fourth step of the signature request process.
If the admin has enabled the **"Allow senders to override account defaults"** option, users will have the ability to customize their own reminder and expiry settings for individual requests.
> **However, if this option is disabled, the settings applied to all requests will strictly follow the admin’s predefined values.** This ensures that admins maintain control over document workflows while allowing flexibility where necessary. # Users Through Evia Sign, you can invite new users and share the digital signing experience. ## Creating New Users Follow the procedures outlined below to create new users: * Go to your Evia Sign home screen and click on the **Settings** tab.
* Select the **Users** tab. This action will direct you to the Users section of Evia Sign.
* Click the **+NEW USER** dropdown menu from where you can select Create new user
* Enter the **First Name**, **Last Name**, and **Email** of the relevant user added to the system and click **Save**.
# How to import O365 users? ## Importing Users Follow the procedures outlined below to import users: * Go to your Evia Sign home screen and click on the **Settings** tab.
* Select the **Users** tab. This action will direct you to the Users section of Evia Sign.
* Click on the dropdown menu of the **+NEW USER** and select Import O365 users.
* This action will load your active directory list of O365 users from which you can select the users you wish to import by checking the boxes and clicking the **Import** button.
# How to add new users? Follow the procedures outlined below to add new users: * Go to your Evia Sign home screen and click on the **Settings** tab.
* Select the **Users** tab. This action will direct you to the Users section of Evia Sign.
* Click on the dropdown menu of the **+NEW USER** and select Create new user.
* Then add the First Name, Last Name and the Email of the new user and click on the Add button.
# How to delete users? To delete a user, follow the procedures below: * Go to your Evia Sign home screen and click on the **Settings** tab.
* Select the **Users** tab. This action will direct you to the Users section of Evia Sign.
* From the list of the existing users, click on the three dotted menu of the user you want to delete and click on the **Delete** button.
* Finally confirm the deletion process by clicking **Yes.**
# How to activate and deactivate users? # How do I change the current subscription plan of my account? You can change your Evia Sign subscription plan at any anytime. Follow the procedures outlined below to alter your subscription plans: * Click on the Settings tab on the Evia Sign home screen and then on the **Account** dropdown, from which you can select the **Billing** tab.
* .This action will provide the specifics of your current subscription plan, payment method used, billing information, and invoice history.
* Moving forward, you can upgrade or downgrade your current subscription package based on your requirements. ### Subscription Upgrade * Click the **Update Plan** option to upgrade your subscriptions from the Personal to the Professional plan.
* You will now be able to access the purchase module. Here you can select **Monthly** and **Yearly** options and the plan of choice.
* .If you have decided to upgrade your plan with a professional package, you can also select the number of users you require.
* Next, click the **Continue** button to proceed.
* Finally, click the **Confirm** button.
### Subscription Downgrade * Click the **Update Plan** option to downgrade your subscriptions from the Professional to the Personal plan.
* You will now be able to access the purchase module. Here you can select **Monthly** and **Yearly** options and the plan of choice and downgrade your current subscription plan by clicking the **Continue** button.
* Finally, click the **Confirm** button to proceed.
# How to cancel and renew plan? ### **Cancel plan** As an account admin, you can terminate your subscription plan anytime. To do this, follow the procedures below: * Click on the Settings tab on the Evia Sign home screen and then on the **Account** dropdown, from which you can select the **Billing** tab.
* Click on the **Cancel Plan** button.
* Here you will find the details of the plan you are canceling and the end date of the billing cycle until which the plan will remain active. Confirm the cancellation by clicking on the **Cancel Plan** button.
{% hint style="info" %} This action will cancel your plan, and you can keep using it until the end of the billing cycle. If you want to continue the plan, you can always reactivate it during this period. {% endhint %} ### **Renew plan** To renew the plan, follow the procedures below: * Click on the Settings tab on the Evia Sign home screen and then on the **Account** dropdown, from which you can select the **Billing** tab.
* Click on the **Renew Plan** button.
* Here you will find the details of the plan you are renewing and the renewal date. Confirm by clicking on the **Renew Plan** button.
{% hint style="info" %} Now you can continue with your subscription plan. {% endhint %} # How do I purchase additional user licenses? In Evia Sign, you can add more users once you have activated a professional subscription plan, and depending on the user licenses purchased, you will be charged an additional amount. {% hint style="info" %} If you have activated a yearly professional subscription plan and purchased new user licenses in the middle of the year, you will only be charged for that period and not the whole year. The following billing cycle will include the annual cost for the new user licenses. {% endhint %} To add more users to Evia Sign, follow the procedure below: * Click on the Settings tab on the Evia Sign home screen and then on the **Account** dropdown, from which you can select the **Billing** tab.
* Click the **Update plan.**
* Then, click the plus**(+)** icon of your current Evia Sign professional plan and increase the number of additional user licenses required for purchase.
* Next, click continue to proceed.
* Finally, click the **Confirm** button to proceed.
# How to work with Enadoc Integration? During the signature request process, you have the option to enable the Enadoc integration. This integration allows you to automatically send the uploaded documents to a designated document library in your Enadoc account once the signing process is completed and all the required signatures have been obtained. To work with Enadoc integration, follow the procedures below: * In the fourth step of the signature request process, navigate to the "CONNECTIONS" section. * Proceed to "SIGN IN" to access your Enadoc account. * You can now begin configuring the document by selecting a tag profile from the available options. * This action will automatically populate the corresponding library associated with the selected tag profile. * Finally, you can fill out the Document References fields pre-defined for the specific document library. Once completed, click the "SEND AND ARCHIVE" button. * You can complete the signature request process by clicking the "Send" button. Once all the signatures are obtained on the document, it will be automatically routed to the designated document library. # Terms to be familiar ### **Signatory** Signatory(s) in Evia Sign refers to a single person or group of people who have signed or will be signing a legal business document. ### **Evia Sign stamps** Evia Sign contains five stamps: * Signature * Initial * Date Signed * Name * Email These stamps indicate the place of e-signature, initials, name, email address, and the date of e-signature to the signatory. The sole intention of these stamps is to ensure efficient communication and provide clear instructions to the signatory. ### **Draft documents** The draft documents indicate a legal document in its preliminary form and utilized in the future course of the work processes. ### **Templates** Templates are pre-created documents containing a pre-determined design layout and other essential elements. These documents can be saved in Evia Sign and can be used frequently in the future course of the work processes. # FAQs The most frequently asked questions about Evia Sign are answered here for your convenience. {% content-ref url="/pages/dq31AboyXUp9CShLRYVJ" %} [How to login into Evia Sign?](/faqs/how-to-login-into-evia-sign) {% endcontent-ref %} {% content-ref url="/pages/7X2IpEs6b8vrDaxnb5yL" %} [How do I make an account recovery?](/faqs/how-do-i-make-an-account-recovery) {% endcontent-ref %} {% content-ref url="/pages/YLMqrNYOc7zSLBaDDGnX" %} [How do you configure stamps?](/faqs/how-do-you-configure-stamps) {% endcontent-ref %} {% content-ref url="/pages/TrmufdnawnFduQSHczXE" %} [How do you add authentication to your request?](/how-to-send-signature-request/how-do-you-add-authentication-to-your-request) {% endcontent-ref %} {% content-ref url="/pages/XjQEqEuCafMYMbWDg6jb" %} [How do you send a private message?](/how-to-send-signature-request/how-do-you-send-a-private-message) {% endcontent-ref %} {% content-ref url="/pages/xeMFRoljgPXcFJohWdEF" %} [How do you manually send reminders to signatories?](/faqs/how-do-you-manually-send-reminders-to-signatories) {% endcontent-ref %} {% content-ref url="/pages/yQQfvGaL9rzV2x0OzMFL" %} [How do you view document history?](/faqs/how-do-you-view-document-history) {% endcontent-ref %} {% content-ref url="/pages/S9eoeDytUCiIqUs7SFPu" %} [How do you decline a document?](/faqs/how-do-you-decline-a-document) {% endcontent-ref %} {% content-ref url="/pages/KBwWggc30tsfZNpzqF1p" %} [How do you download a document?](/faqs/how-do-you-download-a-document) {% endcontent-ref %} {% content-ref url="/pages/G5QBgx15s5zOX3FTRuka" %} [What is a digitally certified document?](/faqs/what-is-a-digitally-certified-document) {% endcontent-ref %} # How to login into Evia Sign? ### **Log in with username/email address and password** The first and foremost step in sending an electronic document to a signatory requires providing the authenticated credentials (email/username and password) to log in to the Evia Sign system. To proceed into the system, follow any of the two steps below: * Enter a valid **email/username** and **password**. ![](/files/s1zbJT4oVRRhtoB8Jodn) * Click **Login** to be directed into the Evia Sign system. ![](/files/RUGCLgS3zY1mDg9mIz1M) ### **Login with O365 account** If you already possess an O365 account: * Click **Sign in with O365** to be directed into the Evia Sign system. ![](/files/8t5xycdKWMuxYrPfZuAx) * Either of the above options will provide you with access to Evia Sign. ![](/files/c03js1g4c8YDYZmmb7at) # How do I make an account recovery? **In a scenario of a forgotten password:** * Click ***Can't access your account?*** ![](/files/pArs2T9cUfgTwGtr8TdL) * This action will direct you to the **Account Recovery Page**. You can add an email address in the space provided to which you want the verification code sent by Evia Sign. * Click **Send Verification Code** this action will send a system-generated verification code to the provided email address. ![](/files/qcHqD7rVwGjQTVGHJOH1) * Type the verification code in the provided space, and click **Next**. ![](/files/IoMBP2I0zPw5OrWMkcPK) * Now create a new password and confirm it by entering the new password one more time. Finally, click **SAVE**. ![](/files/sBlFIEHgxlOtFqGCtUKn) * This action will generate a message confirming the password has been reset; click **Go to login**. ![](/files/f4ntcPhFoJBq8XSzi8zr) * Enter the email/username along with the new password and click **Login**. ![](/files/vuWmCOqlbdD3raFE2P1Z) * This action will successfully direct you to the Evia Sign. ![](/files/c03js1g4c8YDYZmmb7at) # How do you configure stamps? ### **More information about the stamps:**
Signature *This stamp will specify the space in the document where a signatory is supposed to place their signature in the requested document.*
Initial *This stamp will specify the space in the document requested where a signatory is supposed to place their initials.*
Date Signed *This stamp will be autogenerated based on the date a signatory places the signature on the requested document.*
Name *This stamp will be auto-generated by the system based on the signatory name specified in the **SIGNATORY*** *section of the document sending process.*
Email *This stamp will be auto-generated by the system based on the signatory email specified in the **SIGNATORY** section of the document sending process.*
### **More stamp related actions:** {% hint style="info" %} To change the position of a stamp: Select, and drag and drop stamp in the required position on the document. {% endhint %} {% hint style="info" %} To resize a stamp: Select one of the handles of the stamps and drag until it reaches the size you want. {% endhint %} # How do you manually send reminders to signatories? Once you have sent a document to the signatory(s), you can send occasional reminders on the pending signatures. Follow the outlined procedures. * Choose the file from the **Requested by Me** tab that needs to receive the reminder and click on the expanded view option. ![](/files/qWfqiRxgq1ejrZ4J8rGw) * In the signatory section, click on the kebab menu on the signatory to whom you want to send the reminder. Click **Send** **Reminder.** ![](/files/ghIUgO5WhNivIyAvhTgR) * This action will provide a dialogue box with the Name, Email ID of the signatory. Type your reminder message and click **SEND**. ![](/files/hx5aS2DbEd3KLA0V1fiM) # How do you view document history? * Select the document to be signed or sent for a request by clicking on it. ![](/files/oJpCnEzicmIWKleoccfg) * Select **VIEW HISTORY** to view the history of the document. ![](/files/8ghtKslO36D3UWHuUEUa) # How do you decline a document? If you face any disagreements with the document requesting your signature, you can always reject it via Evia Sign. * Click the **DECLINE** button from the dropdown at the top of your screen. ![](/files/SQ9qOqU2JCCQLhb681cB) * This action will open a **DECLINE REQUEST** dialogue box to confirm your declination with a reason. * Type your document declination reason in the provided space and click the **DECLINE** button. ![](/files/jW50eYTq66ERDZVjobDF) * This action will produce a popup message confirming that you have declined your document. ![](/files/wUycY457B4c7qjcbZ7CT) # How do you download a document? When a document is completed or declined, each signatory will receive a copy of the signed or the declined document to the respective email. To download a completed or declined document, follow the procedures below: * Click on the email where you have received a copy of your signed or declined document, and click the **VIEW DOCUMENT** button to access it through the Evia Sign Previewer. ![](/files/pSZKG4N0hylXjrQvf70R) You can also download the completed or the declined documents through the Evia Sign inbox under the Completed or Declined tabs. Follow the procedures outlined below: * Go to your Evia Sign Inbox and click the **Completed** or the **Declined** tabs based on your requirement. * Click the **Document Previewer** button to access the document through Evia Sign Previewer. ![](/files/4i62NbyOvgkB1SSnAscu) * Click the **DOWNLOAD** button at the top of your screen to download your document. ![](/files/s0JprjalSmKt0xGORuKw) # What is a digitally certified document? ### **What is a digitally certified document in Evia Sign?** In Evia Sign, documents that have been digitally certified are those that are electronically signed using an AATL-compliant certificate. ### **How do I confirm that my documents are signed digitally with an AATL-compliant certificate?** The digital certificate badge alongside the Evia Sign Document ID at the top of the document confirms that your documents are digitally signed. Hover over this badge to display the message "This document has been digitally certified by Enadoc."
### **What does it mean when a document is digitally signed?** The document is sealed and shielded from unauthorized alterations when signed digitally with a certificate that complies with the AATL standards. If any unauthorized modifications occur to the document, the Acrobat Reader will instantly detect it and alert the user. To analyze your document, follow the procedures outlined: * Use Acrobat Reader to view the finished and downloaded document.
* At the top of the document, you can see the information related to the digital certificate's integrity and authenticity.
* To view more information, click the **Signature Panel** button.

Detailed information on the digital certificate

# How are additional user licenses purchased? You can purchase additional user licenses for your **professional subscription** **plan** whenever necessary. Follow the procedures outlined below: * Click on the **Settings** tab on the Evia Sign home screen and select the **Billing** tab. * Click the **Change Plan** option to access the purchase module. * You can provide your personal information. * In the **Selected Plan** section, on the **Total Users** section, utilize the **+** option to purchase additional user licenses and click on the **GET STARTED** button. * You can provide your payment and billing information. * Finally, click the **CHECK OUT** button to proceed. # How do you send reminders to signatories? Reminders can help you remind your signatories of the signature request. * Go to your Evia Sign **Inbox**. * Click on the **Waiting for Others** tab and select the document sent for signature request. * Click on the three-dotted menu icon and select the **Send Reminder** option. * Type the reason for the reminder in the provided space and click **SEND**. # How to modify your session duration? Begin by navigating to the Settings tab.
From there, select the Settings option. Locate the Security Settings section, where you will find the option to adjust the Session Timeout duration.
After making the desired changes, do not forget to save your modifications by clicking on the Save Changes button.
# How do I monitor the request usage of my Evia Sign account? ### What is a request usage? It is a feature of Evia Sign that showcases the percentile of completed signature requests, also known as the Request Usage. {% hint style="info" %} ***A signature request is considered completed when all the requested signatories have signed the document.*** {% endhint %} You can monitor and acquire real-time information on your Evia Sign Request Usage by following the procedure below: * Go to your Evia Sign home screen and click on the Settings tab.
* Next, click on the Account dropdown, from which you can select the Usage tab.
* Here you can view the accurate details of the request usage.
### More details on how to read your usage meter in Evia Sign. 1. No requests are completed.
2. The colored area indicates the percentage of request usage.
3. Request usage is 100% completed or has reached its maximum limit (This is based on the transaction package purchased).
4. Request usage above the set limit (This is based on the transaction package purchased). In this case, a surcharge will be applied for the "request usage" that has exceeded the specified limit.
# Release Notes ## V 2.5.0.3 (9th October 2025) **Overview**\ A maintenance release delivering **UI enhancements** and **bug fixes**. ## V 2.5.0.2 (2nd October 2025) **Overview**\ A patch release with **Contact List enhancements and refinements**. **Highlights** * Enhanced accuracy and display of contact information. * Minor UI and usability improvements. ## V 2.5.0.1 (30th September 2025) **Overview**\ A minor update introducing **UI enhancements** and **general fixes**. **Highlights** * Refined UI components for a cleaner, more consistent interface. * Fixed minor visual and layout inconsistencies. * General usability and stability improvements. ## V 2.5.0.0 (28th September 2025) **Overview**\ This release focused on boosting **system stability, performance, and reliability**. **Highlights** * Optimized backend processes for faster performance. * Improved system responsiveness and reduced load times. ## V 2.4.0.1 (04th September 2025) #### Fixes * UI Enhancements and bug fixes. ## V 2.4.0.0 (02nd September 2025) New Feature – Archive * Introduced a new **Archive** section for better organization. * All **completed, declined, or recalled requests older than 30 days** will automatically move to the Archive. * Keeps the Inbox clean while ensuring easy access to past records. * Added **one global search** that covers everything – results now include both **Inbox and Archive**. #### Improvements * Enhanced overall system performance and stability. * Enhanced search. #### Fixes * UI Enhancements and bug fixes. ## V 2.3.0.1 (26th August 2025) Fixes UI Enhancements and bug fixes. ## V 2.3.0.0 (20th August 2025) New Feature – Outbox for Signed Requests * Introduced a new **Outbox** in Evia Sign. * The Outbox is visible only when signed requests require processing, and those requests automatically move to the Inbox once processing is complete. * This gives users better visibility and tracking of request progress. Improvements * Enhanced performance and stability. * Improve scalability and reliability. ## V 2.2.0.0 (10th August 2025) #### Overview This update improves the system’s overall performance and reliability. Users can expect a smoother, more consistent experience. * UI enhancements and bug fixes. * Improved overall system speed and reliability, ensuring a smoother and more consistent user experience. ## V 2.1.1.1 (09th May 2025) **Fixes** UI Enhancements and bug fixes ## V 2.1.1.0 (05th May 2025) **Features** * **Added a new security setting to enable OTP authentication for all external users**, with configurable OTP delivery options including Email, SMS, or both. **Fixes** * UI Enhancements and bug fixes ## V 2.0.0.0 (28th February 2025) **Features** * **Fresh, Sleek Look** – A cleaner inbox and better document tracking * **Smarter Contact Book** – Auto-suggests past signatories and team members * **More Control Over Signing** – Set signing order and predefined actions with ease * **Document Commenting** – Evia Sign now lets users add, manage, and reply to comments on documents during signing, with visibility controls and email notifications for seamless collaboration. **Fixes** * UI Enhancements and bug fixes ## V 1.23.0.0 (27th September 2024) **Feature** * Implemented the tenant deletion feature, which permanently removes all associated users, data, and documents. This action is irreversible, and once completed, recovery is not possible. **Fixes** * UI Enhancements ## V 1.22.0.0 (13th September 2024) **Features** * Implemented New Brand Guidelines in Evia Sign UI * Signing request will be sent to CC recipients' inboxes only once after the signing process is completed and they will also receive the completed document with a link to access **Fixes** * UI Enhancements and bug fixes ## V 1.21.1.0 (16th August 2024) **Enhancement** * Updated Template UI with the latest viewer **Fixes** * UI Enhancements and bug fixes ## V 1.21.0.0 (26th July 2024) **Feature** * An Admin user of Evia Sign is able to view a comprehensive dashboard that displays the status of all signature requests **Enhancement** * Enhancements in Audit Trail **Fixes** * UI Enhancements and bug fixes ## V 1.20.0.0 (12th July 2024) **Feature** * The request initiator is now able to edit recipients after sending a signature request **Fixes** * UI Enhancements and bug fixes ## V 1.19.0.0 (20th June 2024) **Features** * Users have the flexibility to send signature requests either sequentially or in parallel or both. * Audit Trail Enhancements-The audit trail will display a record when an OTP is sent/verified to a recipient. **Fixes** * UI Enhancements and bug fixes ## V 1.18.0.0 (03rd June 2024) **Feature** * Signature Request Path with User Guide. **Fixes** * UI Enhancements and bug fixes ## V 1.17.1.0 (30th May 2024) **Enhancements** * OTP popup notification is added with the phone number and the email address. * AI summary enhancements. **Fixes** * UI Enhancements and bug fixes ## V 1.17.0.0 (16th April 2024) **Features** * Email Delivery Status for Signing Requests Sent to Recipients. * AI summarization. **Fixes** * UI Enhancements and bug fixes ## V 1.16.0.0 (19th April 2024) **Features** * In sequential signing, only the signed signatories and the person who declined will receive notifications, about the declined reason for the signature request document. In parallel signing, all signatories, regardless of whether they have signed the document or not, and the declined person, will receive the declined reason simultaneously. * The admin users can modify the size of the signature for the text type signature. **Fixes** * UI Enhancements and bug fixes ## V 1.15.0.0 (15th December 2023) **Feature** * Multiple signers can collaborate and sign documents in parallel, regardless of their position in the queue **Enhancements** * Enhancements done in mobile view **Fixes** * UI Enhancements and bug fixes **Known issue** * Document ID has displayed incorrectly for specific documents ## V 1.14.1.0 (17th November 2023) **Feature** * Session timeout **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently in mobiles ## V 1.14.0.1 (20th October 2023) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently in mobiles ## V 1.14.0.0 (06th October 2023) **Features** * Add approvers to sign requests * Add CC to sign requests **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently in mobiles ## V 1.13.1.0 (22nd September 2023) **Feature Enhancement** * Inbox Update: Pop-up notifications for new sign requests **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently in mobiles ## V 1.13.0.1 (08th September 2023) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently in mobiles ## V 1.13.0.0 (25th August 2023) **Feature** * Add timestamp to Signature stamp under settings section, so that can see the date signed that document **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently in mobiles ## V 1.12.7.0 (12th August 2023) **Feature Enhancements** * Enadoc integration – enabling for multiple documents * Request delete enhancements **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently in mobiles ## V 1.12.6.0 (26th July 2023) **Feature Enhancement** * Sign from mobile QR code enhancement **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently in mobiles ## V 1.12.5.0 (15th July 2023) **Feature Enhancement** * Inbox loading performance improvements **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently in mobiles ## V 1.12.4.1 (06th July 2023) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently in mobiles ## V 1.12.4.0 (30th June 2023) **Feature Enhancement** * PDF previewer enhancements **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently in mobiles ## V 1.12.3.0 (27th June 2023) **Feature Enhancement** * Document viewer performance enhancement **Fixes** * UI Enhancements and bug fixes * Some landscape pages with images in some documents may not be visible intermittently in desktops **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently in mobiles ## V 1.12.2.0 (26th June 2023) **Feature Released** * Attachment of the audit trail to the completed email. **Feature Enhancement** * Sending user directly to PDF previewer from email **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently ## V 1.12.1.1 (23rd June 2023) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently ## V 1.12.1.0 (16th June 2023) **Features** * Download the completed document and audit trail in different combinations of files * Enadoc integration is enabled for the documents uploaded in the signature request process. **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents * Some landscape pages with images in some documents may not be visible intermittently ## V 1.12.0.2 (12th June 2023) **Fixes** * For an annual personal account, the document count will automatically reset to 0/10 at the beginning of each renewal month until the end of the plan * Responsiveness improvements are added for multiple screen resolutions * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents ## V 1.12.0.0 (02nd June 2023) **Features** * Upload multiple documents for one signature request process * Sign via mobile for multiple documents **Fixes** * UI Enhancements and bug fixes * Contact list – add multiple people with the same name **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents ## V 1.11.0.0 (20th May 2023) **Feature Enhancements** * Limiting stamps count to 200 * Highlighting the pending requests for users **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues with some screen resolutions * Document ID has displayed incorrectly for specific documents ## V 1.10.0.0 (22nd April 2023) **Features** * Transaction basis pricing * Deletion of drafted documents **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues for some screen resolutions * It displays 'Unknown' when the user reuploads previously completed and digitally certified document * Document ID has displayed incorrectly for specific documents ## V 1.9.0.0 (08th April 2023) **Features** * Integration of the billing component with Stripe **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode may have issues for some screen resolutions * It displays 'Unknown' when the user reuploads previously completed and digitally certified document * Document ID has displayed incorrectly for specific documents ## V 1.8.0.6 (09th February 2023) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.8.0.5 (04th February 2023) **New Feature** * Attach the completed document to signature request completed email sending to signatory **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.8.0.4 (28th January 2023) **New Features** * Contact list- give suggestions in request create path * Azure logs **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.8.0.3 (21st January 2022) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.8.0.2 (18th January 2022) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.8.0.1 (11th January 2022) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.8.0.0 (09th January 2023) **Featre Enhancments** * Azure logs​​ * Saving data at the end of request creation path​​ * SignalR issues​​ * Lazyloading​​ * Inbox revamping​​ * Digital certificate issues​​ **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.7.1.10 (06th January 2022) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.7.1.9 (06th January 2023) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.7.1.8 (27th December 2022) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.7.1.7 (23rd December 2022) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.7.1.6 (22nd December 2022) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.7.1.5 (19th December 2022) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.7.1.3 (13th December 2022) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.7.1.2 (10th December 2022) **New Feature** * My signature navigation added to the mobile view **Feature enhancement** * Added 'Do not show again' checkbox to the sign in desktop popup (when using mobile) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents * Declined emails/notifications comes to all other signatories when previous signatory declined the document ## V 1.7.0.1 (06th December 2022) **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.7.0.0 (04th December 2022) **New Features** * Reminder of trial expiry * Request delete * Text field stamp **Fixes** * UI Enhancements and bug fixes **Known issues** * Mobile landscape mode will have issues for some screen resolutions * It shows 'Unknown' when user recompleted previously completed and digitally certified document * Document ID views incorrectly for specific documents ## V 1.6.0.0 (18th November 2022) **New Features** * Trial Expiration * Send manual reminders to signatories **Fixes** * UI Enhancements and bug fixes **Known issue** * Mobile landscape mode will have issues for some screen resolutions ## V 1.5.0.1 (11th November 2022) **Fixes** * UI Enhancements and bug fixes **Known issue** * Mobile landscape mode will have issues for some screen resolutions ## V 1.5.0.0 (09th November 2022) **New Features** * Signature recall * Enadoc Integration enhancements **Fixes** * UI Enhancements and bug fixes **Note** * Enadoc integration works for latest enadoc only * Tag profile default values load in this enadoc enhancement * Upload facility is introduced without considering the user scopes **Known issue** * Mobile landscape mode will have issues for some screen resolutions ## V 1.4.0.0 (27th October 2022) **New Feature** * Enadoc Integration **Feature enhancements** * OneDrive file upload **Fixes** * UI enhancements * Cross tenants' issues and other bug fixes **Known issue** * Mobile landscape mode will have issues for some screen resolutions ## V 1.3.1.2 (14th October 2022) **Fixes** * UI enhancements * Bug fixes **Known issue** * Mobile landscape mode will have issues for some screen resolutions ## V 1.3.1.1 (12th October 2022) **Fixes** * UI enhancements * Bug fixes **Known issue** * Mobile landscape mode will have issues for some screen resolutions ## V 1.3.1.0 (10th October 2022) **Feature enhancements** * Document encryption by using Azure Key Vault encryption **Known issue** * Mobile landscape mode will have issues for some screen resolutions ## V 1.3.0.0 (07th October 2022) **Features** * **Settings Page** o Billing o Users page o Package upgrading * **Templates** o Edit templates **Fixes** * Notification is received correctly but "Review and sign document " button is not clickable (when it is clicked document is not loading) * Need to refresh the inbox to update the status of tuples * Common bug fixes and UI enhancements **Known issue** * Mobile landscape mode will have issues for some screen resolutions ## V 1.2.1.0 (23rd September 2022) **Features** * Templates creation, using templates, delete templates
**Fixes** * Evia Sign logo changes in the application * Responsiveness fixes on web view for different resolutions * UI improvements on Add Signatory step in signature request creation path * Ui improvements on country code is not displaying properly in mobile number field in Configuration step in signature request creation path **Known issue** * Mobile landscape mode will have issues for some screen resolutions. # Evia Sign API # V1 # Overview The Evia Sign API has been introduced to facilitate user access to Evia Sign resources. Users become eligible to submit requests to the Evia Sign API upon the completion of the application registration and authorization processes. The primary goal of the Evia Sign API documentation is to delineate the steps users must follow for application registration, obtaining authorization, and comprehensively outlining the details of Evia Sign API methods to facilitate seamless access to Evia Sign resources. {% hint style="info" %} Access to the Evia Sign API service is restricted to authorized applications only. {% endhint %} The document's scope encompasses the following key components: 1. **Application Registration Process:** This section provides detailed guidance on the process of registering applications for interaction with the Evia Sign API. 2. **Authorization Acquisition:** Users will find comprehensive information on obtaining the necessary authorization to access the Evia Sign API in this section. 3. **API Methods for Accessing Evia Sign Resources:** This crucial section details the specific API methods available for interacting with various Evia Sign resources. # Authorization of the API Access ## Steps to Register a Client Application To initiate the registration of a client application with Evia Sign, the client is required to initiate contact with the Evia Sign team through email. During this communication, the client should provide their designated redirect URL for their external application, which serves as a crucial component for the registration process. Upon successful communication and collaboration with the Evia Sign team, the client's application will be formally registered. Subsequently, the client will receive their unique Client ID and Client Secret, which are essential credentials for authentication and authorization processes. {% hint style="info" %} It is imperative to note that the client's redirect URL, which was initially shared, plays a pivotal role in the overall process. {% endhint %} Following a successful login event, the OAuth code will be returned to the specified redirect URL, facilitating seamless integration and interaction between the client's application and the Evia Sign platform. ### Key Parameters: * `client_id`: The Application ID assigned by the Evia Sign developer team during the registration process. * `client_secret`: The Application Key provided by the Evia Sign developer team for secure access and authentication. * `redirect_url`: The URL specified by the client during registration, to which the OAuth code will be returned upon successful login. ## Obtaining Authorization for Evia Resources To obtain authorization, utilize the assigned client ID and client secret to acquire the authorization URL from the system. When requesting an access token and refresh token, specify the grant type as '**authorization code.**' The resulting access token facilitates access to Evia resources through the Evia API. As this process involves a redirection-based flow, it is imperative that the client possesses the capability to engage with the resource owner's user-agent, typically a web browser. Furthermore, the client should be equipped to receive incoming requests, particularly through redirection, from the authorization server. ### The EVIA-IDENTITY-PROVIDER (EIP) This serves as the central system responsible for furnishing user identifiers for interactions with Evia. EIP takes charge of user authentication, maintaining a comprehensive record of user login details. It also oversees the management of Enadoc organization information and user data. To engage with Evia resources via the Evia API, clients need to possess both the Evia website URL and the EIP URL. This ensures proper access and authentication for seamless integration with Evia services. Refer to the provided image for the Evia Sign SaaS app URL to gain an understanding of the associated EIP URL:

EIP URL

## Get Authorization URL After obtaining the client ID and client secret, you can proceed to construct the client authorization URL using the specified format. Utilize your assigned **client ID** and **redirect URL** in accordance with the provided guidelines to generate the authorization URL. This URL serves as the Authorization URL, allowing you to input your unique **Client ID** and the **Redirect URL** for authentication purposes. {% code overflow="wrap" %} ``` https://evia.enadocapp.com/_apis/falcon/auth/oauth2/authorize?application_state=external&resource=RESOURCE_APPLICATION&client_id={client_id} &responce_type=code&redirect_uri={redirectURL} ``` {% endcode %} ### **Error Messages** | Error | Error Decription | | ------------------------------------ | --------------------------------------------------------------- | | If access token is invalid | Invalid access token | | If access token is expired | Access token is expired | | If user does not exist in the system | User does not exist in the system. Please contact administrator | | If network error occurred | Error! Please check your internet connection and try again. | ## Get Access Token This endpoint, activated by a **GET** request to the designated URL with the access token included as a header, facilitates the retrieval of the access token for Evia Sign. Upon successful execution, it responds with a status code of 200 and presents the login page. `POST` `https://evia.enadocapp.com/_apis/falcon/auth/api/v1/Token` #### Headers | Name | Type | Description | | ------------- | ------ | --------------------------------------------- | | Authorization | Bearer | Access token should be sent as request header | {% tabs %} {% tab title="200: OK " %} If the request proceeds successfully, you will receive status code 200 with the login page to Evia Sign. {% endtab %} {% endtabs %} ### **Request Body** Upon a successful request to obtain the Access Token, the API provides a response containing relevant information, including the access token and additional details. Here's a breakdown of the request body: ```json { "client_id":"", "client_secret":"", "code":"", "grant_type":"authorization_code" } ``` ### Response Body ``` { "authToken": "Auth Token", "refreshToken": "Refresh Token" } ``` ## Refresh Token Triggered by a **GET** request to the specified URL, accompanied by the access token as a header, this endpoint is designed to refresh the access token for Evia Sign. Upon successful execution, it responds with a status code of 200, providing access to the login page, and issues a refresh token for future utilization `POST` `https://evia.enadocapp.com/_apis/falcon/auth/api/v1/Token` #### Headers | Name | Type | Description | | ------------- | ------ | --------------------------------------------- | | Authorization | Bearer | Access token should be sent as request header | {% tabs %} {% tab title="200: OK " %} If the request proceeds successfully, you will receive status code 200 with the login page to Evia Sign. {% endtab %} {% endtabs %} #### Request Body ``` { "client_id":"", "client_secret":"", "refresh_token":"'Refresh Token'", "grant_type":"refresh_token" } ``` **Response Body** Upon a successful request to refresh the access token, the API provides a response containing relevant information, including the refreshed access token and additional details. Here's a breakdown of the response body: ```json { "authToken": "Auth Token", "refreshToken": "Refresh Token" } ``` # Requests In the initial phase of the document upload process, upon successful completion, a document token is issued as a unique identifier for the uploaded document. This token plays a crucial role in the subsequent step, enabling the seamless initiation of a sign request associated with the uploaded document. Serving as a key element, the document token establishes a connection between the uploaded content and the sign request, enhancing the workflow for a more efficient and secure document signing experience. ## Document Endpoint This API offers endpoints for handling document-related operations, including fetching document pages, and uploading documents to a rendering service. These operations require proper authorization through an access token included in the request header. ## **Document Upload** This API endpoint facilitates the upload of documents to the Evia Sign platform. `POST` `https://evia.enadocapp.com/_apis/sign/thumbs/api/Requests/document` #### Headers | Name | Type | Description | | ------------- | ------ | --------------------------------------------- | | Authorization | Bearer | Access token should be sent as request header | #### Request Body | Name | Type | Description | | ---- | ---- | --------------------------------------------------------------------------- | | | File | The body contains the document data in a supported format. (PDF, DOC, DOCX) | {% tabs %} {% tab title="200: OK " %} The body of the response contains the document data, formatted in a supported file type such as PDF, DOC, or DOCX. Ensure that the uploaded document adheres to the specified format requirements. {% endtab %} {% endtabs %} ### Response Body The response body will include the document token for identification and reference purposes. ### Error Messages | Error | Error Description | | -------------------------- | ----------------------- | | If access token is invalid | Invalid access token | | If access token is expired | Access token is expired | ## Creating the Signature Request This API endpoint enables the creation of a new signature request. Submit a **POST** request to the specified URL with the access token provided as a header to initiate the process. `POST` `https://evia.enadocapp.com/api/Requests?type=1,2,3` #### Headers | Name | Type | Description | | ------------- | ------ | --------------------------------------------- | | Authorization | Bearer | Access token should be sent as request header | {% tabs %} {% tab title="200: OK " %} Upon successful creation, a status code of 200 is returned, confirming the successful initiation of the sign request. {% endtab %} {% endtabs %} **Three Methods to Create a Sign Request** | Type | Description | | ---- | ----------------------------------------------------- | | 1 | Initiate Signature Request from Template | | 2 | Fixed Positioning for Standard Signature Request | | 3 | Auto Stamping - (This is under the development phase) | **Request Body for Template** ```json { "templateId": "05117898-90db-45e5-b6b8-0230fd326e4f", "signatories": [ { "roleId": "9e7bb576-a2da-9fdc-d99c-958063dcfa19", "signatoryUserName": "Alison", "signatoryUserEmail": "alison@gmail.com" }, { "roleId": "dd0caa50-58e1-bf28-441b-556bf70d5fc0", "signatoryUserName": "Stev Smith", "signatoryUserEmail": "stev@gmail.com" }, { "roleId": "0612c8de-52b0-dc18-9a95-447041ebbe56", "signatoryUserName": "Jhone doe", "signatoryUserEmail": "jhone@gmail.com" } ] } ``` **Request Body for Fixed Positioning** ```json { "Message": "Message", "Title": "Title", "IsParallelSign": true, "Documents": [ "document token" ], "Signatories": [ { "Color": "#7c95f4", "Email": "sample@gmail.com", "Name": "Jhone Doe", "Order": 1, "PrivateMessage": "Private Message", "signatoryType": 1, "OTP": { "IsRequired": true, "AccessCode": "12345", "Type": "2", "MobileNumber": "+94711234567" }, "Stamps": [ { "Color": "#7c95f4", "DocumentToken": "document token", "Order": 1, "Location": { "X": 100.5, "Y": 105.5 }, "StampSize": { "Height": 50, "Width": 100 }, "PageNumber": 1, "PageHeight": 1000, "PageWidth": 500, "Type": "signature" } ] } ] } ``` ### # Document Upload In the initial phase of the document upload process, upon successful completion, a document token is issued as a unique identifier for the uploaded document. This token plays a crucial role in the subsequent step, enabling the seamless initiation of a sign request associated with the uploaded document. Serving as a key element, the document token establishes a connection between the uploaded content and the sign request, enhancing the workflow for a more efficient and secure document signing experience. ## Document Endpoint This API offers endpoints for handling document-related operations, including fetching document pages, and uploading documents to a rendering service. These operations require proper authorization through an access token included in the request header. ## **Document Upload** This API endpoint facilitates the upload of documents to the Evia Sign platform. `POST` `https://evia.enadocapp.com/_apis/sign/thumbs/api/Requests/document` #### Headers | Name | Type | Description | | ------------- | ------ | --------------------------------------------- | | Authorization | Bearer | Access token should be sent as request header | #### Request Body | Name | Type | Description | | ---- | ---- | --------------------------------------------------------------------------- | | | File | The body contains the document data in a supported format. (PDF, DOC, DOCX) | {% tabs %} {% tab title="200: OK " %} The body of the response contains the document data, formatted in a supported file type such as PDF, DOC, or DOCX. Ensure that the uploaded document adheres to the specified format requirements. {% endtab %} {% endtabs %} ### Response Body The response body will include the document token for identification and reference purposes. ### Error Messages | Error | Error Description | | -------------------------- | ----------------------- | | If access token is invalid | Invalid access token | | If access token is expired | Access token is expired | ### **Upload Document for Signing** `POST` `/`[`https://evia.enadocapp.com/_apis/sign/api/drafts/documents`](https://evia.enadocapp.com/_apis/sign/api/Drafts/documents) This API allows users to send documents stored in any Storage service, including SharePoint, OneDrive, or other file storage solutions, to the Evia Sign application for digital signing. The selected document from Storage will be opened in Evia Sign for further actions like signing, adding recipients, and completing the signing process. {% tabs %} {% tab title="JavaScript" %} ```json { "Documents":[ "documentId1", "documentId2", "documentId3" ], "WebhookUrl":"https://webhook.site/SampleUrl" } ``` {% endtab %} {% tab title="Python" %} ```python message = "hello world" print(message) ``` {% endtab %} {% tab title="Ruby" %} ```ruby message = "hello world" puts message ``` {% endtab %} {% endtabs %} **Response** {% tabs %} {% tab title="200" %} ```json { "requestId": "e0b91887-383e-49a8-9775-6242774618e6", "draftRequestUrl":"https://evia.enadocapp.com/#/docview/draft/e0b91887-383e-49a8-9775-6242774618e6?tab=draftTab&filter=All&from=eviaSign_inbox&zm=ftw" } ``` {% endtab %} {% tab title="400" %} ```json { "error": "Invalid request" } ``` {% endtab %} {% endtabs %} # Send Requests ## Creating the Signature Request This API endpoint enables the creation of a new signature request. Submit a **POST** request to the specified URL with the access token provided as a header to initiate the process. `POST` `https://evia.enadocapp.com/_apis/sign/api/Requests?type=1,2,3` #### Headers | Name | Type | Description | | ------------- | ------ | --------------------------------------------- | | Authorization | Bearer | Access token should be sent as request header | {% tabs %} {% tab title="200: OK " %} Upon successful creation, a status code of 200 is returned, confirming the successful initiation of the sign request. {% endtab %} {% endtabs %} **Three Methods to Create a Sign Request** | Type | Description | | ---- | ----------------------------------------------------- | | 1 | Initiate Signature Request from Template | | 2 | Fixed Positioning for Standard Signature Request | | 3 | Auto Stamping - (This is under the development phase) | # Request Types # Template ## Implementation Overview Evia Sign's "**Initiate Signature Request from Template**" API simplifies the process of generating signature requests based on predefined templates. This API endpoint enables the initiation of a signature request from a template: `POST` `https://evia.enadocapp.com/_apis/sign/api/Requests?type=1` #### Headers | Name | Type | Description | | ------------- | ------ | --------------------------------------------- | | Authorization | Bearer | Access token should be sent as request header | {% tabs %} {% tab title="200: OK " %} Upon successful creation, a status code of 200 is returned, confirming the successful initiation of the sign request. {% endtab %} {% endtabs %} The provided JSON body serves as an example, showcasing the essential parameters required to initiate such a request. **Request Body for Template** ```json { "templateId": "05117898-90db-45e5-b6b8-0230fd326e4f", "signatories": [ { "roleId": "9e7bb576-a2da-9fdc-d99c-958063dcfa19", "signatoryUserName": "Alison", "signatoryUserEmail": "alison@email.com" }, { "roleId": "dd0caa50-58e1-bf28-441b-556bf70d5fc0", "signatoryUserName": "Stev Smith", "signatoryUserEmail": "stev@email.com" }, { "roleId": "0612c8de-52b0-dc18-9a95-447041ebbe56", "signatoryUserName": "Jhone doe", "signatoryUserEmail": "jhone@email.com" } ] } ``` # Fixed Positioning ## Implementation Overview Evia Sign's Fixed Positioning API introduces a seamless and secure approach to automated annotation placement, focusing on precise positioning of signatures within documents. This API supports a structured JSON payload, empowering users to define key elements for creating signature requests with fixed positioning. This API endpoint enables the creation of a new signature request with fixed positioning: `POST` `https://evia.enadocapp.com/_apis/sign/api/Requests?type=2` #### Headers | Name | Type | Description | | ------------- | ------ | --------------------------------------------- | | Authorization | Bearer | Access token should be sent as request header | {% tabs %} {% tab title="200: OK " %} Upon successful creation, a status code of 200 is returned, confirming the successful initiation of the sign request. {% endtab %} {% endtabs %} **Request Body for Fixed Positioning** ```json { "Message": "", "Title": "Vendor agreement - Silverline Traders.pdf", "SignInOrder": false, "Documents": [ "{{documentId}}" ], "Signatories": [ { "Color": "#7c95f4", "Email": "johndoe@email.com", "Name": "Test User 1", "Order": 1, "PrivateMessage": "", "SignatoryType": 1, "OTP": { "IsRequired": false, "AccessCode": "", "Type": "0", "MobileNumber": "" }, "Stamps": [ { "Color": "#7c95f4", "DocumentToken": "{{documentId}}", "Order": 1, "Location": { "X": 397.9166666666667, "Y": 249.79166666666669 }, "StampSize": { "Height": 35, "Width": 75 }, "PageNumber": 1, "PageHeight": 1122, "PageWidth": 793, "Type": "signature" } ] }, { "Color": "#c0a5cf", "Email": "Peterdoe@email.com", "Name": "Test User 2", "Order": 1, "PrivateMessage": "", "SignatoryType": 1, "OTP": { "IsRequired": false, "AccessCode": "", "Type": "0", "MobileNumber": "" }, "Stamps": [ { "Color": "#c0a5cf", "DocumentToken": "{{documentId}}", "Order": 1, "Location": { "X": 407.2916666666667, "Y": 338.33333333333337 }, "StampSize": { "Height": 35, "Width": 75 }, "PageNumber": 1, "PageHeight": 1122, "PageWidth": 793, "Type": "signature" } ] }, { "Color": "#f7b994", "Email": "John@email.com", "Name": "test user 3", "Order": 2, "PrivateMessage": "", "SignatoryType": 1, "OTP": { "IsRequired": false, "AccessCode": "", "Type": "0", "MobileNumber": "" }, "Stamps": [ { "Color": "#f7b994", "DocumentToken": "{{documentId}}", "Order": 1, "Location": { "X": 397.9166666666667, "Y": 462.2916666666667 }, "StampSize": { "Height": 35, "Width": 75 }, "PageNumber": 1, "PageHeight": 1122, "PageWidth": 793, "Type": "signature" } ] }, { "Color": "#97c9bf", "Email": "tom@email.com", "Name": "Test User 4", "Order": 3, "PrivateMessage": "", "SignatoryType": 1, "OTP": { "IsRequired": false, "AccessCode": "", "Type": "0", "MobileNumber": "" }, "Stamps": [ { "Color": "#97c9bf", "DocumentToken": "{{documentId}}", "Order": 1, "Location": { "X": 402.08333333333337, "Y": 551.875 }, "StampSize": { "Height": 35, "Width": 75 }, "PageNumber": 1, "PageHeight": 1122, "PageWidth": 793, "Type": "signature" } ] }, { "Color": "#ffb3c6", "Email": "jonny@email.com", "Name": "Test User 5", "Order": 3, "PrivateMessage": "", "SignatoryType": 1, "OTP": { "IsRequired": false, "AccessCode": "", "Type": "0", "MobileNumber": "" }, "Stamps": [ { "Color": "#ffb3c6", "DocumentToken": "{{documentId}}", "Order": 1, "Location": { "X": 408.33333333333337, "Y": 653.9583333333334 }, "StampSize": { "Height": 35, "Width": 75 }, "PageNumber": 1, "PageHeight": 1122, "PageWidth": 793, "Type": "signature" } ] } ], "AuditDetails": { "AuthorType": 1, "AuthorIPAddress": "124.43.19.95", "Device": "Device Type: desktop - OS: Windows - Browser: Chrome (v129.0)" }, "Connections": [] } ``` **Signing Order**: Signing requests can be sent either in parallel, where all signatories receive the request simultaneously, or sequentially, where each signatory receives the request one after another. **Signatory Types**: Signatories can be categorized as either *Signing*, *Approval*, or *CC*. At least one *Signing* signatory is required for each request, and signature fields are mandatory for signing. Additional options include the ability to add initials, name, signed date, email, and text. **Security Features**: For added security, there is an option to include an OTP (One-Time Password) via email, SMS, or both, and to set an access code. **Audit Trail**: Once the document is completed, an audit trail document is generated for each request. It includes the details of the sender and the signatories, such as IP addresses and devices used. **Signer Types**: Signers can either be internal or external. # Auto Stamping ## **Implementation Overview** Evia Sign's Auto Stamping API offers a streamlined and secure solution for the automated placement of annotations, such as signatures, on documents. This API provides a highly customizable process, accepting structured JSON payloads that define the documents, signatories, and the specific stamp positions. ### **API Processing** Upon receiving the request, Evia Sign's API processes each document, ensuring the accurate placement of specified stamps at designated locations. The system adheres to the provided coordinates and specifications for stamp placement. This API endpoint enables the creation of a new signature request with auto stamping: `POST` `https://evia.enadocapp.com/_apis/sign/api/Requests?type=3` #### Headers | Name | Type | Description | | ------------- | ------ | --------------------------------------------- | | Authorization | Bearer | Access token should be sent as request header | {% tabs %} {% tab title="200: OK " %} Upon successful creation, a status code of 200 is returned, confirming the successful initiation of the sign request. {% endtab %} {% endtabs %} ### **Sample API Request Structure** Below is an example illustrating the structure of a typical API request for Auto Stamping in Evia Sign: ```json { "Message": "Message", "Title": "Title", "Documents": [ "2e5cfa87-44d3-4d6d-88e1-3f6586a3c158" ], "Signatories": [ { "Color": "#7c95f4", "Email": "johndoe@email.com", "Name": "Jhone Doe", "Order": 1, "PrivateMessage": "Private Message", "signatoryType": 1, "OTP": { "IsRequired": true, "AccessCode": "12345", "Type": "1", "MobileNumber": "" }, "AutoStamps": [ { "Identifier":"signature1", "Color": "#7c95f4", "Order": 1, "Offset": { "X_offset": 0, "Y_offset":-50 }, "StampSize": { "Height": 50, "Width": 100 }, "Type": "signature" }, { "Identifier":"text1", "Color": "#7c95f4", "Order": 1, "Offset": { "X_offset": 0, "Y_offset": -25 }, "StampSize": { "Height": 50, "Width": 100 }, "Type": "text" }, { "Identifier":"email1", "Color": "#7c95f4", "Order": 1, "Offset": { "X_offset": 0, "Y_offset": -25 }, "StampSize": { "Height": 50, "Width": 100 }, "Type": "email" }, { "Identifier":"Date1", "Color": "#7c95f4", "Order": 1, "Offset": { "X_offset": 0, "Y_offset": -25 }, "StampSize": { "Height": 50, "Width": 100 }, "Type": "date" }, { "Identifier":"initial1", "Color": "#7c95f4", "Order": 1, "Offset": { "X_offset": 0, "Y_offset": -50 }, "StampSize": { "Height": 50, "Width": 100 }, "Type": "initial" } ] } ] } ``` ### **Key Elements of the Request:** * **Message & Title:** General information about the signing request, including a message to signatories and the title of the document. * **Documents:** An array containing identifiers (Document ID) of the documents to be signed. * **Signatories:** Details of individuals required to sign, including personal information and signature-related details. * **Stamps:** Specifies the placement details for each signatory, such as location, size, and type of stamps (e.g., signatures). # Document The Document API in the Evia Sign platform provides robust functionality for document handling, including fetching document pages, uploading new documents, and retrieving documents linked to specific requests. `GET` {{PDFRenderService}}/api/ImageRenderingService/GetPage?documentToken=ZXZpYV9zaWduX3BkZl9kNWQ3MTRkMi05ODcyLTQ5OGItOWY4NC1lZjc2MmIzM2IyMTFfYTVlNmFhMzItMzNjZi00YTkyLWE3ZDctMDY4YjU2MDdjYjkyLnBkZnwy This endpoint retrieves a specific page of a document using the document token. The document token is a unique identifier for the uploaded document. `POST` {{PDFRenderService}}/api/Requests/document This endpoint facilitates the upload of documents to the Evia Sign platform. `GET` [https://evia.enadocapp.com/\_apis/sign/pdf/api/ImageRenderingService/GetPage?documentToken=ZXZpYV9zaWduX3BkZl9mZDE0NzNjYy0zOGY1LTQ3ODUtYjBiZi02MzNkNTk0NDRiYTdfZjY3ZGYxNWMtYzBmNS00N2Q0LWIzY2EtZWVkMTcxMjNjODgyLnBkZnwxfGZhYjIyYzEzLWU5MGEtNDFjMi05NGFmLWQ1Zjk2YmIyOTM2OA==](https://evia.enadocapp.com/_apis/signnew/pdf/api/ImageRenderingService/GetPage?documentToken=ZXZpYV9zaWduX3BkZl9mZDE0NzNjYy0zOGY1LTQ3ODUtYjBiZi02MzNkNTk0NDRiYTdfZjY3ZGYxNWMtYzBmNS00N2Q0LWIzY2EtZWVkMTcxMjNjODgyLnBkZnwxfGZhYjIyYzEzLWU5MGEtNDFjMi05NGFmLWQ1Zjk2YmIyOTM2OA==) This endpoint retrieves the documents associated with a specific sign request. # Signature and Initials # Signature The Signature API in the Evia Sign platform provides endpoints for managing user signatures. This includes retrieving the current signature, uploading a new signature, and deleting an existing signature. Below are the descriptions of the provided endpoints. ### Retrieve User Signature `GET` {{baseUrl}}/api/users/signature This endpoint retrieves the current signature of the user. ### Upload User Signature `POST` {{baseUrl}}/api/users/signature This endpoint facilitates the upload of a new signature for the user. ### Delete User Signature `DELETE` {{baseUrl}}/api/users/signature This endpoint deletes the current signature of the user. # Initials The Initials API in the Evia Sign platform provides endpoints for managing user initials. This includes retrieving the current initials, uploading new initials, and deleting existing initials. Below are the descriptions of the provided endpoints. ### Retrieve User Initials `GET` {{baseUrl}}/api/users/initial This endpoint retrieves the current initials of the user. ### Upload User Initials `POST` {{baseUrl}}/api/users/initials This endpoint facilitates the upload of new initials for the user. ### Delete User Initials `DELETE` {{baseUrl}}/api/users/initial This endpoint deletes the current initials of the user. # Webhooks ## **Webhook Events** Evia Sign provides webhook notifications for various events, allowing you to stay informed and take action in real-time. Here are the supported webhook events: ### **Create Signature Request** Triggered when a new signature request is initiated. ### **Create Template:** Fired when a new template is created within the Evia Sign platform. ### **Create ZeroTouch Request:** Informs about the creation of a ZeroTouch request, which involves generating a draft request using a predefined template. ### **Signatory Signed:** Notifies when a signatory has successfully added their signature to the document. ### **Signatory Completed:** Indicates that a signatory has completed their part in the signing process. ### **Signatory Declined:** Triggered when a signatory declines to sign the document. ### **Request Recall:** Informs about the initiation of a request recall, indicating a request's withdrawal or cancellation. ## **Webhook Notification Data Formats:** Evia Sign allows flexibility in choosing the data to be included in webhook notifications. You can customize the webhook payload to include relevant information for your application. Commonly included data formats are: 1. **Document:** * Information related to the document being signed. 2. **Signatories:** * Details about the individuals involved in the signing process. 3. **Stamps:** * Data pertaining to the stamps or signatures applied to the document. {% hint style="info" %} This flexibility enables you to tailor the webhook notifications based on your specific needs, ensuring that you receive only the data relevant to your integration requirements. {% endhint %} # V2 # Welcome to Evia Sign API Version2 Welcome to the Evia Sign API Version 2 Documentation. This API provides a secure, scalable, and developer-friendly way to integrate advanced digital signature capabilities directly into your applications. Whether you're building a simple signing workflow or a complex, multi-party signature process, Version 2 is designed to meet your needs with enhanced performance and robust security. ## What’s New in Evia Sign API Version 2? Evia Sign API Version 2 is a significant upgrade over Version 1, bringing a range of improvements designed to enhance both security and usability: ### **Optimized Signing Workflow:** * In Version 1, sending signature requests to multiple recipients in a single JSON collection often caused workflow disruptions due to timeouts. * Version 2 introduces an optimized flow, where each signature request is processed independently, ensuring seamless, reliable multi-party signing. ### **Enhanced Security with OAuth 2.0:** * While OAuth 2.0 was part of Version 1, the implementation has been significantly refined in Version 2. * This enhanced implementation ensures better compliance with industry security standards, providing robust protection for your digital signatures. ### **Developer-Friendly Design:** * A more intuitive API structure with well-defined endpoints, designed to simplify integration. * Comprehensive, clear documentation with step-by-step guidance for various use cases. * Practical code examples and ready-to-use templates for faster implementation ## **Why Choose Evia Sign API Version 2?** * **Reliability:** Avoid workflow disruptions with optimized request handling, especially in high-volume signing scenarios. * **Security:** Enjoy robust protection with OAuth 2.0, implemented using best practices for secure API authentication. * **Scalability:** Effortlessly scale your digital signing operations, from simple one-time signatures to complex multi-party agreements. * **Flexibility:** Support for dynamic signatory management, automated stamping, and precise document positioning. ## **Who Should Use This API?** * **Developers:** Looking to integrate secure, flexible digital signatures into their applications. * **Enterprises:** Needing scalable, compliant, and secure digital signing solutions for internal and external workflows. * **Service Providers:** Offering digital signature capabilities as part of their product portfolio. ## Let’s Get Started To make the most of Evia Sign API Version 2, follow these sections to understand its capabilities and implementation: * **Authentication:** Learn how to securely access the API using OAuth 2.0. * **Core API Workflows:** Discover how to create, send, and manage signature requests. * **Error Handling:** Understand how to identify and resolve common issues. * **Webhook Management:** Set up and manage real-time notifications for key events. * **Code Examples:** Explore ready-made code samples for quick integration. For any questions or support, please contact our team at . # How to Migrate from API v1 to v2 # Basic Guide with minimal changes This guide helps developers move from Evia Sign's API v1 to API v2 with minimal changes, specifically for request type 3 (Auto Stamping). > ⚠️ **Note:** This guide only covers the minimal migration path. A full guide for all API v2 features and request types will be released soon. *** ### ✅ What You Can Keep As-Is * **Document Upload:** Your current implementation using API v1 can remain unchanged. *** ### 🔁 What’s Different in API v2 In v1, you sent everything (document, signers, stamps, OTP, etc.) in **one big API call**. In v2, you break it down into 5 smaller, easier-to-manage steps: 1. Upload the document (same as v1) 2. Create the request (with `?type=0`) 3. Add signatories 4. Add stamp positions 5. Send the request *** ### ⚙️ Migration Steps in API v2 **1. Upload the Document (No Change)** ✅ Returns: `documentId` *** **2. Create the Request (type=0)** ```http POST /api/v2/requests?type=0 Authorization: Bearer Content-Type: application/json { "title": "Auto Stamping - Test", "message": "This is your document", "completedDocumentsAttached": true, "callbackTypes": [1], "documents": [""] } ``` 🔁 Returns: `requestId` *** **3. Add Each Signatory** ```http POST /api/v2/requests/{requestId}/signatories { "name": "Signer Name", "email": "signer@example.com", "order": 1, "signatoryType": 1, "otp": { "isRequired": true, "accessCode": "12345", "type": 3 } } ``` ✔️ Returns: `signatoryId` *** **4. Add AutoStamp for the Signatory** ```http POST /api/v2/requests/{requestId}/signatories/{signatoryId}/stamps { "identifier": "<>", "color": "#7c95f4", "order": 1, "offset": { "xOffset": 0, "yOffset": 0, "offsetType": 2 }, "stampSize": { "height": 50, "width": 100 }, "type": "signature" } ``` *** **5. Send the Request** ```http POST /api/v2/requests/{requestId}/send ``` ✅ This triggers the document and sends it to signers. *** ### 📊 Summary Table | Step | v1 | v2 | | --------------- | --------------------- | --------------------- | | Document Upload | Same | Same | | Create Request | One big payload | `/requests?type=0` | | Add Signers | Inline in request | Separate API call | | Add Stamps | Inline in request | Separate API call | | Send Request | Happens automatically | Explicit `/send` call | *** #### 📌 Additional Notes * `type=0` must be passed as a query parameter in v2 request creation * Webhooks are now handled via a separate API. * API v2 provides more descriptive error responses and improves control. This migration keeps your system stable while making use of v2’s improved modular design. # Access Token Request (v1 ➞ v2) ### ✨ Why Migrate? * **Improved Security**: V2 uses Basic Authentication with base64 encoding. * **Standards Compliance**: V2 uses `application/x-www-form-urlencoded`, aligning with OAuth 2.0. * **Detailed Response**: Includes `token_type`, `expires_in`, and other standard fields. *** ### ↺ What Changed? | Feature | API v1 | API v2 | | ------------------------ | ----------------------------- | --------------------------------------------------------- | | **Endpoint** | `/api/v1/Token` | `/api/v2/token` | | **HTTP Method** | `POST` | `POST` | | **Authorization Header** | `Bearer ` | `Basic base64(client_id:client_secret)` | | **Content-Type** | `application/json` | `application/x-www-form-urlencoded` | | **Body Format** | JSON | Form-Encoded | | **Response Format** | `{ authToken, refreshToken }` | `{ access_token, refresh_token, token_type, expires_in }` | *** ### 📁 Migration Steps #### ✅ Before (API v1) ```http POST https://evia.enadocapp.com/_apis/falcon/auth/api/v1/Token Authorization: Bearer Content-Type: application/json { "client_id": "", "client_secret": "", "code": "", "grant_type": "authorization_code" } ``` #### ✅ After (API v2) ```http POST https://evia.enadocapp.com/_apis/falcon/auth/api/v2/token Authorization: Basic Content-Type: application/x-www-form-urlencoded grant_type=authorization_code& client_id=your-client-id& client_secret=your-client-secret& code=received-auth-code ``` *** ### 🔄 Response Comparison #### ❌ v1 Response ```json { "authToken": "Auth Token", "refreshToken": "Refresh Token" } ``` #### ✅ v2 Response ```json { "access_token": "abc123...", "refresh_token": "abc1asas23...", "token_type": "bearer", "expires_in": 3600 } ``` *** ### 🔀 What Remains the Same * You still use `authorization_code` as the `grant_type`. * You still provide `client_id`, `client_secret`, and `code`. *** # Authorization & Authentication Evia Sign API uses OAuth 2.0 (Authorization Code Flow) to provide secure access, ensuring that only authorized users and applications can interact with the API. This method allows applications to obtain an access token that must be included in all API requests for authentication. To securely interact with the Evia Sign API, you’ll need to authenticate your application using **OAuth 2.0 Authorization Code Flow**. ## What is a Base URL? The **Base URL** is the root address that serves as the entry point for all Evia Sign API requests. You will append specific endpoints to this base to interact with different API features (e.g., sending documents, managing signatories, tracking signatures). **Base URL**: `https://evia.enadocapp.com/_apis/sign` ## Authentication Method: OAuth 2.0 (Authorization Code Flow) Evia Sign uses **OAuth 2.0**, specifically the **Authorization Code Flow**, which is one of the most secure methods for authorizing access to an API. Here’s a quick breakdown of how it works: 1. **App Registration** Before initiating the authentication flow, the third-party application must be registered in Evia Sign.\ Upon successful registration, you will receive the following: * **Client ID** – A unique identifier for the application. * **Client Secret** – A confidential key used for secure token exchange. {% hint style="info" %} These credentials uniquely identify and authorize your app. {% endhint %} 2. **Request Authorization Code** Use the Evia Sign authorization URL, including the required parameters, to request an authorization code. 3. **Authorization Code Issued** If the request is valid, Evia Sign returns an authorization code. 4. **Token Exchange** Use the authorization code, along with your Client ID and Client Secret, to call Evia Sign’s token endpoint and exchange it for an access token. 5. **Authenticated Requests** Once the access token is received, include it in the `Authorization` header to make authenticated requests to the Evia Sign API. # How to Register Your Application Before any authentication can take place, your application must be registered within the Evia Sign platform. This registration process allows Evia Sign to recognize and securely authorize your application. Once registered, you’ll receive a **Client ID** and **Client Secret**, which are required to initiate the OAuth 2.0 Authorization Code Flow. These credentials serve as the foundation for all secure interactions between your application and the Evia Sign API. Follow the steps below to register your application on the Evia Sign platform: 1. **Access API Management**\ Go to the **Settings** section, then click on **Integrations**
3. **Register a New Application** Click the **New App** button within the Integrations section. Fill in the required fields: * **App Name** – A unique and recognizable name for your application. * **Redirect URI (Callback URL)** – The endpoint on your system where Evia Sign will send the authorization code. * **Description** – A short description that clearly identifies your app’s purpose. Once all details are provided, click **Save**.
4. **Save and Retrieve Credentials** After saving, the system will generate the following credentials: * **Client ID** – Used to identify your application during the authorization process. * **Client Secret** – A confidential key used to securely authenticate your app during token exchange.
Once your application is registered and you’ve secured your **Client ID** and **Client Secret**, you’re ready to move on to the next step—**requesting the authorization code** needed to initiate the access token flow. # Requesting the Authorization Code ## Get OAuth 2.0 Authorization Code Once your application has been registered and you’ve obtained the **Client ID**, the next step is to request an **authorization code**. This code is a temporary credential that you will later exchange for an access token. This step is executed directly by the third-party system via an HTTP `GET` request to Evia Sign’s authorization endpoint. ### Authorization Code Request URL `GET` `/_apis/falcon/auth/oauth2/authorize` Initiates the OAuth 2.0 Authorization Code Flow. This endpoint is used to request an authorization code by passing your application's credentials and configuration details as query parameters. The response will redirect to your registered `redirect_url` with an authorization code that can be used to request an access token. ### Required Query Parameters | Parameter | Required | Description | | ------------------- | -------- | ------------------------------------------------------------------------- | | `application_state` | ✅ Yes | Static value, typically set to `external` for external integrations. | | `resource` | ✅ Yes | The resource type being accessed; usually `RESOURCE_APPLICATION`. | | `client_id` | ✅ Yes | Your application's unique **Client ID** received during app registration. | | `scope` | ✅ Yes | The permission scope being requested (e.g., `Sign Falcon Licensing`). | | `response_type` | ✅ Yes | Must be set to `code` to receive an authorization code. | ### Example Authorization URL ```http http://evia.enadocapp.com/_apis/falcon/auth/oauth2/authorize? application_state=external& resource=RESOURCE_APPLICATION& client_id=YOUR_CLIENT_ID& scope=Sign%20Falcon%20Licensing& response_type=code ``` ### How It Works 1. **Build the URL** using your `client_id`, desired `scope`, and other parameters. 2. **Send the request** using a server-side `GET` call to the authorization URL. 3. If the request is valid, Evia Sign will **redirect** the response to your provided `redirect_url`, appending the **authorization code** in the URL. ### Example Redirect Response If the request is successful, the user is redirected to your application’s callback URL: ```json ?code=received-auth-code ``` Your application must **extract the `code` parameter** from this URL. This `code` is then used in the next step (token exchange) to receive an access token. # Exchange Authorization Code for Access Token After successfully receiving the **authorization code**, the next step in the OAuth 2.0 flow is to exchange that code for an **access token**. This token acts as a credential that authorizes your application to securely access Evia Sign API endpoints on behalf of the authenticated system. The exchange must be performed by your backend server, using your **Client ID** and **Client Secret**, along with the received code. The resulting access token must then be included in the `Authorization` header of all subsequent API requests. ## Token Exchange URL `POST` `/_apis/falcon/auth/api/v2/token` This endpoint is used to exchange a valid **authorization code** for an **access token**.\ The access token is required to authenticate and authorize all subsequent API requests to the Evia Sign platform. This request must be made server-side to ensure secure handling of the **Client Secret**. ### Request Headers Include the following headers to authenticate your request and ensure it’s correctly processed by the server. | Name | Value | | ------------- | -------------------------------------------------------------------------------------------------------------------------- | | Authorization | The `Authorization` header must use **Basic Authentication**. Format the value as: `Basic base64(client_id:client_secret)` | | Content-Type | Must be set to `application/x-www-form-urlencoded` to ensure that the request body is interpreted correctly by the server. | ### Request Body Parameters (Form-Encoded) The request body should be sent in `x-www-form-urlencoded` format. Below are the required parameters: | Parameter | Required | Description | | --------------- | -------- | ------------------------------------------------------------------------- | | `grant_type` | ✅ Yes | Must be set to `authorization_code` | | `client_id` | ✅ Yes | Your application's **Client ID** (same used in the authorization request) | | `client_secret` | ✅ Yes | Your **Client Secret** | | `code` | ✅ Yes | The **authorization code** received from the previous step | ### Sample Request (Raw Format) ```http POST https://evia.enadocapp.com/_apis/falcon/auth/api/v2/token Authorization: Basic base64(client_id:client_secret) Content-Type: application/x-www-form-urlencoded ``` #### **Body** ```json { "grant_type": "authorization_code", "client_id": "your-client-id", "client_secret": "your-client-secret", "code": "received-auth-code" } ``` ### Successful Response If the request is valid, Evia Sign will return a response with an access token: ```json { "access_token": "abc123...", "token_type": "bearer", "expires_in": 3600, "refresh_token": "xyz456..." } ``` | Field | Description | | --------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | | `access_token` | This is the actual token your app will use to make authorized API requests. You must include it in the `Authorization` header as `Bearer abc123...` | | `token_type` | Always set to `bearer`. This just tells you how the token should be used in the header | | `expires_in` | The number of seconds the access token is valid for. In this case, 7 days. After that, the token is no longer valid. | | `refresh_token` | A token that can be used to request a new `access_token` after it expires—so your app doesn’t need to go through the full authorization flow again. | ### Error Response Example ```json { "error": "invalid_request" } ``` Common causes include: * Missing or incorrect `client_id` or `client_secret` * Expired or reused authorization code * Incorrect or mismatched `redirect_url` ## Using the Access Token in API Requests Once the access token is received, include it in the `Authorization` header of all subsequent API requests: ```http Authorization: Bearer abc123... ``` This token allows Evia Sign to verify the identity of your registered application and authorize its access to the API, based on the scopes granted during app registration. ## Refresh Access Token After the original `access_token` has expired, you can request a new one using a valid `refresh_token`. This allows your application to maintain its authenticated session with the Evia Sign API **without re-running the full authorization flow**. ### Request URL `POST``/ _apis/falcon/auth/api/v2/Token` This endpoint is used to exchange a valid refresh token for a new access token.\ The request must be made **server-side**, as it involves sending your Client ID and Client Secret in the `Authorization` header. ### Request Headers | Header | Required | Description | | --------------- | -------- | -------------------------------------------------------------------- | | `Authorization` | ✅ Yes | Basic Auth using `base64(client_id:client_secret)` | | `Content-Type` | ✅ Yes | Handled automatically as `multipart/form-data` via the `--form` flag | ```http Authorization: Basic Base64(client_id:client_secret) Content-Type: multipart/form-data ``` ### Request Body Parameters | Parameter | Required | Description | | --------------- | -------- | ---------------------------------------------------------------- | | `Refresh_Token` | ✅ Yes | The valid refresh token previously issued by Evia Sign. | | `Grant_Type` | ✅ Yes | Must be set to `Refresh_Token` (case-sensitive on some systems). | ```http Refresh_Token: "457F4F73-025C-451A-8484-674C5FDC11B59F421000-10CD-4B3E-871D-586EFD38139C" Grant_Type: "Refresh_Token" ``` ### Successful Response ```json { "access_token": "new-access-token-123...", "token_type": "bearer", "expires_in": 3600, "refresh_token": "new-refresh-token-456..." } ``` ### Error Response ```json { "error": "invalid_request" } ``` **Possible causes:** * Missing or expired `Refresh_Token` * Incorrect `Grant_Type` * Invalid or malformed `Authorization` header ### Using the New Token Once you receive the new `access_token`, include it in the `Authorization` header like this: ```http Authorization: Bearer new-access-token-123... ``` # Upload Document for Signing Before a document can be sent for signing, it must first be **uploaded to Evia Sign**. This step ensures the document is securely stored and available within the signing environment. ## Document Upload URL `POST` `/_apis/sign/thumbs/api/v2/requests/document` This URL is used to upload a PDF file to Evia Sign before initiating any signing process. Once uploaded, the system returns a `documentToken` that must be used when creating a signature request. The document is stored securely and becomes available for further workflow actions such as assigning signatories or setting stamps. ### Authentication This request **must be authenticated** using a valid `access_token`. You obtain this token through the OAuth flow, and it must be included in the request header. ### **Headers** | Header | Valu | Description | | --------------- | --------------------- | ---------------------------------------------------------- | | `Authorization` | Bearer access\_token | OAuth 2.0 token obtained during authentication | | `Content-Type` | `multipart/form-data` | Must be set to `multipart/form-data` to allow file upload. | ### Request Body Details This API expects a **binary PDF file** to be attached using the form field name `File`. You do not need to send any additional parameters in the body. | Type | Required | Description | | ------ | -------- | ------------------------------------------ | | `File` | ✅ Yes | The document you want to send for signing. | ### Successful Response A unique `documentToken` will be returned for the uploaded document. This token is used in the `Documents` array when initiating a signature request. ```json { "documentToken": "abc123-token" } ``` **What is `documentToken`?** This is the unique reference ID for the uploaded file. You do **not** reupload the document during signature creation. Instead, you send this token to link your signature request with the uploaded file. ### Possible Errors and How to Handle Them
Status CodeError MessageExplanation
400Allowed extensions are PDF, DOC, DOCXThe uploaded file was not a PDF, or the form field key was incorrect.
401UnauthorizedThe access_token was missing or expired
# Creating a Signature Request AuditDetails object ✅ Yes Captures metadata about who initiated the request Connections array Optional Reserved for internal routing or grouping logicAuditDetails object ✅ Yes Captures metadata about who initiated the request Connections array Optional Reserved for internal routing or grouping logicAfter successfully uploading a document, the next step is to initiate a signature request using the `documentToken` returned by the upload step. ## Signature Request URL `POST` `/_apis/sign/api/v2/requests?type=0` This request URL is used to initialize a **Type 0 (Skeleton)** signature request in Evia Sign. It creates a signing workflow that can be configured further by adding signatories and stamps before being sent. ### What This Does This API call **creates a new signature request** using **type=0**, also known as the **Skeleton workflow**. * It sets up the signing request with a document, title, and audit metadata. * **No signers or stamps are added yet** — those will be configured in follow-up API calls. * This is ideal for automated flows where signer data is dynamic or added later. | Type | Name | Description | | ---- | --------------------------- | ---------------------------------------------------------------------- | | `0` | Skeleton (Automation / RPA) | Step-by-step creation using separate calls for signatories and stamps. | ### Required Headers These headers must be included to authenticate and properly format the request. | Header | Required | Description | | --------------- | -------- | ------------------------------------------- | | `Authorization` | ✅ Yes | Bearer token (OAuth 2.0) for authentication | | `Content-Type` | ✅ Yes | Must be `application/json` | ### Required Fields Type 0 (Skeleton – Automation/RPA) For workflows where you want full control over the process — add signers, stamps, and placements **after** creating the request. You initialize the signing process with just the document and metadata. Callback settings are optional but recommended to stay notified about status changes | Field | Required | Type | Description | | ---------------------------- | -------- | ---------- | ---------------------------------------------------------------------------- | | `Title` | ✅ Yes | `string` | The name of the signature request. Appears in the signer UI and email. | | `Message` | ✅ Yes | `string` | A short message shown to the signers (e.g., instructions or context). | | `Documents` | ✅ Yes | `string[]` | List of uploaded `documentTokens`. At least one is required. | | `CallbackUrl` | Optional | `string` | Publicly accessible URL to receive webhook notifications for events. | | `CallbackTypes` | Optional | `int[]` | List of event codes that determine which webhook events should be triggered. | | `CompletedDocumentsAttached` | Optional | `boolean` | If `true`, signed PDFs will be attached in the final webhook callback. | | `AuditDetails` | ✅ Yes | `object` | Captures metadata about who initiated the request | | `Connections` | Optional | `array` | Metadata used for audit trails and tracking. See below. | Define which events you want Evia Sign to notify your system about by setting the `CallbackTypes` | Code | Event Triggered | | ---- | ----------------------------------------------------------------- | | `0` | **All Events** — shorthand to receive notifications for all below | | `1` | Request received | | `2` | Signatory completed their signature | | `3` | Entire signing process completed | ### AuditDetails Breakdown This block improves auditability by storing who created the request and from what environment. | Subfield | Description | | ----------------- | ----------------------------------------------------------------------- | | `AuthorType` | Usually `1` = Admin or system user. | | `AuthorIPAddress` | IP address of the user or system initiating the request. | | `Device` | Human-readable string describing the environment (device, OS, browser). | ### Example Payload ```json { "Title": "Contract Agreement", "Message": "Please review and sign.", "Documents": [ "abc123-token" ], "CallbackUrl": "https://yourdomain.com/webhooks/evia-sign", "CallbackTypes": [1], "CompletedDocumentsAttached": true, "AuditDetails": { "AuthorType": 1, "AuthorIPAddress": "", "Device": "Device Type: desktop - OS: Windows - Browser: Chrome (v131.0)" }, "Connections": [] } ``` ### Successful Response When a signature request is successfully created,Evia Sign returns the following response: ```json { "requestId": "abc123-request-id" } ``` ### Field Explanation | Field | Type | Description | | ----------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `requestId` | `string` | A unique identifier for the newly created signature request. This ID is required for all subsequent operations such as adding signers, assigning stamps, tracking status, or sending the request. | ### Possible Errors and How to Handle Them | Status Code | Error Message | Explanation | | ----------- | ------------------------ | ------------------------------------------------------------------------------------------------------- | | `400` | Bad Request | The request body is invalid or missing required fields such as `Title`, `Documents`, or `AuditDetails`. | | `401` | Unauthorized | The access token is missing, expired, or incorrect. Ensure a valid Bearer token is included. | | `404` | Document Token Not Found | The `documentToken` provided in the `Documents` array does not exist or is no longer valid. | # Add Signatory to a Signature Request This operation allows you to add a **participant** (signer, approver or cc) to a signature request that was created using **type=0 (skeleton mode)**. Each person you add to the request can be configured with a custom role, signing order, color label, and OTP authentication method. You can call this endpoint multiple times to build out your workflow with as many participants as needed, assigning them in sequential or parallel flows. ## Request URL `POST` `/_apis/sign/api/v2/requests/requestId/signatories` Defines the request URL for adding a signatory to a request. ### Required Headers Headers required to authenticate the API call and send data in the correct format. | Header | Required | Description | | --------------- | -------- | ------------------------------------------------------------------------------------ | | `Authorization` | ✅ Yes | Bearer token generated from the OAuth 2.0 flow. Used to authenticate the API caller. | | `Content-Type` | ✅ Yes | Must be `application/json`. Ensures the body is parsed correctly. | ### Request Body Schema Use this JSON structure to define the signatory you’re adding to the signature request. ```json { "Email": "eviasign@gmail.com", "Name": "Signer User", "Order": 1, "PrivateMessage": "Sample private message", "SignatoryType": 1, "Color": "#7c95f4", "OTP": { "IsRequired": true, "AccessCode": "", "Type": 2, "MobileNumber": "" } } ``` ### Field-by-Field Explanation Explanation of each field in the request body. | Field | Type | Required | Description | | ---------------- | --------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------- | | `Email` | `string` | ✅ Yes | Signatory's email. Used for communication and signing access. | | `Name` | `string` | ✅ Yes | Full name of the signatory. Displayed in the UI and audit trail. | | `Order` | `integer` | ✅ Yes | Defines the sequence of signing. Lower order signs first. Use `1`for parallel signing. | | `PrivateMessage` | `string` | Optional | A message visible only to this signatory. Useful for instructions. | | `SignatoryType` | `integer` | ✅ Yes |

Role in the workflow:

1 = Signer,

2 = Approver,

3 = CC (copy only)

| | `Color` | `string` | Optional | UI tag color (hex) to visually represent the user (no impact on final doc). | *** ### Role of the User in the Request Defines the level of interaction each signatory will have with the document. | Value | Role | Description | | ----- | -------- | ---------------------------------------------------- | | `1` | Signer | Can view and apply their signature to the document. | | `2` | Approver | Can review and approve but cannot sign. | | `3` | CC | Receives a final signed copy but cannot take action. | ### OTP (One-Time Password) Settings You can add an extra layer of identity verification using **Email** or **SMS-based OTP**. This is defined inside the `OTP` object. | Field | Type | Required | Description | | -------------- | --------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `IsRequired` | `boolean` | ✅ Yes | Set to `true` if OTP is required before signing. | | `AccessCode` | `string` | Optional | A custom passcode (if required by your compliance policy). Usually left blank. | | `Type` | `integer` | ✅ Yes |

OTP delivery methods:
1 = Email OTP
2 = SMS OTP

3 = AccessCode

4 = Email & SMS OTP

| | `MobileNumber` | `string` | Required if `Type=2 & Type=4` | This is required if SMS OTP is enabled. | {% hint style="info" %} If `IsRequired` is `true` and `Type=2 or Type=4` is selected, the **MobileNumber** must be valid. If missing, the request will fail. {% endhint %} ### Successful Response When a signatory is successfully added to a request, the API returns the following response: ```json { "requestId": "abc123-request-id", "signatoryId": "xyz789-signatory-id" } ``` ### Field Descriptions | Field | Type | Description | | ------------- | -------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `requestId` | `string` | The unique ID of the signature request the signatory was added to. This matches the request you created using `POST /requests?type=0`. | | `signatoryId` | `string` | A unique identifier for the newly added signatory. You'll need this ID to assign stamp placeholders, position stamps on the document, and track the signatory’s progress. | ### Possible Errors and How to Handle Them When adding a signatory to a request, the API may return standard error responses depending on the validity of the input or authentication state. Below are the most common error scenarios and how to interpret them: | Status Code | Error Message | Explanation | | ----------- | -------------------- | ----------------------------------------------------------------------- | | `400` | Bad Request | The request body is missing required fields or is improperly formatted. | | `401` | Unauthorized | The access token is missing, expired, or invalid. | | `404` | Request ID not found | The `requestId` does not exist or has been deleted. | # Add Stamps to a Signatory This operation allows you to assign **stamp fields** (such as signature, initials, date, etc.) to a signatory that was previously added to a `type=0` (skeleton) signature request. These stamps act as placeholders that will be visually placed on the document. You can add multiple stamps to a single signatory by calling this endpoint multiple times, each with a different `Identifier`. ## Request URL `POST` `/_apis/sign/api/v2/requests/requestId/signatories/signatoryId/stamps` This request URL is used to assign a stamp field to a signatory on a specific document. ### Required Headers These headers are required to authorize the request and define the content type. | Header | Required | Description | | --------------- | -------- | ------------------------------- | | `Authorization` | ✅ Yes | Bearer token for authentication | | `Content-Type` | ✅ Yes | Must be `application/json` | ### Request Body This is the JSON structure used to define a stamp placeholder. ```json { "Identifier": "signature1", "Type": "signature" } ``` ### Field-by-Field Explanation | Field | Type | Required | Description | | ------------ | -------- | -------- | ------------------------------------------------------------------------------------------ | | `Identifier` | `string` | ✅ Yes | A unique identifier for the stamp. This ID will be used later during stamp placement. | | `Type` | `string` | ✅ Yes | Defines the type of stamp (e.g., signature, name, email, date). See supported types below. | ### Supported Stamp Types These are the predefined field types you can assign to a document: | Type | Display Text | Field Behavior | | ----------- | ------------------ | ----------------------------------- | | `signature` | `Sign Here` | Signer's signature field | | `initial` | `Initial` | Initials field | | `name` | Full Name | Auto-fills signer's full name | | `email` | Signer’s Email | Auto-fills signer's email | | `date` | e.g., `mm/dd/yyyy` | Auto-inserts date (based on format) | | `text` | `Type here` | A blank text field for custom input | {% hint style="info" %} You can add multiple stamp types per signatory as long as each has a **unique Identifier**. {% endhint %} ### Successful Response ```json { "requestId": "abc123-request-id", "stampsCount": 1 } ``` ### Field Explanation | Field | Type | Description | | ------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------- | | `requestId` | `string` | The unique identifier of the signature request to which the stamp(s) were added. | | `stampsCount` | `number` | Indicates how many stamps were successfully added for the specified signatory. Typically `1` per request unless batching is supported. | ### Possible Errors and How to Handle Them When adding a stamp to a signatory, the API may return standard error responses based on validation or authorization failures. | Status Code | Error Message | Explanation | | ----------- | ---------------------- | ----------------------------------------------------------------------------------- | | `400` | Bad Request | The request body is invalid or missing required fields like `Identifier` or `Type`. | | `401` | Unauthorized | The access token is missing, expired, or invalid. | | `404` | Signatory ID not found | The provided `signatoryId` is invalid or does not exist. | # Send Signature Request This operation **initiates the signature workflow** by sending out notifications to all participants (signers, approvers, CCs) configured in the request. Once triggered, the request becomes active, and recipients can start interacting with the document based on their assigned roles. ## Request URL `POST` `/_apis/sign/api/v2/requests/requestId/send` To **start the signing process** for a signature request previously created using `type=0`. Once sent, signers will receive an email or SMS (depending on configuration), and the document becomes available for interaction. ### Required Headers These headers must be included to authenticate the request. | Header | Required | Description | | --------------- | -------- | ---------------------------------------------- | | `Authorization` | ✅ Yes | Bearer token obtained from the OAuth 2.0 flow. | ### Request Body This endpoint **does not** require a request body.\ A valid `requestId` and authenticated token are sufficient to trigger the request. ### Successful Response ```json { "requestId": "f742655b-7b27-43e1-9e4b-330246b140e6", "embeddedSigningUrl": null } ``` ### Possible Errors and How to Handle Them | Status Code | Error Message | Explanation | | ----------- | ----------------- | ------------------------------------------------------------------ | | `400` | Bad Request | The request ID may be missing or malformed. | | `401` | Unauthorized | The access token is missing, expired, or invalid. | | `404` | Request not found | The specified `requestId` does not exist or has already been sent. | # Edit Recipients This operation updates an existing recipient inside a signature request. Users can use this endpoint to modify a signatory’s name, email, OTP settings, recipient, and recipient's private message. Only non-completed recipients can be edited. All signing order and stamp placements will be preserved. ## Request URL `POST` /\_apis/sign/api/v2/Requests/{requestId}/editrecipient To update a recipient, submit the request with the **requestId** and the updated recipient details in the JSON body. A valid OAuth 2.0 access token is required. ### Required Headers These headers must be included to authenticate the request. | Header | Required | Description | | --------------- | -------- | ---------------------------------------------- | | `Authorization` | ✅ Yes | Bearer token obtained from the OAuth 2.0 flow. | | `Content-Type` | ✅ Yes | application/json | ### Request Body The request must include the updated recipient information. Below is the JSON schema: ```json { "UserName": "john.doe", "UserEmail": "john.doe@example.com", "OTP": { "IsRequired": true, "AccessCode": "987654", "MobileNumber": "+1-202-555-0123", "Type": 1 }, "PrivateMessage": "Requesting to update my registered email address.", "OldUserEmail": "john.doe.old@example.com", "AuditDetails": { "AuthorType": 1, "AuthorIPAddress": "192.168.1.55", "Device": "Device Type: Desktop - OS: Windows 11 - Browser: Chrome (v132.0)" } } ``` ### Successful Response ```json { "requestId" : "UUID" } ``` ### Possible Errors and How to Handle Them
Status CodeError MessageExplanation
400Bad RequestThe request ID may be missing or malformed.
400The updated email cannot be the same as the existing one.The new email matches the current email: no update is performed. Avoid editing without actual changes.
400Action denied. You don't have permission to edit recipient users because the user has already completed the request.Editing of a recipient who has already completed.
400The same user cannot be assigned more than once within a single requestThe email to be edited already exists as another recipient in the same request: duplicate users are not allowed.
404Editing isn’t allowed for this recipient.Editing of a recipient who has already completed.
#### Important Notes * Only **non-completed recipients** can be modified. * Signing order and stamp placements are **not affected** by recipient edits. * Audit fields help maintain security and document trail integrity. * The platform uses **`OldUserEmail`** as a unique identifier to locate the target recipient. # Webhook Management Webhooks allow your application to automatically receive **real-time updates** when specific events occur in the Evia Sign platform — such as when a **signature request is sent**, or **completed**. By configuring webhooks, you can eliminate the need for polling and seamlessly automate backend processes like notifications, updates, or workflows. ## Create a Webhook This operation allows you to **create a webhook** in Evia Sign by submitting your callback URL and subscribing to specific event types. Once created, Evia Sign will send structured payloads to your URL every time a selected event is triggered. ## Request URL `POST``/api/v2/webhooks` This is the request URL used to **create** and subscribe a new webhook. {% hint style="info" %} Your application must include the destination URL (`url`) and specify one or more event types (`events`) it wants to subscribe to. {% endhint %} ### Required Headers These headers are essential for authorizing the request and ensuring the server processes the payload correctly. | Header | Required | Description | | ------------- | -------- | --------------------------------------------- | | Authorization | ✅ Yes | Bearer token obtained from the OAuth 2.0 flow | | Content-Type | ✅ Yes | Must be set to `application/json` | ### Request Body Schema The structure used to define your webhook’s behavior — including where the data should be sent and which events to listen for. ```json { "url": "https://yourdomain.com/callback", "events": ["request.sent", "request.completed"] } ``` This payload defines: * The **public HTTPS** where Evia Sign will send updates. * The **events** your system wants to subscribe to. ### Field Descriptions Details about the fields expected in the request body — so developers understand what to send and why it matters. | Field | Type | Required | Description | | ------ | ------ | -------- | -------------------------------------------------------------------------------- | | url | string | ✅ Yes | Your HTTPS endpoint to receive event notifications. Must be publicly accessible. | | events | array | ✅ Yes | List of event types to subscribe to (see supported events). | ### Supported Events A list of available webhook event types that can be subscribed to. These determine what kinds of changes will trigger a callback to your server. | Event Name | Description | | ------------------- | ----------------------------------------------------- | | `request.sent` | Triggered when a signature request has been received. | | `request.completed` | Triggered when all required signatures are completed. | ### Example: Create a Webhook A ready-to-use payload sample that shows how to submit a webhook creation request. ```json { "url": "https://webhooks.yourdomain.com/evia-sign", "events": ["request.sent", "request.completed"] } ``` ### Event Payloads Illustrates what your server will receive when each subscribed event occurs. Useful for developers to prepare their endpoint to handle incoming data correctly. **`request.sent`** ```json { "Name": "Jane Doe", "Email": "jane@example.com", "Subject": "Contract.pdf", "Link": "https://evia.enadocapp.com/sign/#/sign/abc123" } ``` | Field | Type | Description | | ------- | ------ | ---------------------------------------------- | | Name | string | Name of the participant (initiator or signer). | | Email | string | Email address of the recipient. | | Subject | string | Title or filename of the document. | | Link | string | Direct signing URL. | *** **`request.completed`** ```json { "RequestId": "abc123", "Status": "Completed" } ``` | Field | Type | Description | | --------- | ------ | ---------------------------------------------- | | RequestId | string | Unique ID of the completed signature request. | | Status | string | Final status (`Completed`, `Cancelled`, etc.). | ### Delete a Webhook Describes how to remove an existing webhook subscription when it’s no longer needed **Request URL** ``` DELETE /api/v2/webhooks/webhookID ``` Replace `webhookId` with the actual ID of the webhook to be deleted. ### Possible Errors and How to Handle Them A quick-reference table to help developers troubleshoot issues like malformed payloads, missing tokens, or duplicate registrations. | Status Code | Error Message | Explanation | | ----------- | ----------------- | --------------------------------------------------------- | | 400 | Bad Request | The request body is malformed or missing required fields. | | 401 | Unauthorized | Access token is missing or expired. | | 404 | Webhook Not Found | The given webhook ID does not exist. | # Glossary & Common Fields | `SignatoryType` | 1 = Signer, 2 = Approver, 3 = CC. | | --------------- | --------------------------------- | | `OTP` | Optional security layer via email or SMS. | | ----- | ----------------------------------------- | | `Audit Trail` | Automatically generated after all signatories complete their action. | | ------------- | -------------------------------------------------------------------- | | `DocumentToken` | Returned after successfully uploading a document. | | --------------- | ------------------------------------------------- | | `Documents` | Array of uploaded document tokens used when creating requests. | | ----------- | -------------------------------------------------------------- | | `Signatories` | Required for types 0–3. Defines participants either inline or added separately. | | ------------- | ------------------------------------------------------------------------------- | # Welcome to the New and Improved Evia Sign Welcome to the upgraded Evia Sign experience! It’s still the eSigning experience you know and love—just cranked up a notch for an even smoother, smarter, and faster workflow. This manual is your go-to guide for navigating the new and improved experience. Whether you're a seasoned user or just getting started, we’ll walk you through everything that’s new, ensuring you make the most of every signature. Let's begin Evia Sign now offers a **simpler, cleaner, and more intuitive** experience. The interface has been redesigned with a fresh, elegant look, making it easier to navigate and track your document statuses at a glance. The inbox has been restructured to provide better organization, allowing you to **quickly identify pending actions, approvals, and completed requests** without unnecessary clutter. The improved layout ensures that everything you need is easily accessible, helping you stay on top of your signing tasks with minimal effort. With these updates, managing your documents is now more seamless than ever.

New and Improved Evia Sign Interface

### Sending a Signature Request in the New and Improved Evia Sign To begin, click on the "**New Sign Request**" button—the big blue one—to get started. Once clicked, you’ll be directed to a streamlined, four-step process designed to make sending signature requests easier than ever.

Begin Signature Request

### Step 1: Upload the Document The first step in the process is to upload the document that needs signatures. You have two options: ● Click the "**Browse**" button to upload a document from your device or select a file directly from **OneDrive Business**.

Upload Document

Once uploaded, you’ll see a preview of your document, ensuring everything looks good before proceeding.

Document Preview

When your document is ready, click "**Next**" or the "Process 2" button to move on to the next step—adding your signatories.
### Step 2: Adding Signatories – A Guide to the Contact List As you type the name of a signatory, a contact list will appear.

Contact List

This list includes: * **Internal users** – All members of your organization who have been added to the Evia Sign platform.

Internal Users

* **External users** – Signatories outside your organization, indicated by an external user icon. Whenever you add a signatory outside your organization, they will automatically appear in the contact list with the external user icon.

External Users with Icons

In the contact book, you can: * Sort users alphabetically.

Sort users alphabetically

* Filter internal and external users separately for easy selection.

All Contacts

Internal Users

External Users

#### Adding a Signatory from the Contact List If the signatory you want to add is already in the list, click the plus **(+)** icon next to their name to add them as a signatory to the document.

(+) Icon

User added

#### Adding a New Signatory If you need to add a new signatory, click on the **Add More** button, type in their name and email address, then click the save icon to store them in your contact list for future use.

Add More Users

Save New Contact

New User Added

#### Accessing Your Full Contact List To browse all your saved contacts, click the **Contact Book** icon. From there, follow the same process to add as many signatories as needed to the document.

Contact Book

#### Define Signatory Actions & Signing Order Once you have added your signatories, the next step is to define their role in the document. #### **Assigning Signatory Roles** Select the relevant signatory and click the sign icon to choose one of the following roles: ○ **Signer** – Required to sign the document. ○ **Approver** – Reviews and approves the document without signing. ○ **CC** **Recipient** – Receives a copy of the document for reference.

Signatory Action Icon

Define Signatory Action

#### **Setting the Signing Order** ● Drag and drop signatories to rearrange the order in which they will take action on the document.

Drag and Drop Signatories

● This helps predefine the signing sequence for a structured workflow.

Signing Order Changed

#### **Proceed to Signature Stamps** Once everything is set up, click the "**Next**" button or "Process 3" to move to the next step—adding signature stamps!
### Step 3: Place Signature Stamps In process 3, you can assign signature fields to the signatories you added in the previous step. #### Adding Signature Stamps Select the relevant signatory. Drag and drop their required signature stamp into the correct spot in the document.

Drag and Drag Stamps

Once all stamps are placed correctly, click "**Next**" or "Process 4" to continue.

Stamps Placed In The Document

### Step 4: Send the Document In this final step, you can add a quick message for your signatories before sending the document. #### **Adding a Message** 1. Type a short message for your signatories. This can include instructions or additional details about the document.

Message To Be Delivered To All Signatories

#### **Sending the Document** 2. Click "**Send**" to dispatch the document to all recipients.

Send Document To Signatories

#### Congratulations! You’ve successfully sent a signature request using the new and improved Evia Sign.

Signature Request Sent Successfully

> **Your signatories will receive an email prompting them to review and sign the document.** # How to Use the PDF Commenting Feature in Evia Sign With Evia Sign, you can do more than just request signatures—you can also **post comments directly on the document** to provide instructions, clarifications, or feedback. Whether you're the document requester or a signer, this feature helps streamline communication without endless back-and-forth emails. ## **How to Post a Comment When Sending a Signature Request** ### **Step 1: Upload your document & start the signature request** Follow the usual process to send a document for signing.
### **Step 2: Adding the comments** In the third step of the signature request process, you’ll notice a **Comment Stamp**.
Click on the **Comment Stamp,** drag and drop it to the relevant section of the document and type your comment in the provided space.
### **Step 3: Control who can see the comment** If multiple signatories (e.g., 5 people) are involved, you can choose who gets to see your comment.
To do this, click on the **visibility icon**, then **select or deselect signatories** accordingly.
### **Step 4: Post the comment** Once your comment is ready, click **Post** to finalize it.
The selected recipients will see the comment while reviewing and signing the document, and they can also reply to the comment during the signing process
## How to post a comment before signing a document If you are a **signatory** and want to leave a comment before signing, follow these steps: ### **Step 1: Open the document for signing** When you receive a signature request, click on the document to open it.
### **Step 2: Click on the comment icon** In the document signing interface, you will see a **Comment Icon** (similar to the stamp used when sending a request).
### **Step 3:** **Drag & Drop the Comment Stamp** Click on the Comment Stamp, then click anywhere in the document where you want to leave a comment.
### **Step 4: Enter Your Comment** Type your message in the provided space and click **Post** to finalize your comment.
{% hint style="info" %} If multiple people are involved in the signing process, you can choose **who should and shouldn’t see the comment** by clicking on the **visibility icon** and selecting/deselecting signatories. {% endhint %} The selected members will see the comment during the signing and reviewing process, and they can also reply to it.
## **How to edit a posted comment** If you need to change something in your comment after posting it, follow these steps: To edit a comment: Find the comment on the document.
Click on the **three-dot menu** next to the comment.
Select **Edit**, make the necessary changes, and click **Post** again to update the comment.
## How to delete a posted comment To delete a comment: Locate the comment you want to delete and click the **three-dot menu** on the comment.
Select **Delete**, and the comment will be removed from the document.
{% hint style="info" %} You can only edit or delete a comment **before sending the signature request or before the signing process is completed.** {% endhint %} # How to Upload Documents from SharePoint in Evia Sign Evia Sign now makes it effortless to pull in documents directly from your SharePoint account ## What You Can Do * Connect your SharePoint account from inside Evia Sign. * Browse SharePoint lists and folders that holds your documents. * Select and attach documents directly to your signature request * Complete the eSignature request flow—all without leaving the app. > This guide walks you through how it works from start to send. ## **Step 1: Start a Signature Request** Head to your Evia Sign account and click **“NEW SIGN REQUEST”** to begin a new signing process.
## **Step 2:** In the Document Upload Step, Click “SharePoint” When you reach the **Document Upload** step, you’ll see a button labeled **“SharePoint.”**\ Click it to connect with your SharePoint account.
{% hint style="info" %} I**f you haven’t connected your SharePoint account yet, you’ll be prompted to log in using your SharePoint credentials.** {% endhint %} Once connected, Evia Sign will open a **custom file picker window** that lets you browse your SharePoint environment—without ever leaving the app.
## **Step 3: Browse Your SharePoint Lists and Document Folders** Right Inside Evia Sign The custom file picker window will show your available **SharePoint lists**, each containing folders with the documents you need.
To view and explore your **SharePoint lists**, use the dropdown at the top to select the one you want to access. Evia Sign will then display the folders (items) inside it.
## **Step 4:** Select the Folder That Has Your Documents After choosing a list, you’ll see a set of folders (or items) that hold your SharePoint documents.
Tick the checkbox next to the folder you want to use for your signature request.
## **Step 5: Attach and You’re Done** Once selected, click **Attach**.
Evia Sign will instantly pull the documents from SharePoint and add them to your signature request.
> From here, just continue like usual—assign signatories, place your signature stamps, and send it off.