Fixed Positioning
Implementation Overview
Evia Sign's Fixed Positioning API introduces a seamless and secure approach to automated annotation placement, focusing on precise positioning of signatures within documents. This API supports a structured JSON payload, empowering users to define key elements for creating signature requests with fixed positioning.
This API endpoint enables the creation of a new signature request with fixed positioning:
POST
https://evia.enadocapp.com/api/Requests?type=2
Headers
Authorization
Bearer
Access token should be sent as request header
Upon successful creation, a status code of 200 is returned, confirming the successful initiation of the sign request.
Request Body for Fixed Positioning
Signing Order: Signing requests can be sent either in parallel, where all signatories receive the request simultaneously, or sequentially, where each signatory receives the request one after another.
Signatory Types: Signatories can be categorized as either Signing, Approval, or CC. At least one Signing signatory is required for each request, and signature fields are mandatory for signing. Additional options include the ability to add initials, name, signed date, email, and text.
Security Features: For added security, there is an option to include an OTP (One-Time Password) via email, SMS, or both, and to set an access code.
Audit Trail: Once the document is completed, an audit trail document is generated for each request. It includes the details of the sender and the signatories, such as IP addresses and devices used.
Signer Types: Signers can either be internal or external.
Last updated