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
  • Request URL
  • Required Headers
  • Request Body
  • Field-by-Field Explanation
  • Supported Stamp Types
  • Successful Response
  • Field Explanation
  • Possible Errors and How to Handle Them

Was this helpful?

  1. Evia Sign API
  2. V2

Add Stamps to a Signatory

This operation allows you to assign stamp fields (such as signature, initials, date, etc.) to a signatory that was previously added to a type=0 (skeleton) signature request. These stamps act as placeholders that will be visually placed on the document.

You can add multiple stamps to a single signatory by calling this endpoint multiple times, each with a different Identifier.

Request URL

POST /_apis/sign/api/v2/requests/requestId/signatories/signatoryId/stamps

This request URL is used to assign a stamp field to a signatory on a specific document.

Required Headers

These headers are required to authorize the request and define the content type.

Header
Required
Description

Authorization

✅ Yes

Bearer token for authentication

Content-Type

✅ Yes

Must be application/json

Request Body

This is the JSON structure used to define a stamp placeholder.

{
  "Identifier": "signature1",
  "Type": "signature"
}

Field-by-Field Explanation

Field
Type
Required
Description

Identifier

string

✅ Yes

A unique identifier for the stamp. This ID will be used later during stamp placement.

Type

string

✅ Yes

Defines the type of stamp (e.g., signature, name, email, date). See supported types below.

Supported Stamp Types

These are the predefined field types you can assign to a document:

Type
Display Text
Field Behavior

signature

Sign Here

Signer's signature field

initial

Initial

Initials field

name

Full Name

Auto-fills signer's full name

email

Signer’s Email

Auto-fills signer's email

date

e.g., mm/dd/yyyy

Auto-inserts date (based on format)

text

Type here

A blank text field for custom input

You can add multiple stamp types per signatory as long as each has a unique Identifier.

Successful Response

{
  "requestId": "abc123-request-id",
  "stampsCount": 1
}

Field Explanation

Field
Type
Description

requestId

string

The unique identifier of the signature request to which the stamp(s) were added.

stampsCount

number

Indicates how many stamps were successfully added for the specified signatory. Typically 1 per request unless batching is supported.

Possible Errors and How to Handle Them

When adding a stamp to a signatory, the API may return standard error responses based on validation or authorization failures.

Status Code
Error Message
Explanation

400

Bad Request

The request body is invalid or missing required fields like Identifier or Type.

401

Unauthorized

The access token is missing, expired, or invalid.

404

Signatory ID not found

The provided signatoryId is invalid or does not exist.

PreviousAdd Signatory to a Signature RequestNextSend Signature Request

Last updated 24 days ago

Was this helpful?