Evia Sign
  • Welcome to Evia Sign
    • What can Evia Sign do?
  • How to send signature request?
    • How to enable multiple signatories to access and sign documents at the same time?
    • How to add approvers and CC recipients to a signature request?
    • How do you add authentication to your request?
    • How do you send a private message?
  • How to sign documents?
    • Opening a document through Evia Sign inbox
    • Explore the different ways to add your signature
  • How to draft documents?
    • Components of DRAFTS in Evia Sign
  • Explore Evia Sign Inbox
  • How to create and use templates
    • Components of TEMPLATES
  • How to save your signature and initial?
  • How to add date stamp to your signature?
  • How to set up automatic reminders & expiration for signature requests
  • Users
    • How to import O365 users?
    • How to add new users?
    • How to delete users?
    • How to activate and deactivate users?
  • How do I change the current subscription plan of my account?
    • How to cancel and renew plan?
    • How do I purchase additional user licenses?
  • How to work with Enadoc Integration?
  • Terms to be familiar
  • FAQs
    • How to login into Evia Sign?
    • How do I make an account recovery?
    • How do you configure stamps?
    • How do you manually send reminders to signatories?
    • How do you view document history?
    • How do you decline a document?
    • How do you download a document?
    • What is a digitally certified document?
    • How are additional user licenses purchased?
    • How do you send reminders to signatories?
    • How to modify your session duration?
    • How do I monitor the request usage of my Evia Sign account?
  • Release Notes
  • Evia Sign API
    • V1
      • Overview
      • Authorization of the API Access
      • Requests
        • Document Upload
        • Send Requests
      • Request Types
        • Template
        • Fixed Positioning
        • Auto Stamping
    • V2
      • Welcome to Evia Sign API Version2
      • How to Migrate from API v1 to v2
        • Basic Guide with minimal changes
        • Access Token Request (v1 ➞ v2)
      • Authorization & Authentication
        • How to Register Your Application
        • Requesting the Authorization Code
        • Exchange Authorization Code for Access Token
      • Upload Document for Signing
      • Creating a Signature Request
      • Add Signatory to a Signature Request
      • Add Stamps to a Signatory
      • Send Signature Request
      • Webhook Management
      • Glossary & Common Fields
  • Welcome to the New and Improved Evia Sign
  • How to Use the PDF Commenting Feature in Evia Sign
  • How to Upload Documents from SharePoint in Evia Sign
Powered by GitBook
On this page
  • Document Upload URL
  • Authentication
  • Headers
  • Request Body Details
  • Successful Response
  • Possible Errors and How to Handle Them

Was this helpful?

  1. Evia Sign API
  2. V2

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 /thumbs_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.

{
"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 Code
Error Message
Explanation

400

Allowed extensions are PDF, DOC, DOCX

The uploaded file was not a PDF, or the form field key was incorrect.

401

Unauthorized

The access_token was missing or expired

PreviousExchange Authorization Code for Access TokenNextCreating a Signature Request

Last updated 24 days ago

Was this helpful?