Server Signing (API)
Within the ThrivoSign Remote Signing Solution, users have access to three versatile methods via the Server Signing API, tailored to accommodate diverse document signing needs. These methods include dynamic PDF signing, fixed templates, and embedded APIs, each seamlessly integrated into server environments. By offering flexibility and efficiency, these options streamline the document signing process within the ThrivoSign Remote Signing Solution, ensuring seamless integration and adaptability to various signing workflows. ThrivoSign's commitment to comprehensive digital document signing solutions is exemplified through its Remote Signing Solution, providing users with versatile options to meet their specific requirements and preferences effortlessly.
Use Case: Fixed Template
Description: This use case involves using a predefined template for documents that need to be signed. The template includes fixed fields for signatures and other necessary information.
Main Flow:
List Template: User logs into the system to list template, then return the templateID.
Use template: Use the template and add a recipient, then return the documentID and packageID.
Update text field value: The user updates the necessary values in the fixed fields of the template.
Update Signature Image: The user updates the signature image in the fixed fields of the template.
Process and Share Document: The Server Signing API receives the request and processes it.
Sign Document: Sign document based on the user digital certificate
Push Notification Verification: The user will receive a push notification to either approve or reject the request.
Confirmation: The user approves the request indicating that the document has been signed successfully.
Use Case: Workflow Signing
Description: This use case entails a step-by-step signing process, commencing with package creation and followed by document upload, signatory assignment, and sequential signature collection.
Main Flow:
Add package: The user creates a package, specifying the document to be signed and establishing the signing workflow order.
Upload document: The user uploads the document into the package.
Add user: The user adds recipients who need to sign the document.
Add fields: The user add to signature fields or text fields
Update text field value: The user updates the necessary values in the fixed fields of the template.
Update Signature Image: The user updates the signature image in the fixed fields of the template.
Process and Share Document: The Server Signing API receives the request and processes it.
Sign Document: Sign document based on the user digital certificate
Push Notification Verification: The user will receive a push notification to either approve or reject the request.
Confirmation: The user approves the request indicating that the document has been signed successfully.
Use Case: Embedded Signing
Description: This use case revolves around signing a document seamlessly within an application or website by utilizing an embedded signing interface.
Main Flow:
Add package: The user creates a package, specifying the document to be signed and establishing the signing workflow order.
Upload document: The user uploads the document into the package.
Add user: The user adds recipients who need to sign the document.
Get Signing URL: The user generates a URL to prepare the fields and share the document. Once preparation is complete, the user is redirected to the login page.
Apply signature: Once the fields are prepared, the user uses the same URL to sign the document.
Push Notification Verification: The user receives a push notification to either approve or reject the request.
Confirmation: The user approves the request indicating that the document has been signed successfully.
Last updated