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:
Upload the document (same as v1)
Create the request (with
?type=0)Add signatories
Add stamp positions
Send the request
βοΈ Migration Steps in API v2
1. Upload the Document (No Change)
β
Returns: documentId
2. Create the Request (type=0)
π Returns: requestId
3. Add Each Signatory
βοΈ Returns: signatoryId
4. Add AutoStamp for the Signatory
5. Send the Request
β This triggers the document and sends it to signers.
π Summary Table
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=0must be passed as a query parameter in v2 request creationWebhooks 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.
Last updated