Hey HN! Victor here from SignatureAPI (<a href="https://signatureapi.com" rel="nofollow">https://signatureapi.com</a>)<p>SignatureAPI is an electronic signature platform via API. Our customers use SignatureAPI to add electronic signatures to their apps and workflows.<p>SignatureAPI was born out of the frustration of a friend of mine who needed to integrate electronic signatures into his app, but found Docusign API, at $1+ per envelope, too expensive for his use case. We quickly realized that many others shared this same frustration.<p>We are different from other platforms such as Docusign, Dropbox Sign, Adobe Sign, etc in two key ways:<p>1. API-First. We are focused on the ease of integration and the developer experience (we are proud of our docs). With SignatureAPI, the API is not a second-class citizen to the UI. The API _is_ the product.<p>2. Pricing. Our pricing ranges from $0.10 to $0.25 per envelope. Compare that to Docusign API at $1.25–$4.80, Dropbox Sign API at $1.50–$2.50, or Adobe Sign API at $1.80–$2.50.<p>Our electronic signatures are legally binding in many places, including the US and the EU. The legal foundation of SignatureAPI was developed by a top team of electronic signature lawyers. (And yes, we have the “green checkmark” in Acrobat).<p>We’d love to hear your honest feedback—likes, dislikes, feature requests—whatever you’ve got.
First thanks for shring this. Why should one use this (or docusign hellosign etc) if there are open source esignature platforms like documenso docuseal etc
I didn't see any verification of the person, like checking an ID. Is that not a normal part of electronic signatures?<p>It seems like a path that a tech savvy company could excel in: document/ID photos, voice or video confirmations, recorded interviews..