The DocuSign Developer: Deep Dive Discussions video series covers ground from basic to complex DocuSign API use, as well as insights from our experts on best practices to speed up your development.

In this episode, Keith Litwin, Senior Director of Engineering, showcases the technical nuts and bolts behind DocuSign’s newest acquisition, SpringCM.

SpringCM fits perfectly into the Prepare (document preparation) stage of DocuSign’s System of Agreement by enabling customers to create and collaborate prior to agreement. Specifically, SpringCM enables customers to generate documents, route them for approval and manage redlining, all from the convenience of its intuitive user interface.

Leveraging a contract generation and signature use case in Salesforce, Keith demonstrates how easily developers can interact with SpringCM objects to both obtain information, such as document tracking activities and automate tasks, such as managerial approvals.

The SpringCM REST API contains authentication functionality and three logical sub APIs for programmatically working with SpringCM functionality:

  • Object API – API methods that expose create, read, update and delete functionality for SpringCM objects.
  • Task API – API methods that expose SpringCM services that are invoked as asynchronous tasks
  • Content API – API methods for uploading, downloading and versioning documents in SpringCM

Watch DocuSign Developer – SpringCM REST API:

For the latest in this series, visit the DocuSign Developer: Deep Dive Discussions YouTube playlist, sign up for our developer newsletter and follow us on Twitter.


Matthew Roknich is Developer Evangelist and a lifelong problem solver. His current projects outside of DocuSign involve advanced IoT and sustainability. He can be found on a soapbox talking about the eSignature API at a variety of developer conferences, hackathons, and meetups.