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)

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.

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

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.

JavaScript

{
   "Documents":[
      "documentId1",
      "documentId2",
      "documentId3"
   ],
   "WebhookUrl":"https://webhook.site/SampleUrl"
}

Python

Ruby

Response

200

{
    "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"
}

400