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
  • βœ… What You Can Keep As-Is
  • πŸ” What’s Different in API v2
  • βš™οΈ Migration Steps in API v2
  • πŸ“Š Summary Table

Was this helpful?

  1. Evia Sign API
  2. V2
  3. 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)

POST /api/v2/requests?type=0
Authorization: Bearer <token>
Content-Type: application/json

{
  "title": "Auto Stamping - Test",
  "message": "This is your document",
  "completedDocumentsAttached": true,
  "callbackTypes": [1],
  "documents": ["<documentId>"]
}

πŸ” Returns: requestId


3. Add Each Signatory

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

POST /api/v2/requests/{requestId}/signatories/{signatoryId}/stamps

{
  "identifier": "<<vp_1_s>>",
  "color": "#7c95f4",
  "order": 1,
  "offset": {
    "xOffset": 0,
    "yOffset": 0,
    "offsetType": 2
  },
  "stampSize": {
    "height": 50,
    "width": 100
  },
  "type": "signature"
}

5. Send the Request

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.

PreviousHow to Migrate from API v1 to v2NextAccess Token Request (v1 ➞ v2)

Last updated 11 days ago

Was this helpful?