Community
SignEasy differentiate
Does SignEasy differentiate between “minor changes” (e.g., modifying metadata, adding recipients ) and “major changes” (modifying content) when deciding whether to reset a signature?
I need help
I’m trying to better understand how Signeasy manages document lifecycle and compliance in more complex, real-world workflows. Specifically, how does the platform handle version control and maintain audit trail integrity when a document is modified after being sent out for signature but before all recipients have completed signing?
Hi team support
Hi team, I'm building a multi-tenant SaaS using the Signeasy API and planning to use the Authorization Code flow for multiple users. However, I'm struggling with handling token lifecycle and webhook synchronization together.
Document upload failed
"error": "Internal Server Error", "message": "Something went wrong. Please try again later. If the problem persists please raise a support request to [email protected].", "error_detail": "document_operation Service Failed"
Error on uploading
{
"message": {
"Key: 'UploadFileRequest": "Invalid Key: 'UploadFileRequest payload - File' Error:Field validation for 'File' failed on the 'required' tag\nKey: 'UploadFileRequest"
}
}
Hasan
Hi this is Hasan, my banker sent me a document to sign, but I didn't get any email. I already tried different email, not work.