E-Signature SDKs Connect to Your Existing Business Applications

Sherry Ghafarpour, June 20, 2014

Businesses are increasingly moving to electronic signatures because they provide a significantly better customer experience and ensure a higher level of security and compliance than wet signatures. When e-signatures are offered as part of a business application, users are able to prepare, send and sign documents within an environment that is tied to their existing workflows.

This not only provides a familiar interface from which to leverage e-signatures, but also helps ensure the highest adoption rates by customers and users alike. While e-SignLive has a number of out-of-the-box integrations with third-party business tools, some developers require solutions that are tailored to their specific needs. Developers wishing to connect their homegrown or other third-party systems to e-SignLive can do so through REST API calls. Because Microsoft’s .Net and Java are two widely used development platforms for business, we also offer an SDK for developers writing with .Net and Java technologies.

With the e-SignLive e-Signature SDK, you can easily create and configure transactions for e-signing, regardless of how simple or complex the digital transaction is. The SDK has a fluent interface style that makes it easy to integrate e-signatures with document generation, content management and other systems for true straight-through processing In addition, we know that providing a seamless experience for your users is important. The SDK allows customization of the signing experience, which helps ensure the e-signing experience feels like it was always built into the original application.

E-signature SDK built with developers in mind

Our SDK is built based on direct input from the developer community. We recently added new functionalities into our .Net and Java SDKs to enable you to integrate e-signatures into your applications faster than ever before. You now have the ability to:

  • Create and send packages on behalf of other senders. For integrated customers creating packages using an API key, this is a way to specify who’s the owner of the package, instead of the default API key user.
  • Edit, trash and archive packages.
  • Add, edit and remove signers.
  • Update the signer order.
  • Add, edit, and remove documents.
  • Update the document order.
  • Create templates and view all templates. Template data (e.g., metadata, signers, documents) can be updated using the same package manipulation methods.
  • Mask/hide the answers of signer authentication questions.
OneSpan Developer Community

OneSpan Developer Community

Join the OneSpan Developer Community! Forums, blogs, documentation, SDK downloads, and more.

Join Today

Sign up for a free e-SignLive developer account

Once you register, we’ll provide you with everything you need to get started quickly—i.e., sample code, complete documentation and full access to our Sandbox environment for unlimited prototyping and testing. Create a free developer account today.

Complete SDK documentation for Java and .Net platforms is available in our documentation portal. All of the SDK source code, along with examples, is open sourced and publicly available on GitHub. Give the e-SignLive SDK a try in our sandbox environment and see how easy it is to enable your business applications with e-signatures.