TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Building vs. Buying an eSignature API

15 pointsby encorektover 6 years ago

3 comments

leetroutover 6 years ago
I built a very rudimentary digital &#x2F; electronic signature tracking app in Django several years ago and I would have gladly paid for this product.<p>Just like stripe, offering a service with a developer friendly API-first approach is great and I happily pay for someone else to be the domain expert.<p>Sucks when services go down or are complete black boxes but I&#x27;ve been using HelloSign for several years as a consumer and it&#x27;s always been fantastic. This was a neat article and I&#x27;ll be sure to use them the next time I need to integrate signing in an app.
ykevinatorover 6 years ago
We built our own because it was about the same work to use an api as it was to just build a canvas solution. Inline pdf signatures are a little harder but we will be building that next. The first build literally took a few days. I understand paying $50 a month for docusign but it&#x27;s baffling why anyone would pay $50k or $100k per year for what is essentially a feature.
tinaleatonover 6 years ago
Realistically, probably <i>most</i> organizations out there really don&#x27;t need to spend the time or resources building a solution when super-customizable options like this exist. Just gotta get out of that mindset.