Create Signature Request
After uploading a document, the next step is to initiate a signature request.Depending on the workflow, you can choose from four signature request types.
Endpoint
POST
/api/v2/requests?type={0|1|2|3}
Headers
Authorization
Bearer {access_token}
OAuth 2.0 token obtained during authentication
Content-Type
application/json
Required for sending JSON formatted payloads
Request Types
0
Skeleton (Automation / RPA)
Step-by-step creation using separate calls for signatories and stamps.
1
Template-Based
Uses a predefined template configured within Evia Sign.
2
Fixed Positioning
Manually define exact coordinates for each stamp/signature.
3
Auto-Stamping
Automatically places signatures based on smart tags in the document.
Common Payload Fields
Title
string
Title of the signature request.
Message
string
Optional message for signatories.
Documents
array
Array of uploaded document tokens.
CallbackUrl
string
Webhook URL to receive status updates.
CallbackTypes
array
Events to trigger callbacks (e.g., request.sent, completed).
CompletedDocumentsAttached
boolean
Whether to attach the completed document in callbacks.
Example Payloads
Type 0 (Skeleton - Automation/RPA)
Create the request first, then separately add signatories and stamps.
Type 1 (Template-Based)
Utilizes an existing template, predefining roles and stamp placements.
Type 2 (Fixed Positioning)
You define exactly where each signature or stamp should appear.
Type 3 (Auto-Stamping)
The API finds smart tag placeholders (e.g., {{signature1}}
) inside the PDF and automatically places the stamp.
Last updated